contextlisted

# /context Top-level orchestrator for the `/context` family. Replaces 2 standalone commands with a single entry point + sub-command dispatch. ## Sub-commands | Sub-command | Routes to | Purpose | |---|---|---| | `/context create` | `commands/context/create.md` | Analyze a codebase area and create a structured context document | | `/context refactor` | `commands/context/refactor.md` | Analyze, update, and extend an existing context document | Sub-command names match the locked contract in [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md). ## Dispatch 1. Parse the user's argument: `/context <sub-command> [args]`. 2. Look up the sub-command in the table above. 3. Load the body of the routed file and follow its `## Instructions` section verbatim with the remaining args. 4. If the sub-command is unknown or missing, print the table above and ask: > 1. create — author a new context document > 2. refactor — update an existing context document ## Rules - **Do NOT commit, push, or open a PR** unless the sub-command explicitly authorizes it. - **Do NOT chain sub-commands.** One `/context <sub>` per turn. - If the user invokes `/context` with no argument, **show the menu** — do not guess which sub-command they meant.