auto-plan
Breaks approved project specifications into actionable, ordered execution slices.
Install
mkdir -p .claude/skills/auto-plan && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12995" && unzip -o skill.zip -d .claude/skills/auto-plan && rm skill.zipInstalls to .claude/skills/auto-plan
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Turn an approved spec into ordered slices. Use when framing is accepted and planning begins.Key capabilities
- →Load SPEC.md, DESIGN.md, and relevant source files for planning
- →Address approved_with_risks risks from product reviews in the plan
- →Preserve requirement IDs, gap IDs, invariants, and audit questions in PLAN.md
- →Break work into ordered, testable, bounded, and independent execution units
- →Attach a verification command and acceptance criteria to every material slice
- →Update state with canonical_plan and stage: plan
How it works
The skill loads approved specifications and related documents, assesses review states, and designs ordered, testable slices with verification commands, then updates the project state.
Inputs & outputs
When to use auto-plan
- →Plan project implementation
- →Slice requirements into tasks
- →Define execution order
- →Add verification commands
About auto-plan
Builds a safe, compact plan of execution, attaching verification commands to each slice to ensure progress tracking.
Turn an approved spec into ordered slices. Use when framing is accepted and planning begins.
When not to use it
- →When SPEC.md is missing or unreadable
- →When product_review is descoped or needs_clarification
- →When the scope is still ambiguous after reading SPEC.md
Limitations
- →Does not write code
- →Does not broaden scope beyond the approved spec
- →Does not write PLAN.md if SPEC.md is missing or unreadable
How it compares
This skill systematically structures an approved spec into concrete, verifiable execution slices with explicit dependencies and checkpoints, which is more structured than ad-hoc task breakdown.
Compared to similar skills
auto-plan side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| auto-plan (this skill) | 0 | 3mo | No flags | Advanced |
| create-plan | 36 | 9mo | Review | Beginner |
| project-planner | 32 | 11mo | Review | Intermediate |
| system-design | 19 | 10mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by appautomaton
View all by appautomaton →You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.