writing-plans

To turn vague requirements into actionable implementation plans, provide your feature specifications to generate a step-by-step breakdown including files to touch, tests to write, and commit guidance for zero-context handoffs.

Documenting end-to-end engineering tasks for cross-functional collaboration involves creating a structured plan with file paths, testing steps, and milestones, saving it to .docs/plans with a date-based filename for traceability.

Structure an implementation plan by detailing concrete tasks that specify files touched, tests to write, documentation references, and commit notes, enabling structured planning for features, fixes, and experiments.

Yes, you can save generated implementation plans to a specific file path. The skill automatically saves plans to .docs/plans/YYYY-MM-DD-<feature-name>.md format to ensure consistency and traceability across projects.

Yes, generating implementation plans requires running in a dedicated task context to prevent cross-project leakage, ensuring the documented steps and file paths remain isolated to the specific feature.