writing-plans

To generate an implementation plan from a vague specification, this Skill converts the spec into concrete, bite-sized tasks. It details specific file paths, tests, commands, and acceptance criteria to ensure structured, actionable outputs.

The best way to break down software engineering tasks for team handoffs is to produce detailed, testable implementation plans. This Skill structures work into explicit, bite-sized steps with defined file layouts and verification commands for cross-team collaboration.

Yes, you can use this for multi-step feature planning and onboarding. It generates end-to-end implementation plans that outline tasks, file layouts, tests, and verification steps, making it highly useful for bringing new team members up to speed.

Implementation plan generation does include specific tests and commands. It breaks work into bite-sized tasks that explicitly detail file paths, test cases, and commands, ensuring reproducibility and auditability for your software-engineering workflow.

Planning complex work from specs improves auditability by producing structured, testable implementation plans. It emphasizes reproducible outputs with clear tasks, files, and steps, ensuring that every phase of the software-engineering workflow can be tracked and reviewed.

Vague specs lead to poor task breakdown because they lack actionable detail. This Skill solves that by converting abstract specifications into detailed, bite-sized implementation tasks with explicit file paths, tests, and commands for clear execution.