“Which module owns this table?”
The agent searches 416 APIs and 796 files, then guesses from a similar old implementation.
search
search
search
search
search
AI coding context, made routable
Give AI the
project facts it needs.
Flow2Spec gives Cursor, Claude Code and Codex a documented collaboration layer. Route each request to the facts that matter, then start changing code.
route hit4 topics · 300 lines
verified factRedis lock · TTL 10 min
less rediscovery
more building
more building
3AI clients
Cursor · Claude Code · Codex
Cursor · Claude Code · Codex
1 baseShared knowledge layer
.Knowledge/
.Knowledge/
Route firstFind the relevant facts
before changing code
before changing code
The context problem
AI can write.
It just keeps guessing first.
Project constraints live in code, docs, chat and someone's memory. A new session starts from zero, and more searching means more opportunities to misread the system.
“Matcher hit: m-product-review-template-library.”
Read verified facts first, then open only the files that need to change.
✓ matcher hit
One small layer, four jobs
Four layers that
turn context into infrastructure.
Each layer does one job. Together, they give AI collaboration continuity across a team.
Knowledge
A shared base of APIs, boundaries, data rules and workflows.
.Knowledge/topics/*.mdTask
Each developer's local progress, context and user todos.
.task/<developerId>/Rules
One entrypoint, one set of gates, across every agent.
AGENTS.md · .codex/Skills
Reusable workflows for clarifying, building, fixing, syncing and committing.
f2s-*Progressive routing
From one sentence to
the context you can verify.
Don't pour the repository into the model. Match, expand dependencies, and read only the facts relevant to this request.
01A requestNatural language
02RouteMatchers + dependencies
03Read factsOnly the useful context
04Change + syncCode and knowledge stay aligned
✦
More context isn't always better.
It should be just enough, and useful again tomorrow.
A living development loop
Every delivery makes
the next one faster.
The knowledge base grows through real development: verified, revised, and accurately routed into the next request.
- 01Describe the requestSay what needs to change in natural language.
- 02Read relevant factsRoute topics, expand dependencies, fill gaps.
- 03Build and write backCode and knowledge close in the same workflow.
LC
Q7
shared knowledgetopic revision +1reviewed and merged
Built for shared repositories
Two people.
One knowledge base.
Progress stays local to each developer. Confirmed project facts live in shared `.Knowledge/`, so personal todos never become product knowledge.
Explore team collaborationA calmer first run
Three minutes to
give your project a clear path.
You do not need a complete knowledge base first. Initialize, route one real request, and leave behind the first verified fact.
01Write the collaboration skeleton
Initialize
npx @double-coding/flow2spec@latest initWrite the knowledge base, rules and Cursor, Claude Code and Codex entrypoints into the project.
You get.Knowledge/ · AGENTS.md
02Put a request on the route
Describe your first request
“Add pagination to order search; route me to the relevant facts first.”
Start with a real module or change. Build topic facts as they become relevant instead of writing everything up front.
You getMatched topics · filled context
03Leave the result behind
Verify and keep delivering
Facts verifiedReady for the next request
Confirm the routes, topics and revisions are healthy, then turn this verified fact into a shortcut for the next request.
You getReusable project memory
Keep exploring
Start here, then
go at your own pace.
From installation to collaboration, choose what to explore next.