writing-plans

To draft an implementation plan for a multi-phase refactoring project, you need a structured document outlining the problem, current state, goals, and phased execution. This skill generates a plan with PR-scoped phases, dependency ordering, and risk mitigation strategies.

The required format for SCT repository documentation roadmaps is a mandatory 7-section structure saved in the docs/plans/ directory. This structure ensures all complex feature designs include problem background, goals, phased implementation, testing requirements, and risk mitigation.

Breaking down complex feature designs into single Pull Request phases requires mapping dependency ordering and scoping changes to manageable units. This skill automates that phasing process, ensuring each PR phase aligns with the overarching SCT implementation plan and testing requirements.

You need a structured implementation plan for SCT repository changes when undertaking multi-phase modifications, refactoring strategies, or complex feature designs. These documented roadmaps ensure project management clarity and coordinate dependency ordering across extensive codebase updates.

Yes, the implementation plan generator includes risk mitigation and testing requirements as mandatory components. It integrates these elements into the 7-section format to ensure complex refactoring strategies and feature designs are thoroughly documented against potential project risks.

The best way to document a refactoring strategy for a testing framework is using a standardized 7-section plan format. This approach structures the current state, goals, and implementation phases while enforcing PR-scoped changes and comprehensive testing requirements.