masterplan-detectlisted

# Suggesting /masterplan import for legacy planning artifacts This skill **suggests**, it does not act. The user must explicitly run `/masterplan import` to convert anything. ## When to fire The user is in a git repo and at least one of these is true: - A planning-shaped file lives at the repo root or in a common docs directory: - `PLAN.md`, `TODO.md`, `ROADMAP.md`, `WORKLOG.md`, `NOTES.md` - `docs/plans/*.md`, `docs/design/*.md`, `docs/rfcs/*.md`, `architecture/*.md`, `specs/*.md` - A pre-v3 masterplan artifact exists under `docs/superpowers/{plans,specs,retros,archived-plans,archived-specs}` and there is no matching `docs/masterplan/<slug>/state.yml`. - A plan exists at `docs/superpowers/plans/*.md` with **no** sibling `*-status.md` (orphan from pre-v3 masterplan runs). - An open feature branch (not yet merged into the trunk) has descriptive name + commit history that suggests a tracked feature, but no masterplan status file exists for it. - A draft PR's body contains a task list (`- [ ]` / `- [x]` / numbered steps). Fire at **natural break points**: a fresh conversation in this repo, a user asking "what should I work on?", a user about to start a new feature. Don't interrupt unrelated work. ## What to surface A short message — no prose, no editorialization. Format: > I see <N> existing planning artifact(s) in this repo: > - `<path>` — last modified <date> > - `<path>` — last modified <date> > > If you'd like to bring them under the `/masterplan` schema (`docs/m