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 more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.
$ npx claude-code-templates@latest --skill="ai-maestro/planning" --yesRequires Claude Code. The command adds this skill to your project's .claudedirectory — nothing runs on ToolZip's servers.
What's inside this skill
Component source
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.
Related Claude Code Skills
Agent Management
Create, manage, and orchestrate AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "hibernate agent", "wake agent", "install plugin", "show agent", "restart agent", or any agent lifecycle management task.
Memory Search
Search conversation history and semantic memory to recall previous discussions, decisions, and context. Use when the user asks to "search memory", "what did we discuss", "remember when", "find previous conversation", "check history", or before starting work to recall prior decisions.
Agent Messaging
Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an agent", "check agent inbox", "message another agent", "reply to a message", "notify an agent", or any inter-agent communication task.
Docs Search
Search auto-generated codebase documentation for function signatures, API docs, class definitions, and code comments. Use when the user asks to "search docs", "find documentation", "look up a function", "check the API", or before implementing changes to verify correct signatures and patterns.
Graph Query
Query the code graph database to understand component relationships, dependencies, and change impact. Use when the user asks to "find callers", "check dependencies", "what uses this", "show relationships", "find serializers", or when reading code and needing to understand what depends on a component before modifications.
Frontend Design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.