sde-planlisted
Install: claude install-skill tomtommyyuan/automated-sde-skill
# /sde-plan — plan it, then work the plan
The plan file is the unit of work management: what we are doing, why, in what order, and how far
we got. It lives in the repo, so it survives the session, and it is short enough that a reviewer
reads it in two minutes. Steps are the size of a commit.
Arguments: `$ARGUMENTS`
Mode: a plan file path, `--execute`, `--resume`, or an ask phrased as implement / continue /
resume / pick up → **execute**. Anything else → **plan**.
## Plan mode
### 1. Classify the ask
bug · feature · refactor · chore · question (answer it, no plan file) · experiment (success is a
measured number — hypothesis, baseline, metric; the template's experiment variant).
A GitHub issue URL → `gh issue view <n> --json title,body,labels,comments`; the number goes into
the plan and later into the PR.
### 2. Ground it in the code
Before writing a step, read what the step will touch: grep the symbols the ask names, read the
files that own them, read the last commits that changed them (`git log -n 10 -- <path>`), find the
tests that cover them. Every claim in Context cites `path:line`. A plan that says "update the
loader" without having read the loader is a guess.
### 3. Decide what needs the user
Ask (AskUserQuestion, one question, recommended option first) only for a choice that changes the
design and that the code does not settle — which API survives, migrate versus shim. Everything
else is an assumption written under Assumptions, where it can be corrected.
###