Plan Manager
by @wx528
Unified plan management system for coordinating OpenClaw Agent and Human plans. Use when managing both AI agent execution workflows and human task plans in a...
clawhub install plan-managerπ About This Skill
name: plan-manager description: | Unified plan management system for coordinating OpenClaw Agent and Human plans.
Use when managing both AI agent execution workflows and human task plans in a unified structure. version: 1.0.0 author: ζ轩ε εΈ
Plan Manager
Unified plan management system for coordinating OpenClaw Agent execution plans and Human task plans.
Overview
This skill provides a dual-track planning system:
| Track | Purpose | Location |
|-------|---------|----------|
| Agent Plans | Track OpenClaw Agent's execution workflows, tool sequences, and task progress | plans/agent/ |
| Human Plans | Track human tasks, todos, and project milestones | plans/human/ |
Directory Structure
plans/
βββ README.md # This file - overview and coordination guide
βββ agent/
β βββ plans-overview.md # Agent's high-level execution board
β βββ detailed/
β β βββ index.md # Index of all detailed agent plans
β β βββ XX-{plan-name}.md # Individual agent execution plans
β βββ archive/ # Completed agent plans
βββ human/
βββ plans-overview.md # Human's high-level task board
βββ detailed/
β βββ index.md # Index of all detailed human plans
β βββ XX-{plan-name}.md # Individual human task plans
βββ archive/ # Completed human plans
When to Use Which Track
Use Agent Track When:
Use Human Track When:
Coordination Patterns
Pattern 1: Agent Assists Human Plan
Human creates a plan β Agent creates corresponding execution plan β Agent executes β Both update statusExample:
Human: "Plan a trip to Japan"
β
human/plans-overview.md: "Plan Japan trip" (Status: In Progress)
β
agent/plans-overview.md: "Research flights, hotels, itinerary" (Status: In Progress)
β
[Agent executes research tasks]
β
Both tracks updated to Done
Pattern 2: Agent Autonomous Execution
User requests complex task β Agent creates execution plan β Agent executes independentlyExample:
User: "Refactor the auth module"
β
agent/plans-overview.md: "Auth module refactor" (Status: In Progress)
β
[Agent executes refactoring with detailed plan]
β
Agent updates status to Done
Pattern 3: Human Oversight
Agent creates plan β Requests human approval β Human approves/modifies β Agent executesExample:
User: "Design a new feature"
β
agent/plans-overview.md: "Design new feature" (Status: Pending Approval)
β
[Agent presents plan to human]
β
human/plans-overview.md: "Review and approve feature design" (Status: In Progress)
β
[Human reviews, approves]
β
Agent proceeds to execution
Quick Start
For Agent Tasks:
1. Create plans/agent/plans-overview.md
2. Add execution items to the status table
3. Create plans/agent/detailed/XX-{plan-name}.md for complex tasks
4. Update plans/agent/detailed/index.md
5. Mark steps complete as execution progresses
For Human Tasks:
1. Create plans/human/plans-overview.md
2. Add task items to the status table
3. Create plans/human/detailed/XX-{plan-name}.md for complex tasks
4. Update plans/human/detailed/index.md
5. Update statuses weekly or as tasks complete
Templates
Templates are organized by track:
templates/
βββ agent/ # Templates for Agent plans
β βββ plans-overview.md
β βββ detailed-plan.md
β βββ index.md
βββ human/ # Templates for Human plans
βββ plans-overview.md
βββ detailed-plan.md
βββ index.md
Status Values
| Status | Meaning |
|--------|---------|
| Pending | Plan created, not yet started |
| In Progress | Actively being worked on |
| Blocked | Waiting on dependency or approval |
| Done | Completed successfully |
| Cancelled | No longer needed |
Tips
A-1, A-2 for agent plans and H-1, H-2 for human plans when cross-referencingarchive/ folder monthly01-auth-refactor.md)Example: Coordinated Web Development Project
Human Track (plans/human/plans-overview.md):
| H-1 ||*|| Launch new website ||*|| In Progress ||*|| High ||*|| Q2 2025 ||*|| June 30 ||*|| A-1, A-2 |
Agent Track (plans/agent/plans-overview.md):
| A-1 ||*|| Design database schema ||*|| Done ||*|| High ||*|| Week 1 ||*|| - ||*|| For H-1 |
| A-2 ||*|| Implement API endpoints ||*|| In Progress ||*|| High ||*|| Week 2-3 ||*|| - ||*|| For H-1 |
This structure ensures both human goals and agent execution are visible and coordinated.
π‘ Examples
For Agent Tasks:
1. Create plans/agent/plans-overview.md
2. Add execution items to the status table
3. Create plans/agent/detailed/XX-{plan-name}.md for complex tasks
4. Update plans/agent/detailed/index.md
5. Mark steps complete as execution progresses
For Human Tasks:
1. Create plans/human/plans-overview.md
2. Add task items to the status table
3. Create plans/human/detailed/XX-{plan-name}.md for complex tasks
4. Update plans/human/detailed/index.md
5. Update statuses weekly or as tasks complete
π Tips & Best Practices
A-1, A-2 for agent plans and H-1, H-2 for human plans when cross-referencingarchive/ folder monthly01-auth-refactor.md)