Claude Code Skills

Claude Code is only as disciplined as the instructions it works under. This is a private plugin marketplace with two plugins: workflow, a task-driven engineering process with eleven skills, and php-code-quality, two skills that load themselves whenever Claude touches PHP. They are the same skills used to build and maintain Flow PHP.

Install them once and they show up as slash commands in every project:

/plugin marketplace add flow-php-depot/claude-skills
/plugin install workflow
/plugin install php-code-quality

The task file is the plan

The workflow plugin is built around one idea: planning produces a task file precise enough to implement without guessing, implementation follows it with zero freedom, and reviews audit against it. /plan-task runs a planner against project-specific challengers until the file is executable, /work-on-task executes it exactly as written, and /cleanup-task and /review-task close the loop on every change.

Tasks live in epic folders and accumulate sibling artifacts as they move through the chain, so a finished epic is its own audit trail. /cleanup-epic and /review-epic then hunt the failures single-task reviews cannot see: unowned requirements, drifted contracts, duplicated solutions.

Findings that survive an adversary

Review skills never hand you raw output. Every finding must survive a refute-by-default verifier before it reaches you, and "clean" is always a valid result. Heavy reading and verification run in subagents, so your conversation context stays small - and each skill asks whether to run multi-agent or single-agent, so you choose the cost per invocation.

Nothing happens without you. Architectural decisions, fixes and branch changes are always your call - the skills ask, with a recommendation and full context, and wait.

PHP code quality that loads itself

The php-code-quality plugin needs no invocation. php-type-narrowing loads on PHP files and pushes every signature, property and docblock to the narrowest honest type instead of mixed or bare array. php-testing loads on test files and enforces tests that assert behavior and survive refactoring: handcrafted stubs over mocks, ObjectMother over private helpers, unit tests for edge cases and integration tests for happy paths.

On first use in a repository each skill detects the project's setup - the static analyzer and its annotation dialect, how tests run - confirms it with you once, and never re-asks.

Adapts to your project

The skills are project-agnostic and work out of the box. To teach them your conventions you add extension files - per project and shared with the team, or personal and applied in every repo. Sections resolve independently: project wins, undefined sections fall back to your personal file, then to the built-in defaults. A repo can override just its QA commands while inheriting your personal challenger lenses.

What's in the repository

• The workflow plugin: eleven skills covering plan, explain, implement, cleanup, review - per task and per epic
• Companions that plug GitHub into the chain: /explain-issue reproduces an issue, /explain-pr tours any pull request, /catch-up restores context after time away
• The php-code-quality plugin: type narrowing and testing rules that auto-load on PHP and test files
• One marketplace repository - install only the plugins you want, they are independent
• Extension points for project and personal conventions, documented per skill
• Updates as the skills evolve, at no extra cost

What it is not

It is not a prompt pack. The skills are a process - gated steps, persisted artifacts, verification that must come back clean - and they slow Claude down on purpose where being fast produces slop. You need Claude Code itself; the plugins add no API costs of their own, but the multi-agent modes spend more of your existing usage in exchange for thoroughness, and every skill offers the cheaper single-agent mode.