writing-plans

To break complex software features into bite-sized tasks, create a structured implementation plan that specifies exact file paths, complete code samples, commands, and verification steps. This ensures each task is 2-5 minutes of work with minimal scope for deterministic handoffs and faster delivery.

An implementation plan document is a standardized structure with a header, task steps, and clear success criteria. You need it for multi-step features, large refactors, and delegated work across teams to ensure traceability and testability throughout the software development workflow.

Plan a large code refactor by generating a structured plan document that breaks the work into 2-5 minute bite-sized tasks. Each task must include explicit files to touch, complete code samples, commands, and verification steps to guarantee reproducibility and deterministic execution handoffs.

Yes, this planning workflow supports delegation to subagents and delegated work across teams. It enables deterministic handoffs by providing exact artifacts like precise file paths, complete code samples, and verification steps, along with two-stage reviews and plan saving to docs/plans.

The best way to structure task documentation is using a standardized plan with a header, bite-sized task steps, and clear success criteria. It must require exact file paths, complete code samples, commands, and verification steps to ensure reproducibility and traceability for multi-step features.

Yes, this implementation planning method works without external dependencies. It focuses on generating structured plan documents with exact artifacts and bite-sized tasks, relying solely on the software development workflow itself rather than requiring additional tools or components.