From forge
Use when an approved spec exists and needs to be decomposed into executable tasks with verification criteria. Phase: PLANNING.
npx claudepluginhub caseyrtalbot/forge --plugin forgeThis skill uses the workspace's default tool permissions.
Decompose an approved spec into an ordered list of small, independently executable tasks. Each task must be specific enough that an agent with no project context can execute it, and must include verification criteria so completion is provable.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Decompose an approved spec into an ordered list of small, independently executable tasks. Each task must be specific enough that an agent with no project context can execute it, and must include verification criteria so completion is provable.
Every task in the plan MUST have: 1. A clear description of what to do (not vague like "implement the feature") 2. Specific file paths that will be created or modified 3. Verification criteria (how to prove the task is done -- a test command, a build check, etc.) 4. No placeholders. Every step must include complete code or commands. See `placeholder-rules.md` for forbidden patterns. A plan with any task missing verification criteria is not complete and cannot be executed.digraph chart_tasks {
"Read approved spec" [shape=box];
"Identify components" [shape=box];
"Map dependencies" [shape=box];
"Break into tasks" [shape=box];
"Add verification to each" [shape=box];
"Order by dependencies" [shape=box];
"Self-review plan" [shape=box];
"Write plan to file" [shape=box];
"Present plan to user" [shape=box];
"User approves plan?" [shape=diamond];
"Revise plan" [shape=box];
"Invoke drive-execution" [shape=doublecircle];
"Read approved spec" -> "Identify components";
"Identify components" -> "Map dependencies";
"Map dependencies" -> "Break into tasks";
"Break into tasks" -> "Add verification to each";
"Add verification to each" -> "Order by dependencies";
"Order by dependencies" -> "Self-review plan";
"Self-review plan" -> "Write plan to file";
"Write plan to file" -> "Present plan to user";
"Present plan to user" -> "User approves plan?";
"User approves plan?" -> "Invoke drive-execution" [label="yes"];
"User approves plan?" -> "Revise plan" [label="no"];
"Revise plan" -> "Write plan to file";
}
docs/forge/plans/YYYY-MM-DD-<topic>-plan.md### Task N: [Title]
**Description**: [What to do, specifically]
**Files**: [Paths to create/modify]
**Depends on**: [Task numbers, or "none"]
**Parallel**: [Can run with tasks X, Y]
**Verification**: [Command to run or condition to check]
"This task is: implement the authentication system" Too large. Break it down. "Create the User model with email and hashed_password fields" is a task. "Implement authentication" is a project.
"Verification: it works"
Not a criterion. "Run npm test -- --grep auth and all tests pass" is verification. "It works" is a wish.
"I'll figure out the order during execution" Dependencies discovered during execution cause rework. Map them now when the cost of changing course is zero.
When the plan is complete and the user has approved it, invoke drive-execution to begin task implementation.