tech-dev-writing-plans

To generate an implementation plan from a feature spec, provide the spec to the skill to produce bite-sized tasks specifying files to touch, tests to write, and commits to make. The plan is saved as a version-controlled document under docs/plans.

The best way to break down multi-step software development tasks is creating an executable implementation plan with task-focused steps. This approach specifies file touchpoints, testing requirements, and commits to structure the work before coding begins.

Yes, you need a clear product spec or requirements document to create a task breakdown. The skill translates this spec into a repeatable, version-controlled plan document to guide the implementation process.

Version control applies to software development plans by saving generated documents under docs/plans with a dated naming convention. This creates a repeatable, versioned record of the implementation strategy for team collaboration and handoffs.

Yes, you can use this planning approach with little codebase context. It is specifically designed for software development tasks requiring multi-step planning, generating executable plans that detail exact file touchpoints and testing steps.

A limitation when generating implementation plans is that the output relies entirely on the clarity of the provided spec. Without a clear spec, the skill cannot produce a structured, executable plan with accurate file touchpoints and testing requirements.