implementation-plan

An implementation plan breaks development into sequenced phases with actionable tasks. This Skill generates phased plans that organize feature work across backend, frontend, and design, marking the first phase as in_progress and subsequent phases as pending, with full code blocks for novel aspects and reference patterns for established implementations.

Implementation plans document novel code with complete blocks and reference established patterns by name. This Skill creates task-level breakdowns that cite existing patterns while providing full code examples for new functionality, ensuring developers have concrete guidance for both custom and standard implementations.

Phase breakdown sequences work logically across layers—typically backend foundation, frontend integration, and design refinement. This Skill structures three-phase TODO-driven plans with cross-references to vision, requirements, and spec documents, establishing clear dependencies and task ordering.

Implementation plans work for projects requiring coordination across backend, frontend, and design teams. This Skill generates structured phases with task checklists that integrate these disciplines, supporting parallel work streams and clear handoff points between phases.

Implementation plans suit complex features needing phase sequencing, task interdependencies, and code guidance. Use plans when a feature spans multiple layers or requires referencing existing patterns alongside new implementations, rather than flat task lists.

Requirements specify what to build; implementation plans specify how and when. This Skill cross-references requirements documents while adding phase structure, task breakdown, code examples, and sequencing—transforming what into an actionable development roadmap.