Intent-Router

tom@tomrochette.com (Tom Rochette) — Sat, 10 Oct 2026 00:00:00 +0000

Intent-Router is a single MIT skill that compiles a vague request into a typed IntentSpec contract, asking only what the repository cannot answer, then checks the delivered work against that spec one constraint at a time.

The mechanism is the convergence gate plus the cross-session artifact: it probes the repo before interrupting you, refuses to emit while the intent is underspecified, writes the settled contract to .intent/<intent>.intent.yaml with evidence pointers, and writes the delivery check back into the same file so the next session starts from what was decided instead of zero.

What it is
#

An installable skill (npx skills add angel291592/Intent-Router) that runs as parse, resolve, typecheck, emit: it looks up what it can (deps, routes, git history, docs, ticket systems), asks the one question no file holds, calls out contradictions and disproved premises, and refuses to emit while anything material stays open. The emitted IntentSpec is machine-readable YAML whose state records whether it is still waiting on a question, settled, or carried out, and a later session reads it before probing anything, so an answered question is never asked twice. When the work is handed off, the skill checks the result against the spec constraint by constraint and records the outcome in the artifact. The README positions it against plan modes (which prefer looking up over verifying premises), spec-kit (which asks you to buy its whole workflow), Kiro’s specs (three files and an IDE), and Jev and Laya (typed decisions one layer down, the input layer this skill feeds).

Status
#

Young and fast-rising: 1,015 stars and 121 forks as of 2026-10-10, created 2026-09-22, pushed 2026-10-09, with four releases in its first three weeks (v1.3.0 on 2026-10-09, v1.0.0 on 2026-09-23). A thousand stars in nineteen days is the steepest adoption curve in this category’s recent additions, but the independent footprint has not caught up: a Hacker News search returns no thread about it as of 2026-10-10.

Strengths
#

The delivery check is the part most spec tools skip: checking built work against the spec it came from, one constraint at a time, is where spec drift actually gets caught.
It respects the reader before the writer: probing the repo, tickets, and docs first means the human sees one question instead of an interview.
The cross-session YAML artifact with evidence pointers makes intent durable across agents and teammates without a platform.
Zero install surface beyond a skill: no workflow to adopt, no daemon, no IDE, and it runs prompt-only at its L0 backend.

Cautions
#

The evidence is self-published and small: the delivery report of 2026-09-24 compares 5 bare runs against 3 skill runs (mean 5.0 versus 6.0 of 6) in one harness on one model, and the report discloses that the bare arm needed the skill explicitly denied because an installer test had left a copy in user-level skills.
Three weeks old with a solo maintainer: the IntentSpec format and the four-state model can still move under you.
The star curve (1,015 in nineteen days) is social momentum, not validation; there is no independent replication of the delivery numbers as of 2026-10-10.
It is upstream of typed decision models (Jev, Laya), so teams already running those need to decide which layer owns the clarification step.

Pricing
#

Does not apply: MIT, free, no paid tier recorded as of 2026-10-10.

Compared to
#

GitHub Spec Kit: the full constitution-plus-workflow ceremony; choose Spec Kit when the whole team adopts the process, Intent-Router when you want the contract without the ceremony.
cc-sdd: a 17-skill SDD workflow installed per agent; cc-sdd covers the full spec-design-tasks pipeline, Intent-Router covers only the front door and the delivery check.
Superpowers: the mandatory skill suite with brainstorming from session start; Superpowers enforces a method, Intent-Router is opt-in per request.

Bottom line
#

Recommended for agent users whose requests arrive vague and whose follow-up sessions start from zero: the typed artifact plus the delivery check is a cheap upgrade to any harness. Not for teams needing enforced process (that is Superpowers), and not for anyone who requires third-party-validated numbers before adopting a three-week-old skill.

Changes
#

2026-10-10 - Created from the spec-driven-development resolution pass, choosing this category over task management because the artifact is a spec contract with a delivery check, not a task record.

References
#

https://github.com/angel291592/Intent-Router - repository: README, pipeline, comparison table, license
https://api.github.com/repos/angel291592/Intent-Router - stars, forks, issues, creation and push dates as of 2026-10-10
https://api.github.com/repos/angel291592/Intent-Router/releases - v1.3.0 published 2026-10-09 and the release train
https://raw.githubusercontent.com/angel291592/Intent-Router/main/README.md - the convergence design, artifact model, and prior-art comparison
https://raw.githubusercontent.com/angel291592/Intent-Router/main/evals/reports/2026-09-24-delivery-opencode.md - the self-published delivery report behind the numbers and the contamination check
https://hn.algolia.com/api/v1/search?query=Intent-Router&hitsPerPage=5 - the no-thread community-footprint check as of 2026-10-10

intent-specs on tomrochette.com

Intent-Router

What it is
#

Status
#

Strengths
#

Cautions
#

Pricing
#

Compared to
#

Bottom line
#

Changes
#

See also
#

References
#

intent-specs on tomrochette.com

Intent-Router

What it is #

Status #

Strengths #

Cautions #

Pricing #

Compared to #

Bottom line #

Changes #

See also #

References #

What it is
#

Status
#

Strengths
#

Cautions
#

Pricing
#

Compared to
#

Bottom line
#

Changes
#

See also
#

References
#