DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to delegate a task to an agent and check the result with Intent Router

Hand a settled spec to a coding agent, then compare the delivered work against each constraint.

Who it is forA tech lead who delegates features to an AI agent and wants proof the output matches what was decided.

The problemDelivered code often drifts from the original request, and a chat reply gives no record of what was decided.

The outcomeA spec file with each constraint marked met, with a code pointer, or not met, plus the check result written back into the same file.

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

  1. Install the skill with npx skills add angel291592/Intent-Router, or follow the manual steps in Quick start. (inferred, check the README)
  2. Run the skill on the task in the same conversation as the coding work, so it can see the delivered result.
  3. Let the agent carry out the settled spec as written.
  4. Read the Intent check output, one line per constraint, marked met or not met.
  5. Open the .intent/ file and confirm the check result was written back into it.

Prompt for your agent

Using the Intent-Router skill in this repo, take the settled IntentSpec for '<task>' and carry it out as written. Then run the Intent check against the delivered code. Expected output: one line per constraint, each met with a code pointer or not met. Verify that the check result is saved in the same .intent/ file.

Caveat. The README says the post-delivery check runs when the work happens in the same conversation, so a handoff to a separate session may not get this check.

Share: 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