← ClaudeAtlas

planninglisted

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.
qepilot/qepilot-stack · ★ 0 · AI & Automation · score 66
Install: claude install-skill qepilot/qepilot-stack
# 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/