writing-plans

To write an implementation plan, break down requirements into discrete tasks and map them to specific files, tests, and verification steps before coding begins. This structured planning ensures stakeholders agree on the scope and acceptance criteria.

Documenting project management plans involves generating consistent plan templates that include a structured header, task structure, and acceptance criteria. This approach organizes cross-team scope and multi-subsystem requirements into a clear, referenceable format.

Yes, structured planning docs support cross-team software engineering workflows by guiding task breakdown and file changes. They provide a disciplined workflow that supports creating isolated plan documents in dedicated worktrees.

You map file changes and tests by applying a structured file-level task template during the planning phase. This template guides step-by-step execution and defines clear verification steps for each development task.

You should save generated implementation plans to the docs/superpowers/plans/ directory. Saving them to this standard location ensures the reference documentation is consistently accessible for guided execution and stakeholder review.