Resources

Get the code, the docs, and the community

• intent-cli on GitHub

  The deterministic CLI that runs the loop. Apache-2.0. The npm path is npm i -g intent-system; it provides the intent-cli command without a .NET SDK. npx runs it without a global install.

• Documentation (EN / JP)

  Install, project start, Intent Storming, the loops, recovery, and the command reference.

• J-Tech Japan OSS Discord

  Community questions and discussion — free.

From the Intent System host

Long-form writeups on how Intent-System runs today. Public links coming as soon as the host publishes them — until then, the titles describe what each piece covers.

• Intent System — driving implementation and review autonomously with three threads (③ Implementation loop)

  A historical deep dive into the still-supported timer-loop alternative: three independent threads and the Approve edge that rewinds the loop to ③.

• Intent System — concept (①)

  What Intent and the intent tree are, framed for AI-assisted teams.

Terms used on this site

Intent

The why and what-to-achieve of a system, expressed in customer-facing language.

Intent Tree

Hierarchical / relational organization of intents under Purpose / User Context / Means.

Intent Storming

The process of structuring technology and intent as the product owner, seeding the intent tree. Same posture as Brainstorming or Event Storming, except the artifact you walk away with is an intent tree. It runs as a group workshop (product owner + engineers, designers if the surface matters) or solo — one person acting as product owner while the AI, guided by intent-cli, interviews them with background / options / pros-cons / recommendation for each open decision.

Intent-as-source

Stance that the intent tree is the source of truth, with spec and code as downstream artifacts.

Intent Compass

Direction-and-decision-rights packet given to a capable AI for a slice of work.

Slice

An issue-ready unit of work cut from the intent tree.

Design loop

The cycle inside the design thread: write packet → wait for the merge → drive the running app (Computer Use or Playwright CLI) → judge the result against intent → emit the next packet (adjustment, bug-fix, or new slice). This is what keeps Intent-System from drifting into vibe coding — human-authored intent is added on top of what was actually built, with screen-level evidence attached.

Packet

A work unit one level above an Issue. Carries explicit references to the intent it serves and the verification points the implementation must satisfy. Packets are generated by the LLM in the design thread; the design thread also runs the merged app and folds screen-level observations back in before promoting a packet to an Issue.

solo-conductor (1 thread + subagents)

The single-seat team mode, released in intent-cli v0.32.0 (preview-through-1.x) and the recommended way to start. One conversation, the conductor, carries architect, orchestrator, and builder; every review and re-review goes to a fresh independent subagent the conductor starts. No session transport, seat roster, or supervision cycle is needed.

Subagent

An isolated agent that a thread starts inside its own session. In solo-conductor, the reviewer is a new subagent for every review; it receives only the packet, review context, PR body, and read-only clone paths, never the implementation conversation.

herdr-only orchestration

The recommended session transport for collocated multi-seat teams in intent-cli v0.32.0 (fewer dependencies). The coding agent or operator runs herdr after approval; intent-cli emits guidance and records or validates the topology. agmsg + herdr is deprecated.

agmsg

A signal transport used with herdr. agmsg + herdr is deprecated as of intent-cli v0.32.0: it still works and remains the default when no transport is recorded, and removal is planned only after current users are checked.

file-backed delivery

Delivery declared with delivery_method: file-backed. It persists a durable, addressable task envelope and delivers a one-line pointer; without the declaration, delivery remains inline.

named branch lane

A registered/default or explicitly selected lane for packet routing, recorded as branch_lane with a routing_snapshot. This is a released preview-through-1.x capability, not a 1.0 compatibility guarantee. intent-cli proposes and records the lane; it does not create or manage branches.

Git-backed claim

Multi-user ownership recorded under .intent-cli/claims/ through claim acquire and claim verify. This is a released preview-through-1.x capability, not a 1.0 compatibility guarantee. Only the successful immutable plain push owns the claim; claim before scaffold.

prompt class and scope

A literal prompt class plus scoped approval policy, including answerable_by, a hard non-overridable risk floor, and live-dialog compare-and-swap. This is a released preview-through-1.x capability, not a 1.0 compatibility guarantee. Unknown or unmatched prompts escalate.

team_mode=authoring-only

A released preview-through-1.x authoring capability and front door for interviewing and shaping intent, authoring packets, and publishing issues. It has no delivery topology or seats; delivery mode remains the default and delivery supervision is not applicable here. It is not a 1.0 compatibility guarantee.

/loop 5m

One scheduler choice for the supported three-thread timer-loop alternative. It is an alternative to the four-role orchestration model and to single-seat solo-conductor.

Closeout

Step that writes a merged change back to the intent tree as canonical.