About
intent-driven-development.com is run by J-Tech Japan — a small team that has been working with AI coding agents in production, observed where existing practices stop working, and decided to write down what we found.
Why we built this
We use Codex, Claude Code, and GitHub Copilot daily. We run autonomous agents on real internal projects. We have shipped real systems with AI in the loop, and we have hit the same problems most teams hit: drift over long autonomous runs, re-explaining the same intent on every prompt, reviewing PRs against our own taste because we have no other reference.
Existing solutions — Spec-Kit, Tessl, Augment Intent — solve real problems at the spec layer, but treat intent as a single document or schema. So we built Intent-System, which sits at the IDD layer with a structured intent tree and a deliberate position: Intent-as-source.
Where we are right now
Primary development of intent-cli is largely complete. The system runs continuously on about 5 internal projects today — different shapes, different stacks — and the loop has been operating long enough that we can say with confidence: sustained day-after-day development on top of the /loop is feasible, not just a demo.
intent-cli is now open source. It lives on GitHub under Apache-2.0 and installs in one command, with documentation in English and Japanese and a Discord community for questions. intent-cli on GitHub.
If you are running into the drift problem we describe on this site and want to share your situation, the contact form is the right place. Notes are read; they will not become a marketing list.
The team
Author of Sekiban, an Event Sourcing framework for .NET. Has worked with AI coding tools since the Sonnet 3.5 era and runs the internal Intent-System loop as part of daily development.
What we believe about AI-assisted development
- Intent is the highest-leverage artifact. Spec, code, and tests are downstream and regenerable.
- High-capability AI deserves direction, not restraint. A senior engineer doesn't get a harness; they get briefed.
- Review is intent diffing, not taste matching.
- Small bets, public signal. We launched this site as a small bet. We will let the signal tell us what to build next.
- Honest about scope. We name what Intent-System is not. That honesty is part of the product.
Adopt it with the team that built it
intent-cli is open source and free to run. Getting real leverage out of it — above all, shaping intent that actually steers the work — moves faster alongside people who do it every day. J-Tech Japan, the company behind the project, provides paid consultation to help your team adopt it: from a first Intent Storming session to a loop that keeps shipping in your own codebase.
Quick questions the community can field are answered at no cost on the J-Tech Japan OSS Discord.
Join the Discord →Pair programming, pair storming, and Intent Storming facilitation — hands-on, against your codebase and your domain. A paid consultation engagement with J-Tech Japan.
Tell us about your team in the contact form below and we'll take it from there. More about J-Tech Japan