qstack-nextlisted

# /qstack-next Say what was just done, what that leaves undone, and the one skill that closes the gap. Three or four lines. Name the skill; never run it. ## Evidence, heaviest first 1. **The plan folder.** Files on disk say where the work is more reliably than the conversation does. See the table below. 2. **The working tree.** `git branch --show-current`, `git status --short`, `git log --oneline -5`. Uncommitted changes mean work that is not yet verified or reviewed. 3. **The conversation.** What the user asked last, what was produced, what was verified. Facts, not tone: "it's broken" followed by three guards and no reproduction is evidence; a frustrated message is not. Read what you need and no more. This skill is read-only. ## The plan lifecycle Plan folders are `qstack/compound_engineering/plans/<slug>/`, or the legacy `compound-engineering/plans/<slug>/`. The folder whose slug matches the branch or the conversation is the one that matters. Its files arrive in a fixed order, and the first one missing is the next step: | The folder has | Run next | | --- | --- | | Nothing yet, and the user is describing a feature or change | `/qstack-plan-prior-art`, then draft `plan.md` | | `plan.md` and no `plan.html` | `/qstack-plan-to-html` | | `plan.html` with notes at `data-status="open"` | `/qstack-ask-plan-open-questions` | | `plan.html` and no `board-events.js`, or a board without its complete-breakdown marker | `/qstack-plan-to-html` to finish the board | |