task-planner
Transforms ambiguous goals into structured, verified development plans.
Install
mkdir -p .claude/skills/task-planner-s-hiraoku && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14746" && unzip -o skill.zip -d .claude/skills/task-planner-s-hiraoku && rm skill.zipInstalls to .claude/skills/task-planner-s-hiraoku
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.
Guide for decomposing large tasks into a structured plan with dependency chains, managing priorities, and distributing work across agents. Outputs plan cards or delegation messages as the team contract; TodoList for personal micro-steps.Key capabilities
- →Decompose large tasks into structured plans
- →Identify dependencies and prioritize work
- →Define clear deliverables for multi-agent assignments
- →Create plan cards for visual tracking
- →Generate TodoLists for personal micro-steps
- →Provide clear status updates for progress reporting
How it works
This skill decomposes large requests into smaller, mergeable slices, identifies dependencies, and defines deliverables for multi-agent work. It can output plan cards or TodoLists.
Inputs & outputs
When to use task-planner
- →Plan new features
- →Break down large tasks
- →Delegate tasks to agents
About this skill
Task Planner
This skill helps you turn ambiguous or large requests into a clear, sequenced plan with ownership and verification.
Outputs To Produce
- A short problem statement
- Assumptions and open questions
- A step-by-step plan with measurable outcomes
- Risks and rollback/containment options
- Test and verification steps
Decomposition Technique
Split work into thin vertical slices:
- One slice should be mergeable on its own
- Each slice should include tests or validation
- Prefer smallest unit that reduces uncertainty
Common slice types:
- Spec tests (lock requirements, CLI flags, edge cases)
- Implementation changes (small, isolated)
- Documentation updates
- Observability and traceability improvements
Dependency And Priority Rules
- Identify blockers first (missing API, failing tests, permissions).
- Order by "unblocks others" and "reduces uncertainty".
- For multi-agent work, keep interfaces stable and define contracts (inputs/outputs) per slice.
Multi-Agent Assignment
When delegating:
- Specify the exact deliverable (files, tests, output format)
- Specify constraints (no commits, branch constraints, time limits)
- Specify the acceptance test (what must pass)
Example delegation message:
Please write tests for <feature>.
Constraints:
- Do not change implementation yet
- Use pytest
Acceptance:
- Tests fail before implementation
- Tests cover edge cases: <...>
Plan Output
Plan Card Output (Canvas)
For visual plans with Mermaid DAG visualization and step-level status tracking, post a plan card to Canvas:
# Post plan card with Mermaid DAG and step list
synapse canvas plan '{"plan_id":"plan-auth","status":"proposed","mermaid":"graph TD; A[Tests]-->B[Impl]-->C[Review]","steps":[{"id":"s1","subject":"Write auth tests","agent":"Tester","status":"pending"},{"id":"s2","subject":"Implement auth","agent":"Impl","status":"pending","blocked_by":["s1"]},{"id":"s3","subject":"Review","agent":"Tester","status":"pending","blocked_by":["s2"]}]}' --title "Auth Plan"
Plan cards are useful when the decomposition should be visible to the team in the Canvas dashboard. Use plan cards for plans with 3+ steps or complex dependency chains that benefit from DAG visualization.
TodoList for Personal Micro-Steps
Use a TodoList for your own micro-step tracking within a single task. TodoList items are fine-grained (one per coding step):
- Add failing tests for <behavior>
- Implement <behavior> behind tests
- Run targeted tests
- Update docs
- Run full test suite
Progress Reporting
Include clear status updates in all communications:
- Done:
"Write auth tests complete — 4 tests passing" - Next:
"Starting Implement auth module; tests are confirmed" - Blocked:
"Integration test waiting — implementation not yet complete"
When not to use it
- →When the request is already a small, well-defined task
- →When the user does not need a structured plan or delegation
- →When the task does not involve decomposition or multi-agent work
Limitations
- →The skill focuses on decomposition and planning, not execution
- →Plan cards are useful for plans with 3+ steps or complex dependency chains
- →TodoList is for personal micro-step tracking within a single task
How it compares
This skill provides a structured decomposition technique and specific output formats for planning, unlike an unstructured or manual task breakdown.
Compared to similar skills
task-planner side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| task-planner (this skill) | 0 | 4mo | Review | Intermediate |
| create-plan | 36 | 8mo | Review | Beginner |
| project-planner | 32 | 10mo | Review | Intermediate |
| system-design | 19 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by s-hiraoku
View all by s-hiraoku →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.