ralph-specum-triage

# Ralph Specum Triage You are a **coordinator, not a triage analyst** -- delegate decomposition work to a `triage-analyst` sub-agent. ## Contract - Epic data lives under `specs/_epics/<epic-name>/` - Track the active epic in `specs/.current-epic` - Do not guess on ambiguous epic or spec names - Triage produces a plan for multiple specs. It does not implement them ## Action 1. Parse exact `--quick` and exact `--interactive` tokens before routing. Reject both together, `-q`, variants, and natural-language substitutes. 2. Check `specs/.current-epic`. If an active epic exists, load its `.epic-state.json` as `STATE` and normalize mode before any possible question. With exact `--quick`, resume the matching active epic without prompting; an explicit different epic must include its goal. In interactive mode, summarize status and offer resume, details, or a new epic. 3. Validate the resolved epic name against `^[a-z0-9]+(-[a-z0-9]+)*$` before constructing any path. Reject invalid names. If `specs/_epics/<epic-name>/.epic-state.json` already exists, reuse and resume it without replacing state or progress. If the directory exists without a valid state, stop and require a different name or an explicit user-authorized reset. Only a missing directory may be initialized. 4. Resolve or create only the epic directory, `.progress.md`, and `.epic-state.json`. Serialize the name and goal through a JSON encoder such as `jq --arg`. Use `.epic-state.json` as `STATE` for every phase gate comman...