writing-plans

To create an implementation plan, you provide a project spec and the skill outputs a structured, task-by-task breakdown with explicit file paths, testing instructions, and acceptance criteria for smooth handoffs.

Breaking down a large project into bite-sized tasks involves outlining specific steps, files, tests, and documentation, which this skill automates to ensure deterministic execution and smooth team knowledge transfer.

Planning a multi-agent workflow requires generating detailed task-oriented implementation plans with explicit task granularity and file-path specificity, allowing you to distribute bite-sized actions across multiple agents effectively.

Yes, you can generate test scaffolding and documentation guidance directly from a project spec, as the skill outlines specific testing instructions and documentation requirements alongside each implementation step.

Yes, this implementation planning approach works for design reviews and team handoffs by providing comprehensive, actionable task breakdowns that make cross-team knowledge transfer smooth and deterministic.

You need an automated task breakdown when starting a new feature with many moving parts and uncertain context, ensuring all steps, files, tests, and commit history discipline are explicitly mapped.