Planning
Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires ...
Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.
Install
Quick install
npx skills add https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/ai-maestro/planningnpx skills add davila7/claude-code-templates --skill planning --agent claude-codenpx skills add davila7/claude-code-templates --skill planning --agent cursornpx skills add davila7/claude-code-templates --skill planning --agent codexnpx skills add davila7/claude-code-templates --skill planning --agent opencodenpx skills add davila7/claude-code-templates --skill planning --agent github-copilotnpx skills add davila7/claude-code-templates --skill planning --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add davila7/claude-code-templates --skill planningManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/davila7/claude-code-templates.gitcp -r claude-code-templates/cli-tool/components/skills/ai-maestro/planning ~/.claude/skills/AI Maestro Planning
Solve the execution problem -- staying focused during complex, multi-step tasks. Uses persistent markdown files to track goals, findings, and progress so you never lose context. Part of the AI Maestro suite.
When to Use
- Multi-step tasks (3+ steps)
- Research projects
- Building features requiring >5 tool calls
- Any task where you might lose track of the goal
The 3-File Pattern
Create in docs_dev/ (or $AIMAESTRO_PLANNING_DIR):
| File | Purpose | Update When |
|------|---------|-------------|
| task_plan.md | Goals, phases, decisions, errors | After each phase |
| findings.md | Research, discoveries, resources | During research |
| progress.md | Session log, test results | Throughout session |
Quick Start
PLAN_DIR="${AIMAESTRO_PLANNING_DIR:-docs_dev}"
mkdir -p "$PLAN_DIR"
Then create task_plan.md with:
# Task: [Goal]
## Phases
- [ ] Phase 1: Research
- [ ] Phase 2: Design
- [ ] Phase 3: Implement
- [ ] Phase 4: Test
## Decisions
| Decision | Rationale | Date |
|----------|-----------|------|
## Errors Encountered
| Error | Attempt | Resolution |
|-------|---------|------------|
The 6 Rules
- Create plan first -- Never start complex work without
task_plan.md - Read before decide -- Re-read the plan before any major decision
- Update after act -- Mark phases complete, log what changed
- 2-action rule -- After every 2 search/browse operations, save findings to
findings.md - Log all errors -- Every error goes in the plan with attempt number and resolution
- Never repeat failures -- If an action failed, change your approach
The 3-Strike Protocol
| Strike | Action |
|--------|--------|
| 1 | Diagnose root cause, apply targeted fix |
| 2 | Try a different approach entirely |
| 3 | Question assumptions, search for similar issues |
| After 3 | Escalate to user with all attempts documented |
The 5-Question Reboot
Lost? Answer these from your planning files:
- Where am I? (current phase in
task_plan.md) - Where am I going? (remaining phases)
- What's the goal? (goal section)
- What have I learned? (
findings.md) - What have I done? (
progress.md)
Full AI Maestro Experience
This skill works standalone with no dependencies. For the complete experience including memory search, docs search, graph query, agent messaging, and agent management, install the full AI Maestro platform.
SKILL.md source
---
name: planning
description: Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires ...
---
# AI Maestro Planning
Solve the execution problem -- staying focused during complex, multi-step tasks. Uses persistent markdown files to track goals, findings, and progress so you never lose context. Part of the [AI Maestro](https://github.com/23blocks-OS/ai-maestro) suite.
## When to Use
- Multi-step tasks (3+ steps)
- Research projects
- Building features requiring >5 tool calls
- Any task where you might lose track of the goal
## The 3-File Pattern
Create in `docs_dev/` (or `$AIMAESTRO_PLANNING_DIR`):
| File | Purpose | Update When |
|------|---------|-------------|
| `task_plan.md` | Goals, phases, decisions, errors | After each phase |
| `findings.md` | Research, discoveries, resources | During research |
| `progress.md` | Session log, test results | Throughout session |
## Quick Start
```bash
PLAN_DIR="${AIMAESTRO_PLANNING_DIR:-docs_dev}"
mkdir -p "$PLAN_DIR"
```
Then create `task_plan.md` with:
```markdown
# Task: [Goal]
## Phases
- [ ] Phase 1: Research
- [ ] Phase 2: Design
- [ ] Phase 3: Implement
- [ ] Phase 4: Test
## Decisions
| Decision | Rationale | Date |
|----------|-----------|------|
## Errors Encountered
| Error | Attempt | Resolution |
|-------|---------|------------|
```
## The 6 Rules
1. **Create plan first** -- Never start complex work without `task_plan.md`
2. **Read before decide** -- Re-read the plan before any major decision
3. **Update after act** -- Mark phases complete, log what changed
4. **2-action rule** -- After every 2 search/browse operations, save findings to `findings.md`
5. **Log all errors** -- Every error goes in the plan with attempt number and resolution
6. **Never repeat failures** -- If an action failed, change your approach
## The 3-Strike Protocol
| Strike | Action |
|--------|--------|
| 1 | Diagnose root cause, apply targeted fix |
| 2 | Try a different approach entirely |
| 3 | Question assumptions, search for similar issues |
| After 3 | Escalate to user with all attempts documented |
## The 5-Question Reboot
Lost? Answer these from your planning files:
1. Where am I? (current phase in `task_plan.md`)
2. Where am I going? (remaining phases)
3. What's the goal? (goal section)
4. What have I learned? (`findings.md`)
5. What have I done? (`progress.md`)
## Full AI Maestro Experience
This skill works standalone with no dependencies. For the complete experience including **memory search**, **docs search**, **graph query**, **agent messaging**, and **agent management**, install the full [AI Maestro](https://github.com/23blocks-OS/ai-maestro) platform.
Related skills 6
ElevenLabs Automation
Automate ElevenLabs text-to-speech workflows -- generate speech from text, browse and inspect voices, check subscription limits, list models, stream audio, and retrieve history via the Composio MCP...
Finishing A Development Branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Receiving Code Review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performat...
Webapp Testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browse...
Replicate Automation
Automate Replicate AI model operations -- run predictions, upload files, inspect model schemas, list versions, and manage prediction history via the Composio MCP integration.
OpenAI Automation
Automate OpenAI API operations -- generate responses with multimodal and structured output support, create embeddings, generate images, and list models via the Composio MCP integration.