writing-plans

Plan multi-step coding tasks by generating a comprehensive implementation document that details every action, code touchpoints, test scaffolding, and commit strategy. This provides a complete blueprint to implement complex features safely.

A software implementation plan should include detailed file references, test scaffolding requirements, documentation updates, and version control steps. Structured plan documents ensure engineers capture all necessary code touchpoints.

Yes, you can generate engineering plans from existing specs when codebase context is limited. The planning process works directly with provided requirements to create thorough roadmaps for unfamiliar codebases.

The best way to document code touchpoints and commit strategy is creating a structured plan document saved to a standardized path like docs/plans/YYYY-MM-DD-feature-name.md, ensuring comprehensive implementation tracking.

Yes, structured plan writing works for complex tasks by covering the full engineering workflow from planning to validation. It documents test scaffolding and version control steps to satisfy structured work artifact requirements.