Use persistent markdown files for complex task execution. Creates task_plan.md, findings.md, and progress.md. Use when starting multi-step tasks, research projects, or any task requiring >5 tool calls. Solves the EXECUTION problem - staying focused during long-running tasks.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
planning
description
Use persistent markdown files for complex task execution. Creates task_plan.md, findings.md, and progress.md. Use when starting multi-step tasks, research projects, or any task requiring >5 tool calls. Solves the EXECUTION problem - staying focused during long-running tasks.
allowed-tools
Read, Write, Edit, Bash, Glob, Grep
user-invocable
true
metadata
{"author":"23blocks","version":"1.0"}
AI Maestro Planning Skill
The Problem This Solves: EXECUTION
This skill solves the execution problem - losing focus during complex tasks:
Problem
Symptom
This Skill Fixes It
Goal drift
Forgot original objective after 50 tool calls
Re-read plan before decisions
Lost progress
Can't remember what phase I'm in
Phase tracking in task_plan.md
Repeated errors
Make same mistake twice
Error log prevents repetition
Session loss
Can't resume after /clear
Planning files persist on disk
Note: This is different from the Memory skill (which solves recall of past conversations). Planning solves staying focused NOW.
Core Principle
Context Window = RAM (volatile, limited, fast)
Filesystem = Disk (persistent, unlimited, explicit read required)
Anything important gets written to disk.
Output Directory
Planning output files (task_plan.md, findings.md, progress.md) should be written to:
The directory specified by the AIMAESTRO_PLANNING_DIR environment variable (if set)
Otherwise, docs_dev/ in the current project root
Create the directory if it does not exist
Do NOT write planning files to the project root — use docs_dev/ to avoid cluttering the project.
The 3-File Pattern
Create these files in docs_dev/ (not the project root or the skill directory):
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
Before any complex task (3+ steps):
# 1. Determine output directory
PLAN_DIR="${AIMAESTRO_PLANNING_DIR:-docs_dev}"mkdir -p "$PLAN_DIR"# 2. Create planning files from templatescat ~/.claude/skills/planning/templates/task_plan.md > "$PLAN_DIR/task_plan.md"cat ~/.claude/skills/planning/templates/findings.md > "$PLAN_DIR/findings.md"cat ~/.claude/skills/planning/templates/progress.md > "$PLAN_DIR/progress.md"# 3. Edit task_plan.md with your specific goal and phases
Then follow the rules below.
The 6 Rules
Rule 1: Create Plan First
NEVER start a complex task without creating task_plan.md.
Before writing any code or making any changes:
Create task_plan.md with clear goal
Break work into phases
List key questions to answer
Rule 2: Read Before Decide
Before any major decision, re-read the plan:
cat"${AIMAESTRO_PLANNING_DIR:-docs_dev}/task_plan.md" | head -50
This refreshes your goals in the context window, preventing drift.
Rule 3: Update After Act
After completing any phase:
Mark phase as [x] complete
Update status section
Log any errors encountered
Note files created/modified
Rule 4: The 2-Action Rule
After every 2 search/view/browse operations, immediately save key findings to findings.md.
Visual content (screenshots, PDFs, browser results) doesn't persist in context. Write it down NOW.
