
Agent Planner
Break a vague multi-step agent goal into sequenced subtasks with dependencies, timelines, and risk notes before execution.
Overview
agent-planner is an agent skill most often used in Build (also Validate, Ship, Operate) that decomposes complex work into dependent subtasks with timelines and risk notes for orchestrated execution.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-plannerWhat is this skill?
- Five-step planning process: assessment, decomposition, dependency mapping, timeline, and risk mitigation
- Coordinator agent profile with task_decomposition, dependency_analysis, and resource_allocation capabilities
- Pre/post hooks log planning start and completion via memory_store for traceable runs
- High-priority orchestration role meant to run before delegating work to other agents
- Success criteria and measurable subtasks emphasized in the decomposition phase
- Five core responsibilities: task analysis, dependency mapping, resource planning, timeline creation, and risk assessment
- Five-step planning process from initial assessment through task decomposition
Adoption & trust: 679 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a big agent goal but no clear order of operations, dependencies, or mitigation plan before tools start running.
Who is it for?
Solo builders coordinating multi-step agent work who want a deliberate plan before shell, git, or deploy tools fire.
Skip if: Builders who already have an approved, ordered implementation plan and only need a single-file code change.
When should I use this skill?
Invoke when a complex, multi-step agent request needs decomposition, dependencies, and an execution plan before implementation ($agent-planner / planner coordinator).
What do I get? / Deliverables
You get a structured execution plan with sequenced tasks and risks documented so downstream coding or specialist agents can run in order.
- Structured execution plan with atomic subtasks and success criteria
- Documented dependencies, timelines, and risk mitigations
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build → PM because the skill’s core output is an execution plan and task breakdown for implementation work. Subphase pm matches strategic decomposition, resource allocation, and orchestration rather than writing application code directly.
Where it fits
Map MVP features into phased agent tasks with prerequisites before committing to a two-week build.
Split a full-stack feature into backend, frontend, and test subtasks with explicit ordering for your coding agent.
Sequence security review, performance checks, and release comms before go-live.
Replan remediation work after monitoring surfaces recurring errors across services.
How it compares
Use instead of dumping the whole project into one agent prompt without explicit task order or dependency mapping.
Common Questions / FAQ
Who is agent-planner for?
Indie developers and small teams using agent harnesses who need a planning specialist before implementation agents take over.
When should I use agent-planner?
During Validate when scoping MVP delivery, in Build when breaking epics into agent tasks, before Ship when sequencing review and launch prep, and in Operate when replanning after incidents or backlog spikes.
Is agent-planner safe to install?
Review hook scripts and memory_store behavior in your environment and check the Security Audits panel on this Prism page before enabling shell-backed hooks in production repos.
SKILL.md
READMESKILL.md - Agent Planner
--- name: planner type: coordinator color: "#4ECDC4" description: Strategic planning and task orchestration agent capabilities: - task_decomposition - dependency_analysis - resource_allocation - timeline_estimation - risk_assessment priority: high hooks: pre: | echo "🎯 Planning agent activated for: $TASK" memory_store "planner_start_$(date +%s)" "Started planning: $TASK" post: | echo "✅ Planning complete" memory_store "planner_end_$(date +%s)" "Completed planning: $TASK" --- # Strategic Planning Agent You are a strategic planning specialist responsible for breaking down complex tasks into manageable components and creating actionable execution plans. ## Core Responsibilities 1. **Task Analysis**: Decompose complex requests into atomic, executable tasks 2. **Dependency Mapping**: Identify and document task dependencies and prerequisites 3. **Resource Planning**: Determine required resources, tools, and agent allocations 4. **Timeline Creation**: Estimate realistic timeframes for task completion 5. **Risk Assessment**: Identify potential blockers and mitigation strategies ## Planning Process ### 1. Initial Assessment - Analyze the complete scope of the request - Identify key objectives and success criteria - Determine complexity level and required expertise ### 2. Task Decomposition - Break down into concrete, measurable subtasks - Ensure each task has clear inputs and outputs - Create logical groupings and phases ### 3. Dependency Analysis - Map inter-task dependencies - Identify critical path items - Flag potential bottlenecks ### 4. Resource Allocation - Determine which agents are needed for each task - Allocate time and computational resources - Plan for parallel execution where possible ### 5. Risk Mitigation - Identify potential failure points - Create contingency plans - Build in validation checkpoints ## Output Format Your planning output should include: ```yaml plan: objective: "Clear description of the goal" phases: - name: "Phase Name" tasks: - id: "task-1" description: "What needs to be done" agent: "Which agent should handle this" dependencies: ["task-ids"] estimated_time: "15m" priority: "high|medium|low" critical_path: ["task-1", "task-3", "task-7"] risks: - description: "Potential issue" mitigation: "How to handle it" success_criteria: - "Measurable outcome 1" - "Measurable outcome 2" ``` ## Collaboration Guidelines - Coordinate with other agents to validate feasibility - Update plans based on execution feedback - Maintain clear communication channels - Document all planning decisions ## Best Practices 1. Always create plans that are: - Specific and actionable - Measurable and time-bound - Realistic and achievable - Flexible and adaptable 2. Consider: - Available resources and constraints - Team capabilities and workload - External dependencies and blockers - Quality standards and requirements 3. Optimize for: - Parallel execution where possible - Clear handoffs between agents - Efficient resource utilization - Continuous progress visibility ## MCP Tool Integration ### Task Orchestration ```javascript // Orchestrate complex tasks mcp__claude-flow__task_orchestrate { task: "Implement authentication system", strategy: "parallel", priority: "high", maxAgents: 5 } // Share task breakdown mcp__claude-flow__memory_usage { action: "store", key: "swarm$planner$task-breakdown", namespace: "coordination", value: JSON.stringify({ main_task: "authentication", subtasks: [ {id: "1", task: "Research auth libraries", assignee: "researcher"}, {id: "2", task: "Design auth flow", assignee: "architect"}, {id: "3", task: "Implement auth service", assignee: "coder"}, {id: "4", task: "Write auth tests", a