plan-directorylisted

# Plan Directory Skill ## When to Use This Skill - Scaffolding a new project, feature, or migration that benefits from a structured, step-by-step plan. - Creating a repeatable plan that an LLM or engineer can execute with explicit, verifiable checkboxes. - Maintaining an existing plan directory: adding tasks, updating progress, or archiving completed plans. - When the user says "create a plan", "scaffold a plan", "plan this feature", or similar intent implying structured task breakdown. Do **not** use this skill for ad-hoc todo lists, single-file notes, or when the user explicitly wants a different format. ## LLM Intake (Required Inputs) Before writing any files, gather these inputs. If any are missing, **ask** the user for them explicitly. | Input | Required | Description | |-------|----------|-------------| | Plan title | Yes | Human-readable name (e.g., "User Authentication Overhaul") | | Plan slug | Yes | Hyphenated directory/file slug (e.g., `user-auth-overhaul`) | | Target location | No | Directory path; defaults to `docs/plans/<slug>/` or `plans/<slug>/` | | Task list | Yes | List of tasks with short names and scopes | | Locked decisions | No | Key constraints or choices that must not change | | Testing expectations | No | Commands, subsets, or manual QA requirements | When updating an existing plan, read the current `PLAN.md` first to understand context before modifying. ## Invariants (Do Not Violate) 1. **PLAN.md is the index, not the content.** It c