CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./cli-tool/components/skills/ai-maestro/planning/SKILL.md
SKILL.md
Quality
Evals
Security

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):

FilePurposeUpdate When
task_plan.mdGoals, phases, decisions, errorsAfter each phase
findings.mdResearch, discoveries, resourcesDuring research
progress.mdSession log, test resultsThroughout 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

  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

StrikeAction
1Diagnose root cause, apply targeted fix
2Try a different approach entirely
3Question assumptions, search for similar issues
After 3Escalate 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 platform.

Repository
davila7/claude-code-templates
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.