plan-writing

To turn feature specifications into implementation plans, provide the feature spec to generate a detailed breakdown of atomic steps, risks, dependencies, and acceptance criteria. This reduces ambiguity by decomposing work into testable tasks and mapping dependencies.

Mapping dependencies and risks during migration planning involves sequencing tasks and surfacing potential blockers. The generated implementation plan enforces dependency mapping and risk identification to align stakeholders and ensure smooth coordination across components.

Breaking down a large refactor into atomic, testable steps requires decomposing the scope into small, independent tasks. The plan enforces step decomposition, defines milestones tied to acceptance criteria, and establishes checkpoints to trace progress back to requirements.

Yes, generating rollback strategies and checkpoints is supported during feature planning. The plan defines specific milestones for validation and includes rollback strategies to mitigate risks, ensuring traceability back to the original requirements.

Implementation planning works for coordinating work across multiple components by mapping dependencies and sequencing tasks. It aligns stakeholders by providing a structured breakdown of work, owners, success criteria, and traceability to requirements.