plan-protocollisted

# Plan Protocol > **Load this skill** when creating or updating implementation plans. ## TL;DR Checklist When creating or updating a plan, ensure: - [ ] YAML frontmatter with `status`, `phase`, `updated` - [ ] `## Goal` section (one sentence) - [ ] `## Context & Decisions` table with citations (`ref:delegation-id`) - [ ] Phases with status markers: `[COMPLETE]`, `[IN PROGRESS]`, `[PENDING]` - [ ] Tasks with hierarchical numbering (1.1, 1.2, 2.1) - [ ] Only ONE task marked `← CURRENT` - [ ] Citations for all research-based decisions --- ## When to Use 1. Starting a multi-step implementation 2. After receiving a complex user request 3. When tracking progress across phases 4. After research that informs architectural decisions ## When NOT to Use 1. Simple one-off tasks → use built-in todos instead 2. Pure research/exploration → use delegations only 3. Quick fixes that don't need tracking 4. Single-file changes with no dependencies --- ## Plan Format Use `plan_save` with this exact markdown format: ```markdown --- status: STATUS phase: PHASE_NUMBER updated: YYYY-MM-DD --- # Implementation Plan ## Goal ONE_SENTENCE_DESCRIBING_OUTCOME ## Context & Decisions | Decision | Rationale | Source | |----------|-----------|--------| | CHOICE | WHY | `ref:DELEGATION_ID` | ## Phase 1: NAME [STATUS_MARKER] - [x] 1.1 Completed task - [x] 1.2 Another completed task → `ref:DELEGATION_ID` ## Phase 2: NAME [IN PROGRESS] - [x] 2.1 Completed task - [ ] **2.2 Current task** ← CURRENT