planning-workflow

Produces pre-implementation plans through a seven-step workflow with adversarial critique scoring.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill planning-workflow-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-workflow
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-core/skills/planning-workflow
Command: npx skills add https://github.com/toderian/project_template --skill planning-workflow-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Non-trivial code changes often start without a grounded plan, leading to scope creep, rebuilt existing solutions, and wrong approaches discovered only after code is written. This Skill structures the planning phase so weak plans are caught and revised before implementation begins. ## Core Features & Use Cases - Seven-step planning workflow: problem statement, scope check with a halt rule, existing-solutions search, minimal path design, adversarial critique, decomposition, and durable plan output. - Five-axis critique rubric: scores plans on assumption audit, scope creep, existing solutions, minimalism, and uncertainty, issuing PROCEED, REVISE, or BLOCKED verdicts with evidence-based justifications. - Tracer-bullet vertical slicing: breaks PRDs into end-to-end slices cutting through schema, API, UI, and tests, with an expand-migrate-contract pattern for wide refactors. - Use Case: Given a PRD for a new feature, produce a phased plan where each phase is an independently shippable vertical slice, critiqued against the rubric before any code is written. ## Quick Start Ask the agent to plan a non-trivial change before writing code, for example: plan the implementation of this PRD using the planning workflow and critique the plan before we start.

Frequently Asked Questions about planning-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a code change before writing code?

Follow the seven-step workflow: write a problem statement with explicit out-of-scope items, estimate affected files, search for existing solutions, design the minimal path, run the adversarial critique, decompose into phases if needed, and write the plan to docs/_plans/<slug>.md.

How do I break a PRD into implementation phases?

Use tracer-bullet vertical slicing: each phase cuts through all integration layers (schema, API, UI, tests) for one thin piece of user-visible behavior. Present the phase list to the user for merge or split approval before writing the plan file.

What is the plan critique rubric and how are verdicts decided?

Plans are scored 1-5 on five axes: assumption audit, scope creep, existing solutions, minimalism, and uncertainty. A composite of 3.0 or higher with no axis below 2 yields PROCEED; below 3.0 or any axis at 1 yields REVISE; below 2.0 or two axes at 1 yields BLOCKED.

When should I skip the formal planning workflow?

Skip it for single-file changes under roughly 50 lines, mechanical edits like renames or dependency bumps, and work already covered by an existing plan or task. Skipping silently on non-trivial changes is not acceptable.

How do I handle a wide refactor that cannot fit a vertical slice?

Sequence it as expand, migrate, contract: add the new form beside the old, migrate call sites in batches sized by blast radius, then delete the old form once no callers remain. If batches cannot stay green, share an integration branch with a final verify slice.