planning-and-task-breakdown

Decompose specifications into atomic TDD tasks with acceptance criteria and dependency ordering.

9|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/jerrylin96/dotgemini --skill planning-and-task-breakdown-jerrylin96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/jerrylin96/dotgemini/tree/main/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/jerrylin96/dotgemini --skill planning-and-task-breakdown-jerrylin96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large feature requests and specs are hard to start, easy to scope-creep, and often get implemented without tests or verification. This Skill turns a specification into granular, verifiable units of work with explicit test-first steps and a mandatory human approval gate before any code is written. ## Core Features & Use Cases - Atomic Task Decomposition: Breaks objectives into tasks touching roughly five files or fewer, each with a RED test spec, GREEN implementation target, and an exact verify command. - Execution Strategy Selection: Declares either Standard Single Agent or Sequential Subagents execution, with per-slice adversarial review gates in heavy mode. - Human Approval Gate: Produces a reviewable plan document (e.g. plan.md in the make-feature worktree) and pauses until the engineer explicitly approves it. - Use Case: Given a spec for a new API endpoint, generate an ordered checklist of TDD tasks where each task names the failing test to write, the minimal implementation, and the exact pytest command to verify it. ## Quick Start Ask the agent to run /plan on your feature specification to produce an ordered, test-driven task breakdown for approval before coding begins.

Frequently Asked Questions about planning-and-task-breakdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a large feature spec into implementable tasks?

Use the /plan workflow to decompose the spec into atomic tasks of roughly five files or fewer each. Every task must specify a RED failing test, a GREEN minimal implementation, and an exact verify command, ordered by dependency.

What is the TDD task schema required in each plan task?

Each task must define three elements: a RED test spec naming the target test file and failing assertion, a GREEN implementation target with minimal code to pass, and an exact empirical verify command such as a pytest invocation.

When should I use Sequential Subagents instead of a single agent?

Choose Sequential Subagents when the breakdown contains five or more complex multi-file slices, or when handing off an external plan. Each slice then passes adversarial test and code review gates with a two-stage commit cadence.

Can I start coding before the plan is approved?

No. The process enforces a hard pause after the plan document is written, and code is only written after the human engineer explicitly approves the audited plan at the make-feature Step 3c gate.

When should I skip formal task breakdown planning?

Skip it for simple single-file changes where the scope is already obvious. The skill is designed for non-trivial work needing decomposition, parallelization, or scope communication.