A specification built on
context and evidence.
A six-phase investigation with your approval at each stage. Start from an idea or from the evidence in your existing code. You receive 10 linked documents and an executable kit that can be pushed directly to your repository.
THE SYSTEM PROPOSES — YOU SIGN EVERY PHASE
Two starting points
The phases are the same — what changes is discovery: from a blank page, or from your system's real evidence.
From scratch
Start with an idea and a brief. Discovery explores the problem with you — users, assumptions and risks — before the documents take shape.
Evolution
Start with a connected repository and an existing technical assessment. Discovery assesses the proposed change against real code, identifying affected components and dependencies with file and line references.
Migration
Rewriting an existing system with checks for equivalent behavior. In development, with no announced release date.
In Evolution mode, an investigative agent sweeps a clone of your repository, and every file:line anchor it cites is mechanically validated against the code — a citation that does not match is rejected before reaching the document.
A conversation, not a form
The workspace is one continuous chat: messages, engine activity, decision cards and phase deliveries appear on the same timeline.
The agent proposes changes before they become part of the final document. You review and approve each phase.
The session lives in the database, not in memory: leave, come back tomorrow, and the conversation continues where it stopped.
Requirements, decisions, screens, contracts and stories become a graph with mechanical invariants: nothing orphaned, nothing without evidence.
The approximate execution plan appears at the end — and when there is no basis to estimate, the document says why instead of inventing a date.
Where it fits your workflow
I already use GitHub Spec Kit.
Keep the tools your team uses. Specifications in ArchGenerator add repository investigation, approval at each stage and a verified traceability graph. The kit supports imports and exports with Spec Kit, with documented conversion limits.
Is this not the same as v0 and Lovable?
Application builders implement a product. ArchGenerator prepares the context, specification and acceptance criteria that can guide the coding agent your team chooses.
Why not an architect by the hour?
Human judgment remains essential to product decisions. ArchGenerator adds automated investigation and traceability, while you retain approval at each stage.
A clear specification connects the problem, the decisions and the criteria that guide development.
What you receive
A linked documentation set in the platform and an executable package for your repository.
brief, PRD, design, architecture, data schema, performance budget, roadmap, stories and sensors — navigable on the platform.
the traceability graph travels along: every story points to the requirement it serves, every decision is recorded.
repository export that preserves the files your team has already written.
Bring an idea — or a system.
In the demo, we explore your situation through the discovery phase and show how the specification begins to take shape.