project-planning

Create a step-by-step implementation plan by researching existing code patterns, identifying affected files and dependencies, then structuring work into 3–5 independently testable phases. Each phase includes acceptance criteria, estimates, and a consolidated plan.md documenting context, risk matrix, and dependency order.

A structured plan translates goals into phases, tasks, and measurable acceptance criteria. This Skill generates a consolidated plan.md with functional requirements, code patterns, phase templates, risk multipliers, time estimates, and a dependency map for build sequencing.

Apply estimating techniques with risk multipliers to each phase. This Skill analyzes your codebase patterns, breaks work into independently testable components, and produces a risk matrix showing impact and mitigation alongside phase-level estimates and dependencies.

Yes. This Skill researches existing code patterns and dependencies within your codebase, identifies affected files, and creates a structured 3–5 phase plan with acceptance criteria and a dependency map tailored to your project's architecture.

Consolidate all phases, acceptance criteria, estimates, and dependencies into a single plan.md file. This Skill generates that documentation with a dependency map showing which phases block others, enabling teams to execute work in the correct sequence.

This Skill handles technical analysis—researching code patterns, identifying dependencies, and mapping affected files. You provide the goal; the Skill produces phase breakdowns, acceptance criteria, estimates, and a risk matrix ready for team review and execution.