do-planlisted

# Make a Plan (Shape Up Methodology) ## Repo Context Probe If `docs/sdlc/do-plan.md` exists, read it and honor its declarations; otherwise use the generic defaults described below. The context file is where a repo layers its planning automation onto this generic baseline: stage/status markers, a recon-validation gate, blast-radius and memory tools, the plans/infra directory conventions, required plan sections and frontmatter fields, the commit-on-main rule, and a plan-revising lock. When the file is absent (the common case in a foreign repo), this skill runs entirely on `git`, `gh`, the Read/Write tools, and optionally WebSearch — it writes a structured plan document and links a tracking issue, with no repo-specific tooling required. Creates structured feature plans (by default under `docs/plans/`) following Shape Up principles: narrow the problem, set appetite, rough out the solution, identify rabbit holes, and define boundaries. ## What this skill does 1. Takes a vague or specific request and narrows it into a concrete plan 2. Writes a structured plan document in `docs/plans/{slug}.md` 3. Creates or links a GitHub issue for tracking 4. Sends the plan for review with open questions ## When to load sub-files | Sub-file | Load when... | |----------|-------------| | `PLAN_TEMPLATE.md` | Writing the plan document (copy the template into `docs/plans/{slug}.md`) | | `SCOPING.md` | The request is vague, a grab-bag, or needs narrowing before planning | | `EXAMPLES.md` | Deci