scaffold-sumo-qa-skilllisted

# scaffold-sumo-qa-skill Drives the four-step recipe for adding a new `sumo-qa-<name>` sub-skill so all the pieces land together. The deterministic file generation lives in `scripts/scaffold.py`; this document is the thin guide for gathering inputs and checking the surfaces the script cannot reach (the installed MCP server). ## When to use Trigger this skill whenever the user asks to add a new sumo-qa sub-skill — phrases like "scaffold a new skill", "add a sumo-qa-X skill", "I want a skill that handles Y for QA", or even just "let's start the routing for Z". The user invokes it explicitly with `/scaffold-sumo-qa-skill`; it doesn't auto-trigger. ## Inputs Gather these from the user up front. If they only give a partial set, ask for the rest in one round of questions — don't drip-feed. 1. **Skill name** (without prefix) — kebab-case, descriptive of the user-intent the skill handles. The script prepends `sumo-qa-` automatically. 2. **One-line description** — for the SKILL.md frontmatter `description:`. Convention across the estate: start with "Use when ..." so the trigger context is obvious. 3. **Approach tag** — the kebab-case routing key that lands in `knowledge/approaches.md`. The user's `sumo-qa-deciding-approach` skill consults this catalogue when picking which sub-skill to route to. ## Verify the surfaces the script can't reach The script checks for collisions against the source tree (`skills/`, `tests/evals/promptfoo/`, `knowledge/approaches.md`). It can't check t