Decide the technical path once the ask is clear. Use when the WHAT is confirmed but more than one way to build it remains — architecture, technology, design.
76%
Does it follow best practices?
Impact
95%
1.13x2 of 3 eval scenarios. Add 1 more for a full score.
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./hope/skills/shape/SKILL.mdChange no file while a choice the path rests on is open. A choice you settle by assuming, however likely the assumption, is open.
Decide only among ways that differ where it matters. Where no work order states the bar the ask must meet, use deepen skill first. Look up what settles a choice without the user — the bar, their taste from CLAUDE.md and project rules, what their own accounts and plans already offer, facts from the repo, docs, the web. Only choices that stay open after that route to a skill.
Route each open choice by what keeps it open, invoking the named skill with the Skill tool:
When the work iterates — an agent loop, a refinement cycle — which loop is itself one of the choices: read loop-selection.md.
Each decision re-enters the routing: a resolved choice can open the next one or conflict with an earlier one; a conflict is one more choice, surfaced to the user. Route again until every open choice has the user's decision or confirmation and none conflict.
Ask every choice still open at once, with AskUserQuestion. Then state each resolved choice with its reason and what lost.
The path is chosen and no target contract will judge it → use inversion skill on it; each negated line joins the path as a constraint.
The ask itself is still rough — starting would mean inventing what the user means → use intent skill.
saadshahd/moo.md
c263dea
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.