using-smithylisted

# Using Smithy Smithy is a full dev pipeline. This skill is the router: it tells you WHEN to reach for which smithy skill, and it names the rationalizations that lead to skipping them. <CRITICAL> If a smithy skill applies to the task at hand — even plausibly — invoke it BEFORE responding, before clarifying questions, before exploring the code. The skills front-load exactly those steps; doing them ad-hoc first duplicates work and skips their safeguards. If the skill turns out not to fit, you can say so and step out — but the check comes first. </CRITICAL> ## Routing table — trigger → skill (technical alias in parentheses) Every skill also has a plain software-engineering alias, installed as a slash command: `/smithy:plan` invokes `smithy:blueprint`, etc. | The user wants / the situation is | Skill (alias) | |---|---| | Build a feature end-to-end, "take this from idea to tested code" | `/smithy:smithy` (`pipeline`) | | Understand requirements, explore before building, "write a spec" | `/smithy:assay` (`research`) | | A spec exists; break work into tasks/plan | `/smithy:blueprint` (`plan`) | | An approved plan exists; implement it | `/smithy:forge` (`implement`) | | Implement test-first / "TDD this" / fixing a bug with a repro | `/smithy:jig` (`tdd`) | | "Review this change/task/diff" | `/smithy:inspect` (`code-review`) | | "Is this ready to ship?" / multi-perspective review | `/smithy:guild` (`review-panel`) | | "Who uses this system?" / define test personas | `/smithy:com