Create a structured task_plan.md with phases, goals, and checkbox tracking for persistent planning.
Scanned 5/29/2026
Install to Claude Code
Skills Directorynpx -y skills add a5c-ai/babysitter --skill plan-creation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Plan Creation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-plan-creation)More formats (shields.io, HTML) on the badges page.
# Plan Creation
Create a structured task_plan.md with phases, goals, and checkbox tracking for persistent planning.
## Agent
Plan Architect - `pwf-plan-architect`
## Workflow
1. Analyze task description to identify logical phases
2. Decompose phases into specific, achievable goals
3. Define phase dependencies and review gates
4. Generate task_plan.md with markdown checkbox format
5. Validate plan completeness and goal coverage
6. If recovering, merge with existing plan state
## Inputs
- `taskDescription` - Description of the task to plan
- `projectPath` - Root path for planning files
- `recoveredState` - Previous session state (optional)
- `customPhases` - Custom phase names (optional)
## Outputs
- task_plan.md with phases, goals, and checkboxes
- Plan object with phase count, total goals, summary
## Process Files
- `planning-orchestrator.js` - Phase 1 plan creation
- `planning-session.js` - Three-file pattern initialization
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
