\r \r

Agent Plan Manager\r

\r Manage OpenClaw Agent's execution plans and task workflows in a structured, trackable way.\r \r Who is it for? OpenClaw Agent that needs to organize tasks, track execution progress, or document step-by-step implementation plans.\r \r What makes it different?\r \r

• Agent-Centric: designed for AI agent execution workflows with clear entry/exit points\r
• Structured: separates high-level goals from detailed tool-calling steps\r
• Trackable: uses checkboxes and status fields for execution state visibility\r
• Lightweight: just Markdown files, integrates with OpenClaw's file system tools\r \r

Quick Start\r

\r

1. Create plans/plans-overview.md from the overview template\r
2. Add execution items to the table with appropriate status\r
3. If a plan needs detailed steps, create plans/detailed/XX-{plan-name}.md\r
4. Update plans/detailed/index.md to link the new plan\r
5. Update statuses as execution progresses\r \r

Directory Structure\r

\r

plans/\r
├── plans-overview.md      ← from templates/plans-overview.md\r
└── detailed/\r
    ├── index.md           ← from templates/index.md\r
    └── XX-{plan-name}.md  ← from templates/detailed-plan.md\r
```\r
\r
## When to Use\r
\r
- Creating a new execution plan for complex tasks\r
- Tracking multi-step tool calling workflows\r
- Breaking down user requests into actionable steps\r
- Recording detailed execution documentation\r
- Structured agent task management\r
\r
## Example: Web Scraping Task\r
\r
**Step 1** — Add to `plans/plans-overview.md`:\r
\r
```markdown\r
| 1 ||***|| Web scraping for product prices ||***|| In Progress ||***|| High ||***|| TBD ||***|| TBD ||***|| Extract prices from example.com |\r
```\r
\r
**Step 2** — Create `plans/detailed/01-web-scraping.md`:\r
\r
```markdown\r
# Detailed Plan - Web Scraping for Product Prices\r
\r
## Plan ID: #1\r
\r
## Objective\r
Extract product prices from example.com and save to a CSV file.\r
\r
## Schedule\r
TBD\r
\r
## Deadline\r
TBD\r
\r
## Tool Sequence\r
\r
1. `browser_navigate` → example.com/products\r
2. `browser_snapshot` → extract product list\r
3. `browser_click` → navigate to each product\r
4. `WriteFile` → save results to products.csv\r
\r
## Implementation Steps\r
\r
### 1. Navigate to target URL\r
- [x] Use browser_navigate to load example.com/products\r
\r
### 2. Extract product data\r
- [ ] Capture page snapshot\r
- [ ] Parse product names and prices\r
- [ ] Handle pagination if present\r
\r
### 3. Save results\r
- [ ] Format data as CSV\r
- [ ] Write to products.csv\r
\r
## Estimated Token Usage\r
~2K tokens\r
```\r
\r
**Step 3** — Update `plans/detailed/index.md`:\r
\r
```markdown\r
| #1 | Web scraping for product prices | TBD | TBD | [01-web-scraping.md](./detailed/01-web-scraping.md) |\r
```\r
\r
## Templates\r
\r
All templates live in `templates/`:\r
\r
- **`plans-overview.md`** — High-level execution board with status table\r
- **`index.md`** — Index of all detailed execution plans\r
- **`detailed-plan.md`** — Step-by-step execution plan with tool sequences\r
\r
## Tips\r
\r
- Keep plan names concise; use kebab-case for filenames (`01-web-scraping.md`)\r
- Update `last_updated` in frontmatter whenever the overview changes\r
- Use checkboxes (`- [ ]`) in detailed plans to track execution progress\r
- Include tool sequences to clarify the execution flow\r
- Archive completed plans by moving them to the "Completed Items" section\r
- Estimate token usage when possible for complex multi-step tasks\r