From cc-setup
Create a hierarchical multi-phase project plan optimized for solo agentic development. Supports brief, roadmap, and phase-plan types. Each task is scoped for a single agent session. Saves to ./plans/YYMMDD-HHMM-slug/.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cc-setup:create-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build a hierarchical project plan saved to disk before any implementation begins.
Build a hierarchical project plan saved to disk before any implementation begins.
Classify as one of:
If ambiguous, ask: "Brief, roadmap, or phase-plan?"
Restate the goal in one sentence. Identify what is in scope, out of scope, and key constraints.
Phase N: <Name>
Goal: <What this phase achieves>
Tasks:
N.1 <Task> → output: <artifact>
N.2 <Task> → output: <artifact>
Dependencies: Phase X must complete first
Effort: S / M / L
Validation gate: <What must be true before next phase>
Rules for tasks:
Always end with a Functional Validation phase:
Phase N: Functional Validation
Tasks:
N.1 Build / start the real system
N.2 Exercise through actual interface (CLI, UI, API)
N.3 Capture evidence (screenshot, log, response)
N.4 Confirm evidence matches success criteria
Validation gate: Evidence captured and all success criteria met
No unit tests. No mocks. Real system only.
Save overview to ./plans/YYMMDD-HHMM-<slug>/plan.md.
For roadmap and phase-plan, also save ./plans/YYMMDD-HHMM-<slug>/phase-NN-<name>.md per phase.
Output the full plan, then end with:
Plan saved to: ./plans/YYMMDD-HHMM-<slug>/
CONFIRM to proceed, or tell me what to change.
Do not write code or take any implementation action until the user confirms.
## Project: <Name>
**Type:** brief | roadmap | phase-plan
**Goal:** <one sentence>
**In scope:** ... | **Out of scope:** ... | **Constraints:** ...
## Success Criteria
- [ ] ...
## Phases
### Phase 1: <Name>
**Goal:** ... | **Effort:** S/M/L | **Dependencies:** none
1.1 ... → output: ...
**Validation gate:** ...
### Phase N: Functional Validation
...
## Dependency Map
Phase 2 → requires Phase 1
## Effort Summary
Total: ~X days
npx claudepluginhub krzemienski/cc-setup --plugin cc-setupGenerates structured phased implementation plans from feature descriptions, sized for 30-50k token sub-agent contexts, with clarifying questions, acceptance criteria, and dependencies. Invoke before multi-phase execution.
Generates executable Markdown implementation plans for multi-step tasks from context briefs, resolving ambiguities, ordering dependencies, and enabling parallel worker execution.
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.