agent-planner
Skill1 starsChanged 3 months agoMITView on GitHub
Agent skill for planner - invoke with $agent-planner
6 other projects use a version of this, 1 of them edited.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- ruvnet/rufloword for word, first seen Oct 21, 2026
- ruvnet/claude-flowword for word, first seen Oct 8, 2026
- edisonzerolam/openclaw-skillstheir own version, first seen Jul 4, 2026
- jpoindexter/theft-kitword for word, first seen May 20, 2026
- fidgetcoding/fidgetfloedited, first seen Apr 17, 2026
- Zekiog/rufloword for word, first seen Apr 8, 2026
Other versions6 projects use a version of this.
Word for word · 4
- ruvnet/claude-flow★ 80k100% same
- ruvnet/ruflo★ 79k100% same
- Zekiog/ruflo★ 2100% same
- jpoindexter/theft-kit★ 1100% same
Edited · 1
- fidgetcoding/fidgetflo★ 197% same
Wrote their own version · 1
- edisonzerolam/openclaw-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository176 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/commands/monitoring/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- v3/CLAUDE.mdCLAUDE.md
- agent-adaptive-coordinatorSkill
- agent-agentic-paymentsSkill
- agent-agentSkill
- agent-analyze-code-qualitySkill
- agent-app-storeSkill
- agent-architectureSkill
- agent-arch-system-designSkill
- agent-authenticationSkill
- agent-automation-smart-agentSkill
- agent-base-template-generatorSkill
- agent-benchmark-suiteSkill
- agent-byzantine-coordinatorSkill
- agent-challengesSkill
- agent-code-analyzerSkill
- agent-code-goal-plannerSkill
- agent-code-review-swarmSkill
- agent-coderSkill
- agent-collective-intelligence-coordinatorSkill
- agent-consensus-coordinatorSkill
- agent-coordinationSkill
- agent-coordinator-swarm-initSkill
- agent-crdt-synchronizerSkill
- agent-data-ml-modelSkill
- AgentDB Advanced FeaturesSkill
- AgentDB Learning PluginsSkill
- AgentDB Memory PatternsSkill
- AgentDB Performance OptimizationSkill
- AgentDB Vector SearchSkill
- agent-dev-backend-apiSkill
- agent-docs-api-openapiSkill
- agent-github-modesSkill
- agent-github-pr-managerSkill
- agent-goal-plannerSkill
- agent-gossip-coordinatorSkill
- agent-hierarchical-coordinatorSkill
- agentic-jujutsuSkill
- agent-implementer-sparc-coderSkill
- agent-issue-trackerSkill
- agent-load-balancerSkill
- agent-matrix-optimizerSkill
- agent-memory-coordinatorSkill
- agent-mesh-coordinatorSkill
- agent-migration-planSkill
- agent-multi-repo-swarmSkill
- agent-neural-networkSkill
- agent-ops-cicd-githubSkill
- agent-orchestrator-taskSkill
- agent-pagerank-analyzerSkill
- agent-paymentsSkill
- agent-performance-analyzerSkill
- agent-performance-benchmarkerSkill
- agent-performance-monitorSkill
- agent-performance-optimizerSkill
- agent-pr-managerSkill
- agent-production-validatorSkill
- agent-project-board-syncSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Ensure each task has clear inputs and outputs
- Distinctive: line 49
Create logical groupings and phases
- Distinctive: line 97
Update plans based on execution feedback
- Distinctive: line 99
Document all planning decisions
- Distinctive: line 103
Always create plans that are:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Task Analysis: Decompose complex requests into atomic, executable tasks
- Dependency Mapping: Identify and document task dependencies and prerequisites
- Resource Planning: Determine required resources, tools, and agent allocations
- Timeline Creation: Estimate realistic timeframes for task completion
- 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:
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
- Always create plans that are:
- Specific and actionable
- Measurable and time-bound
- Realistic and achievable
- Flexible and adaptable
- Consider:
- Available resources and constraints
- Team capabilities and workload
- External dependencies and blockers
- Quality standards and requirements
- Optimize for:
- Parallel execution where possible
- Clear handoffs between agents
- Efficient resource utilization
- Continuous progress visibility
MCP Tool Integration
Task Orchestration
// 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", assignee: "tester"}
],
dependencies: {"3": ["1", "2"], "4": ["3"]}
})
}
// Monitor task progress
mcp__claude-flow__task_status {
taskId: "auth-implementation"
}Memory Coordination
// Report planning status
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$planner$status",
namespace: "coordination",
value: JSON.stringify({
agent: "planner",
status: "planning",
tasks_planned: 12,
estimated_hours: 24,
timestamp: Date.now()
})
}Remember: A good plan executed now is better than a perfect plan executed never. Focus on creating actionable, practical plans that drive progress. Always coordinate through memory.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

