Coordinate feature development from product direction through architecture, planning, validation, and implementation. Run the whole workflow or start at a selected stage, with saved decisions, review checkpoints, and a final pull request.
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.
Review the instructions the agent will receive before you install.
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)docs/plans/plan-{name}.md ceo-review
|
eng-review
|
start
|
validate
|
execute
Each 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/.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.