Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →florianbruniaux/plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
Passed 21 of 25 test cases with the skill, and 7 of 25 without it.
and 12 more in the full report
14 fixed7 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the pipeline execution graph, which review stage must be executed immediately before `eng-review`?
| Checked | Without skill | With skill |
|---|---|---|
| Names `ceo-review` as the preceding stage. | Missed | Passed |
The instructions your model reads when the skill loads.
Orchestrates the complete plan-to-execution pipeline. Can run the full pipeline or a single isolated stage.
| Stage | Skill | Purpose |
|---|---|---|
| 1 | /plan-pipeline:ceo-review | Challenge the brief, lock product direction |
| 2 | /plan-pipeline:eng-review | Lock architecture, diagrams, and test matrix |
| 3 | /plan-pipeline:start | 5-phase planning: PRD, research, ADRs, task list |
| 4 | /plan-pipeline:validate | 2-layer validation before any code is written |
| 5 | /plan-pipeline:execute | Worktree isolation, parallel agents, quality gate, PR |
/plan-pipeline # full pipeline, asks for context
/plan-pipeline --from=start # skip gates, start from planning phase
/plan-pipeline --from=validate # validate an existing plan
/plan-pipeline --from=execute # execute a validated plan
ceo-review: use before any significant feature when the direction is not locked. Especially valuable when the request is specific (specificity signals collapsed solution space).
eng-review: use after direction is locked. Required for features with async components, external dependencies, or multi-step flows.
start: use for any non-trivial feature touching more than 2 files or involving architecture decisions.
validate: always before execute. The cost of validation is negligible against the cost of discovering issues mid-execution.
execute: after validate confirms all issues are resolved.
--from=eng-review or later)--from=start or later)test cases passed, vs 7 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.