dev-checkpoint

## Checkpoint Current Session Review the current session and create a continuation prompt for the next session. ### SAVE-ONLY MODE This skill analyzes and saves. It does NOT fix, investigate, or implement anything. - Do NOT investigate bugs or errors mentioned during the session - Do NOT start implementing fixes or next steps - Do NOT move to the next phase or task - If the user mentions bugs during confirmation (Step 4), note them in `<blockers>` or `<notes>` but do NOT attempt to fix them ### Why commit-first ordering The branch/worktree decision and the optional commit happen **before** PRD markers are updated and the checkpoint is written. This way the saved checkpoint records the branch and commit the session actually ends on — a branch created *after* the checkpoint would make the next `/dev-resume` report `drifted`. The PRD-marker edits and `checkpoint.md`/`session-log.md` written after the commit are honestly recorded as `uncommittedChanges: true`; they get swept into the next session's commit. ### 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"`). T...