writing-plans

To create an implementation plan, decompose complex features into structured tasks covering file paths, testing steps, and commit guidelines before writing code. This structured task decomposition eliminates ambiguity and rework.

The best way to document onboarding plans is using repeatable plan templates that specify exact file modifications, tests to write, and documentation updates. This yields a complete plan you can hand to any developer.

Yes, you need a completed spec before generating an implementation plan. This skill applies to scenarios where a spec exists but code has not yet been written, guiding file changes and testing across repositories.

Structure file changes and testing steps in project documentation by generating structured plan artifacts saved as markdown files. These artifacts include specific file paths, task breakdowns, testing steps, and clear commit guidelines.

Yes, you can use this planning approach for features spanning multiple repositories. It guides file changes, testing steps, and documentation updates across repositories to ensure comprehensive multi-step task coverage.