Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →florianbruniaux/plan-pipeline-start
5-phase planning: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
Passed 17 of 23 test cases with the skill, and 7 of 23 without it.
and 9 more in the full report
10 fixed7 passed either way6 still failing0 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to fix a minor typo in the copyright footer text of components/Footer.tsx. Which mode or command should we use for this single-file change, and should we execute the full 5-phase research agent pipeline?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the user to use standard /plan mode rather than the multi-phase pipeline for simple single-file edits. | Missed | Passed |
| Recommends against spawning research agents for minor editorial changes. | Passed | Passed |
The instructions your model reads when the skill loads.
Analyze the request and produce a complete implementation plan through structured phases. No code is written. Every significant decision is recorded. Run /clear after this command before running /plan-pipeline:validate.
Skip if no PRD exists (refactor, infra change, bug fix).
Read all PRD files and docs/INFORMATION_ARCHITECTURE.md if present. Scan the codebase to understand current implementation status.
Surface findings in 3 buckets:
Missing requirements: acceptance criteria that are absent or incomplete Ambiguous requirements: items with multiple valid interpretations Compliance concerns: security, data privacy, API contract implications
For each finding: present options with concrete pros/cons. Discuss with user. Record every decision in the plan file under a ## Decisions section before moving on. Do not proceed past unresolved ambiguities.
Skip if no UI changes are in scope.
Read: DESIGN_SYSTEM.md, existing UX ADRs, CLAUDE.md UX rules.
Produce specs for:
prefers-reduced-motion fallbacksCreate Design ADRs for significant UX decisions (choice of interaction pattern, new animation convention, platform divergence). Record minor layout choices directly in the plan file.
test cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.