using-skillslisted

# Using Skills A router. Identify the SDLC phase of the incoming work, then activate the matching skill. Skills live under nine SDLC phases, plus a `meta` group for this router and `skill-authoring`. ## When to use - Start of a session, before any response or action. - Unsure which skill fits the task at hand. - A task spans multiple phases and you need to sequence them. **Not for:** mid-task when a skill is already active — don't re-route. For any new task, route even if it seems obvious; the skill may enforce discipline the shortcut skips. **Rationalizations that skip routing — resist them:** | Excuse | Reality | |---|---| | "This is just a simple question." | Questions are tasks. A skill may structure the answer. | | "I already know how to do this." | Knowing how ≠ following the discipline. The skill enforces the steps. | | "It's faster to just do it." | A skipped test-first or review is a bug shipped faster. | | "The skill is obvious here." | Obvious to route ≠ obvious to follow. Invoke it; let it run. | | "This is too small for a skill." | Small tasks are where discipline slips. `tdd`/`debugging` scale down. | | "I'll route after I start." | Starting unrouted biases you against the skill's process. Route first. | ## Steps 1. Pick the phase, then activate the entry-point skill it lists. - **meta** — `using-skills` (this router) · `skill-authoring` (author + eval skills) - **01-product** — `brainstorm` · `spec` · `oss-strategy` - **02-research** — `researc