next-skills

# /next-skills **Next Skills (NSP)** answers the question a skill leaves open: *what now?* When a participating skill finishes, NSP reads that skill's declared successors and surfaces them — each with an activation phrase and a short reason — for the caller to choose from. The caller (a human, or another agent) picks; nothing auto-runs. NSP is invoked two ways: **automatically**, when a skill carrying the NSP opt-in block completes; or **directly**, as `/next-skills <skill>` to preview a skill's declared successors. > **Structured execution spec:** [`protocol.yon`](protocol.yon). It carries the three steps and the > offer-only / empty-silent / loop-safe rules as validatable records; this file is the explanation. > Keep the two in sync — edit one, update the other and refresh the `@STAMP` date. ## The protocol — three steps 1. **Read.** Take the just-finished skill's `next-skills:` front-matter list. Each entry has a `skill`, a `phrase` (its activation phrase), and a `why` (one line: why it might be useful next). If the list is absent or empty, **stop silently** — NSP surfaces nothing. 2. **Surface.** Present the recommendations for the caller to pick (runtime-mapped, below). Recommendations are *offered*, never auto-invoked. 3. **Activate.** On the caller's pick, activate the chosen skill(s) via their activation phrase. On no pick, end quietly. ## Surface step — runtime mapping - **Claude Code** → `AskUserQuestion` (multiSelect). One option per recommendati...