writing-plans

An implementation plan decomposes a spec into bite-sized tasks that map directly to code, tests, docs, and commits. It provides a clear, auditable blueprint with precise file paths and validation steps that a junior engineer can follow and a reviewer can validate.

Task decomposition works by breaking a spec into concrete tasks with precise file paths, expected changes, and test coverage. It delivers a context-rich Markdown plan with per-task steps, test instructions, and explicit validation requirements to guide implementation.

Yes, generating a plan with exact file paths and test instructions is the core function. It applies to brainstorming contexts where a spec exists, producing a comprehensive Markdown plan with per-task steps, exact file paths, test and commit instructions, and explicit validation requirements.

Yes, implementation planning applies directly to brainstorming contexts where a spec exists. It produces a comprehensive, executable implementation plan with bite-sized tasks that map to code, tests, docs, and commits, ensuring a smooth build process.

The primary limitation is that a project spec must already exist before decomposition can occur. The skill automates turning specs into plans, so without an initial spec, it cannot generate the per-task steps, file paths, and test instructions needed for implementation.