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.
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./examples/skills/plan-pipeline/SKILL.mdOrchestrates 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 planceo-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)docs/plans/plan-{name}.mdceo-review
|
eng-review
|
start
|
validate
|
executeEach stage writes its output to disk before the next stage begins. If the pipeline is interrupted, resume with --from=<stage> using the correct stage name. All decisions are recorded in docs/plans/plan-{name}.md and the corresponding ADRs in docs/adr/.
a6329c5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.