Roadmap
intent-cli is now open source on GitHub under Apache-2.0, installable in one command. We run it in production on about 5 internal projects with continuous /loop operation. From here, the focus is the community and support around it.
Where we are
- ·Methodology articulation (Intent-as-source, Compass, Git-AI-Flow)
- ·Site published in EN/JP
- ·Primary development of intent-cli largely complete
- ·Running on about 5 internal projects with continuous /loop operation
- ·Sustained-development feasibility confirmed (the loop keeps producing usable PRs day after day)
- ·Internal testing across multiple project shapes
- ·Private release to early hands-on users ahead of the public launch
- ·intent-cli published on GitHub under Apache-2.0
- ·Installable in one command (dotnet tool install -g JTechJapan.IntentSystem.Cli)
- ·Documentation (EN/JP) and a Discord community
- ·Growing the Discord community; free community Q&A
- ·Paid consultation by J-Tech Japan (pair / Intent Storming)
- ·Iterating intent-cli from real-world usage
Get intent-cli
intent-cli is open source on GitHub under Apache-2.0. Install it with one command and point your AI coding agent at it. Full documentation is available in English and Japanese, and there's a Discord community for questions.
What's settled, and what these signals still shape
The core question — open source or not — is settled: intent-cli is open source. The signals below no longer decide that. They still shape what comes next: what we prioritize, and how the support layer above the open-source core grows. They reach us through inquiries, third-party writing, and partnership conversations.
One part of that is here today: J-Tech Japan, the company behind the project, offers paid consultation — pair programming, pair storming, and Intent Storming facilitation — for teams adopting it. Support & consultation →
| Signal | Interpretation | Tentative direction |
|---|---|---|
| Enterprise teams ask how to deploy this on their own stack | Demand is for a serviced product, not a bare tool | Commercial / managed offering becomes the more likely path |
| Repeated "can I install the CLI?" requests from individual practitioners | The CLI itself is what people want, on their own boxes | OSS CLI surface + commercial layer on top |
| Third-party write-ups or talks reference IDD / this site without us asking | Methodology is taking root on its own merits | Stay concept-first; deepen documentation before product packaging |
| Partnership or integration feelers from adjacent tooling | Category is forming and interop pressure is real | Keep both OSS and commercial options open |
| Direct requests to participate in a paid private beta | Buyers exist before the product is fully shaped | Open the paid private beta sooner than originally planned |
| Few or no inbound across 3 months | The current framing is not landing with anyone | Revisit the methodology articulation before any commercial move |
Two quiet channels we read every day
The table above is the framework. What actually reaches us is more concrete: notes and requests that arrive through the contact form, and mentions on X and other social platforms that touch this site, IDD, or Intent-System. We read them every day. They are not aggregated into a marketing list and we are not chasing volume — we are listening for which kinds of teams are getting stuck where.
A single sentence is enough. "I want to try it," "in our situation it would look like this," "the methodology snags for me here" — each one weighs on what we build next. If anything on this site lands for you, telling us is the most direct way to participate in how Intent-System ends up shaped.
Posts on X and other networks that reference this site, IDD, or Intent-System. We see them, and they matter.
Founder on X (@tomohisa)