dev-plan

## Step 0: Discover Project Root Run the [discovery script](scripts/discover.sh): ```bash bash "$DISCOVER" root ``` Where `$DISCOVER` is the absolute path to `scripts/discover.sh` within this skill's directory. **Path safety** — shell state does not persist between tool calls, so you must provide full script paths on each call: - **Use `$HOME`** instead of the literal home directory (e.g., `bash "$HOME/code/…/discover.sh"`, not `bash "/Users/name/…/discover.sh"`). This prevents username hallucination. - **Copy values from tool output.** When reusing a value returned by a previous command (like `$PROJECT_ROOT`), copy it verbatim from that command's output. Never retype a path from memory. - **Verify on first call**: if a script call fails with "No such file", the path is wrong — STOP and re-derive from the skill-loading context. - **Never ignore a non-zero exit.** If any script in this skill fails, stop and report the error before continuing. Store the output as `$PROJECT_ROOT`. If the command fails, inform the user and stop. ## PRIMARY DIRECTIVE The sole deliverable is PRD files written to `$PROJECT_ROOT/.dev/$FEATURE_NAME/`. Produce documentation, not code. Every session must end with files on disk. This is part of a 3-skill system (`/dev-plan` → `/dev-checkpoint` → `/dev-resume`). The other skills parse PRD files using status markers (`⬜` pending; `✅`/`⏭️`/`⛔`/`⏹️` resolved), phase gates, file changes summary, and sub-PRD links. Write steps with `⬜` — any other emoj...