implementation-plan

To turn an approved task analysis into a ready-to-code design, provide the completed task context and chosen solution to generate implementation-plan.md and coding-task.md files in your tmp/tasks directory. This validates code, tests, and schema references for a clean development handoff.

The best way to create implementation handoff artifacts from a task context is to transform the completed task.md and chosen solution into structured planning outputs. This process revalidates codebase configurations and writes ready-to-implement designs into the tmp/tasks/<task-name>/ folder.

Yes, you need a completed task.md file and a chosen solution within a Cursor task context before generating an implementation plan. The process requires an approved task analysis to revalidate existing code, tests, and schemas before writing the final planning artifacts.

Task analysis validation works by re-verifying existing code, tests, configs, and schema references against the approved task context. This enforces guardrails during the transition from planning to implementation, reducing ambiguity before writing the coding-task.md output.

No, you cannot generate planning outputs without researching the codebase. Codebase research is required to revalidate code, tests, and configurations, ensuring the generated implementation-plan.md and coding-task.md accurately reflect the technical environment.

The generated implementation plan and coding task files are written directly into the existing tmp/tasks/<task-name>/ folder. They are saved as implementation-plan.md and coding-task.md to facilitate a clean handoff between analysis and development.