How this skill is triggered — by the user, by Claude, or both
Slash command
/plan-for-all:step-decompositionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
Split the detail plan into discrete sub-plans.
This skill is a strict splitter and copier. Its job is to completely copy the relevant phase from the detail plan into a separate subplan file without summarizing, compressing, or removing any information.
Step decomposition also carries forward full-lifecycle audit state. If execution still depends on unresolved terminology, external claims, or recheck-required knowledge, the subplan must keep that visible.
A step subplan should help an executor focus on a single phase of execution without losing any detail or context from the original plan.
If the subplan summarizes or omits details from the original phase, it failed.
task_plan.md and findings.md when relevantWrite to:
docs/plan-for-all/plans/step_subplans/step_subplan_phase{N}.mdEvery generated subplan must start with a TDD guard banner that uses the skill name, not a file path:
> Required Skill: Invoke plan-for-all:test-driven-development before executing the detailed steps below.This stage runs after writing-plans and before execution.
To avoid accidental summarization by free-form generation, prefer deterministic splitting with:
powershell -ExecutionPolicy Bypass -File plan-for-all/scripts/split-step-subplans-verbatim.ps1 -DetailPlanPath docs/plan-for-all/plans/YYYY-MM-DD-<topic>-detail.md
If deterministic generation is available, use it first and only do manual fallback when the script cannot run.
The subplan should mirror the structure of the phase exactly as it appears in the detailed plan, prefixed with the required metadata:
# Phase N: [Name] — Step Subplan
> Source: `docs/plan-for-all/plans/YYYY-MM-DD-<topic>-detail.md`
> Required Skill: Invoke `plan-for-all:test-driven-development` before executing the detailed steps below.
[Exact literal copy of the phase content from the detail plan]
Do not rewrite copied content into template fields such as objective, file list, baseline check, steps, or risks. The phase body must stay in its original structure and wording.
If a phase still depends on external knowledge, the subplan must show one of these states explicitly (copied from the detail plan):
verified_officialverified_recentunresolvedstale_recheck_requiredIf execution introduces a new suspicious term later, repair the plan and findings rather than quietly editing the subplan in isolation.
Before saving the subplan, verify:
plan-for-all:test-driven-development skill bannernpx claudepluginhub mengsi16/plan-for-all --plugin plan-for-allProduces bite-sized, executable implementation plans from PRDs or design specs. Each plan includes per-task Files blocks, complete code per step, and exact verification commands, rejecting placeholders like TBD or TODO.
Generates the next self-contained task file from a plan, with context, scope, acceptance criteria, and constraints. Tracks progress for sequential decomposition.
Creates structured implementation plans for multi-step tasks from specs or requirements. Generates plan.json and task markdown files with explicit code and testing steps.