Turn a rough ask into a clear work order. Use when the ask is rough, unspoken, or double-readable — before planning or building.
71
77%
Does it follow best practices?
Impact
94%
1.32xAverage score across 1 eval scenario
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./hope/skills/intent/SKILL.mdFrom the conversation/context/user:
Proceed only when: starting the work now would mean inventing what the user means.
Anything else, say which in one plain line — never work the ask over anyway:
Before routing anything: retrieve what the record, the repo, or the world can answer. Only what the user alone holds routes to a skill.
Route each blocker by what it is, invoking the named skill with the Skill tool:
What each skill gives back re-enters the routing: a clarify pick can surface something the user can't express; an elicit record can leave words with two readings; an explain can let the user finally say the ask; an interrogate answer can amend the ask. Route again until nothing blocks the ask.
Where the input leaves it open, ask the negative once — what should this NOT do — before closing.
The work order is the result: the ask restated in one line, confirmed by the user — plus what it must NOT do, where that surfaced. The routing ends only when starting the work would invent nothing.
Then check what still stands open:
The routing is spent once the user confirms the one-line ask — anything further runs under the branch picked here, never as another round of working the ask over.
7f55b8e
Also appears in
last in sync Mar 28, 2026
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.