Who it is forA developer who gets vague tasks like 'add caching to the user API' and wants a clear briefing before the agent writes code.
The problemA vague request makes the agent guess. The guess can rest on an assumption you never made, and the work gets thrown away.
The outcomeA saved IntentSpec in .intent/ or .intent.yaml that records the probed facts, the one question you answered, and whether the intent is settled.
What you need first
- A coding agent where you can install a skill, using `npx skills add angel291592/Intent-Router` or the manual steps in Quick start
- A repository the agent can read, since the skill probes the repo before asking anything
- A vague request you want to turn into work, such as a refactor or a feature
Steps
- Install the skill with
npx skills add angel291592/Intent-Router, or follow the manual steps in Quick start. (inferred, check the README) - Give your agent the vague request in one sentence, in the same repo you want changed.
- Let the skill probe the repo first, then answer only the question the repo cannot answer.
- Open the saved file in .intent/ or .intent.yaml and check the probed fields and their evidence pointers.
- Confirm the spec state reads settled before you let the agent carry out the work.
Prompt for your agent
Using the Intent-Router skill in this repo, turn the request '<request>' into a typed IntentSpec. Probe the repo first and ask only the one question the repo cannot answer. Expected output: a saved IntentSpec file under .intent/ with evidence pointers and a state field. Verify that no probed field lacks an evidence pointer.
Caveat. The README says the skill reads your repo, ticket system or docs before asking, so the number of questions depends on what those sources already answer.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page