Resources
Where to read more — primary references on SDD, IDD, and the tools in this space, plus a glossary of terms used on this site.
Get the code, the docs, and the community
- intent-cli on GitHub
The deterministic CLI that runs the loop. Apache-2.0. Install: dotnet tool install -g JTechJapan.IntentSystem.Cli
- 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.
SDD landscape
- Understanding Spec-Driven-Development: Kiro, spec-kit, and TesslBirgitta Böckeler · martinfowler.com
Origin of the SDD three-level model.
- spec-driven.mdGitHub Spec-Kit
Frames IDD as the upstream of SDD.
- Tessl Framework documentationTessl
The boldest spec-as-source implementation.
- Augment Intent — overviewAugment Code
macOS app that pairs Spec-anchored discipline with parallel agent execution.
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)
How design / implementation / review are split across three threads, why /loop 5m matches Claude's prompt-cache TTL, and how the Approve edge rewinds the loop to ③.
- Intent System — concept (①)
What Intent and the intent tree are, framed for AI-assisted teams.
IDD origins (the schools)
- What is Intent-Driven Developmentvisrow · Medium
- Intent-Driven Development: Build-First Documentationvisrow · Keyhole Software
- Intent Driven Development is our Current Futurem8a-io · dev.to
- r/IntentDrivenDev — original threadReddit
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.
- /loop 5m
- The local Claude-side cadence on which implementation and review threads continue. The 5-minute interval matches Claude's prompt-cache TTL, so the next wake re-enters the same thread with a warm context.
- Closeout
- Step that writes a merged change back to the intent tree as canonical.