do-planlisted

# Make a Plan (Shape Up Methodology) ## Stage Marker At the very start of this skill, write an in_progress marker: ```bash sdlc-tool stage-marker --stage PLAN --status in_progress --issue-number {issue_number} 2>/dev/null || true ``` After the plan document is committed and pushed (end of Step 5), write the completion marker: ```bash sdlc-tool stage-marker --stage PLAN --status completed --issue-number {issue_number} 2>/dev/null || true ``` Creates structured feature plans in `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` | Deciding how to respond to a user request (vague vs. grab-bag vs. good) | ## Cross-Repo Resolution For cross-project work, the `GH_REPO` environment variable is automatically set by `sdk_client.py`. The `gh` CLI natively respects this env var, so all `gh` commands automatically target the correct repository. No `