SpecGraph
Request access
Specgraph v2 · now in private beta

Coding is solved.
Specs aren't.

AI can write the code. SpecGraph hands it the spec: discovery on the codebase you already run, every constraint and acceptance criterion, sealed into a contract it implements verbatim.

Request accessSee the 60-second tour

Brownfield-first. Discovery reads the system you already run, six phases pin down what ships next, and your agent cites the pack in every PR.

spec pipelinestage 01 / 05
  1. 01your codebase
    app/lib/convex/components/schema.tsauth/…
  2. 02discovery

    42 modules · 9 owners · 7 debt flags

  3. 03spec model

    constraints · acceptance criteria · tokens

  4. 04sealed pack · v1.0.0

    8 files · signed · immutable

  5. 05your agent

    implements verbatim · cites the spec

→ served over MCP to claude-code / codex
§ The 60-second tour

Five scenes from the real product. Played back, slowed down.

Every panel below is a stylised stand-in for an actual surface in SpecGraph 2.0. The choreography is exactly how the app behaves, just slow enough to read.

01 · Voice interview

The agent does the asking.

A guided voice interview by phase: vision, features, brief, design, architecture, quality, security. Every answer fills a field. Every field tracks who answered, when, and why.

acme · v3-portal · visionVoice interview
specgraph agentidle
rec · 00:42
Tell me what you're trying to build, in one sentence.
A patient-intake portal for a 14-clinic group, EHR-integrated.
Got it. EHR: Epic, Cerner, or something internal?
Epic. With SMART-on-FHIR scopes, HIPAA in scope.
Drafting vision. I'll mark the EHR + compliance details into the brief.
02 · Mockup → spec

Bring the prototype. Keep the plan.

Sketch the UI on Lovable, v0, Base44 or Bolt. SpecGraph reads the mockup, extracts tokens and surfaces, and seeds the brief. The prototype becomes evidence. Not a throwaway.

acme · v3-portal · mockupMockup → spec
source
prototyped onv0

shadcn-shaped UIs in seconds. Drop the URL or a screenshot. SpecGraph extracts tokens, infers surfaces, and pre-fills the brief.

extracted
design tokens
  • Primary#0a584a
  • Surface#f5f3ec
  • Muted#6b7280
  • Radius8px
  • TypePlus Jakarta
spec scaffold seeded
  • vision.md ← inferred from copy & imagery
  • design.md ← tokens + components extracted
  • features.md ← 11 surfaces detected
  • architecture.md ← stack proposal: Next, Convex, Tailwind
  • open-questions.md ← 6 prompts for the interview

Prototype the feel on Lovable, v0, or Base44. Ship the plan from SpecGraph. The mockup becomes evidence inside the spec, not a throwaway artifact.

03 · Discovery · brownfield

Already shipping? Bring the repo.

Discovery scans an existing codebase in one pass: modules, ownership, stack, tech-debt, compliance gaps. Then seeds a SpecGraph project on top of it. Same six-phase lifecycle, pre-warmed. Ready for scale, ready for the next feature.

acme · v3-portal · discoveryBrownfield discovery
scanning repolive
  • tssrc/auth/legacy-sso.ts612 LOC
  • tssrc/intake/forms/v1.tsx1.4k LOC
  • tssrc/intake/forms/v2.tsx920 LOC
  • tssrc/integrations/hl7v2.ts488 LOC
  • tssrc/integrations/fhir-r4.ts766 LOC
  • infinfra/terraform/main.tf324 LOC
  • infinfra/k8s/intake-svc.yaml
  • cfgpackage.json
  • cfgtsconfig.json
  • docdocs/runbook.md
  • docdocs/2024-q4-postmortem.md
findings
  • stackNext.js 14 · Convex · Tailwind 3 · Resend
  • duplicationTwo intake-form implementations (v1, v2)
  • tech-debtLegacy SSO bridge predates FHIR R4 migration
  • compliancePHI flows uncovered by audit log in 6 paths
  • readyWorkspace scaffolding maps cleanly to BMAD epics
seeded into the spec
  • discovery.md
    modules · ownership · LOC heatmap
  • vision.md
    inferred from README + postmortems
  • architecture.md
    stack + boundaries · alternatives noted
  • open-questions.md
    12 prompts for the voice interview
  • next-feature-backlog.md
    8 candidate epics, scored
ready for scale

Discovery turns a brownfield repo into a SpecGraph project in one pass. Same six-phase lifecycle, just pre-seeded. From here the team adds new featuresunder the same spec, without retro-fitting briefs by hand.

scale-ready·audit-clean
04 · Async wishes

Every team gets a turn.

Engineering, design, compliance, finance, operations. Structured surveys, no calendar warfare. Wishes flow into the spec automatically. Typed, attributed, scoped.

acme · v3-portal · wishesAsync wish capture
spec · visionlive
drafting

Patient-intake portal · 14 clinics · Epic SMART-on-FHIR · HIPAA in scope.

wishes captured0 / 6
ProductM. Carr

Single intake form across regions

Patients shouldn't repeat themselves at every clinic.

wish
EngineeringA. Petrov

FHIR R4 only, no HL7v2 bridge

Drop the legacy bridge. It owns 40% of incidents.

needs review
ComplianceL. Owusu

Audit log retained 7y, immutable

Required by HIPAA + state rules in NY and CA.

wish
DesignK. Sato

Mobile-first; staff use phones too

Field staff and rural clinics rely on tablets, not desktops.

wish
FinanceR. Diaz

Cap initial scope at $480K

Anything beyond v1.2 needs a fresh purchase order.

blocking
OperationsJ. Hale

Pager rotation: weekday 8–18 only

Don't promise a 24/7 SLA we can't staff yet.

needs review
05 · Conflicts → resolution

Disagreement before code, not after.

Conflicts surface with severity. Three unification strategies sit side by side. Stakeholders vote. Audit log writes itself.

acme · v3-portal · resolveConflict resolution
conflict 1 of 3blocking
Engineering

FHIR R4 only, drop HL7v2 bridge

Operations

Three of our partners only emit HL7v2

resolution

Keep HL7v2 → FHIR adapter for partners A, B, C; sunset roadmap stamped to Q2.

approved · 4 of 4 stakeholders·logged to audit trail
unification strategy

Compare side-by-side, pick a strategy, and the spec rewrites itself. Every decision lands in the audit trail.

06 · BMAD pack

Eight files your agent can read.

When the spec is sealed it ships as a BMAD pack: product-brief, prd, architecture, ux-design, epics, qa-test-plan, project-context, CLAUDE.md, plus per-story implementation. Stamped, immutable, signed.

acme · v3-portal · pack v1.0.0BMAD pack
files
planning artifacts
implementation
product-brief.mdsealed · v1.0.0
07 · Tailor-made skills

Subagents shaped to your spec.

SpecGraph emits project-specific skills: tiny, scoped subagents that already know your PRD sections, your tokens, and your constraints. Loadable by Claude Code, Codex and Copilot. Your agent stops re-deriving context every session.

acme · v3-portal · skillsTailor-made skills
generated from your spec0 / 5
  • epic-sso-bootstrapauth

    Bootstraps SMART-on-FHIR SSO flow with PRD-bound scopes and Epic-specific quirks.

    ClaudeCodex
  • fhir-bridge-adapterintegration

    Translates HL7v2 messages into FHIR R4 resources for partners A, B, C. Adapter tagged to sunset.

    ClaudeCopilot
  • audit-log-immutable-writercompliance

    Enforces 7y, immutable, cryptographically chained audit writes for every PHI mutation.

    ClaudeCodexCopilot
  • patient-intake-validatorux

    Form-level field validator wired to PRD §2.1. Knows which fields branch by clinic region.

    Claude
  • specgraph-discoverymeta

    Re-scans the repo when scope changes; emits a fresh discovery.md and updates open-questions.

    ClaudeCodexCopilot
08 · Agent handoff · MCP

From contract to commits.

The pack and its skills are served over MCP to your coding agent. Claude Code, Codex or Copilot execute it verbatim. They cite the spec back in every PR. The contract is the wire.

claude-code · mcp://specgraphagent handoff
works with
  • Claude Codeanthropic
  • Codexopenai
  • GitHub Copilotgithub
terminal · zshconnected
$ claude-code ↳ load specgraph pack
thinking
09 · Live progress · amend

Watch it happen. Amend on the fly.

Agents stream every started task, every commit, every question back into SpecGraph in real time. Spot drift early. Edit a phase. Re-seal the pack. Agents read the diff over MCP and resume. The loop is closed.

acme · v3-portal · progressLive progress · dashboard
progress feedstreaming
  1. awaiting next event…
§ Numbers

Months become weeks. Weeks become Friday.

The numbers that matter aren't lighthouse scores. They're how long it takes for a sentence in a meeting to become a tested pull request.

Time-to-spec11weeks0weeksfrom kickoff to a sealed PRD
Cross-team meetings37meets0meetsstructured wishes do the rest
Departments aligned2teams0teamsasync voice + survey, no warfare
Spec → code latencyweeksminutesagents read the pack directly
Re-spec after kickoff62%0%conflict resolution before code

Numbers are anonymized aggregates from current pilots: financial services, healthtech, public-sector logistics. We'll send the full benchmark on request.

§ The org layer

Beyond a single spec, an org-wide context.

SpecGraph isn't one project at a time. The platform layer carries your design system, your tech stack, your compliance framework, and your portfolio of features across every project. Each new spec inherits what the org has already decided.

Knowledge base

Your design system, stack, and compliance, quoted by every spec.

Upload a design system, an approved tech stack, your security framework, and the templates you reuse. Every new project pulls from the same shelf. No copy-paste, no drift, full attribution back to the source entry.

  • Design tokens
  • Tech stack
  • Compliance
Portfolio

Every feature, prioritised, across every project.

A single board for the whole org. Score by impact, lock priority by quarter. Each lit row converges into a sealed spec, without losing the frame the leadership team agreed on at the offsite.

  • P0 / P1 / P2
  • Quarter views
Discovery

Bring an existing repo into SpecGraph in one pass.

Brownfield-friendly. Discovery scans the codebase, infers stack and modules, drafts a discovery.md, seeds vision and architecture, and lists the open questions the voice interview should ask first. Same six-phase lifecycle, pre-warmed.

  • Repo scan
  • discovery.md

What gets specified and built

  • Fullstack web apps
  • Backend APIs
  • Microservices
  • ML pipelines
  • Data schemas
  • Mobile apps
  • CLI tools
  • Infrastructure-as-code
  • Design systems
  • Data semantics

SpecGraph is not only for fullstack apps. Any software artefact with stakeholders, constraints, and an AI agent on the other end benefits from a sealed spec, and from a contract that travels with the code.

§ For

Built for orgs that can't afford ambiguity.

Six verticals where a half-written brief costs more than an engineer-month. SpecGraph is built for the room where that cost is already counted.

  1. 01Product orgs at scalecross-team specs without rituals that don't ship.
  2. 02Enterprise ITaudit-grade lineage from wish to commit, every time.
  3. 03Government & defenceprocurement-friendly artefacts. Immutable approval log.
  4. 04HealthtechHIPAA and FHIR scoping baked into the brief, not bolted on.
  5. 05Financial servicesrisk and compliance referenced as constraints, not vibes.
  6. 06AI-native teamsMCP-served packs your agent executes verbatim.
§ Closing

Stop vibe-coding solo.
Start shipping with the whole org aligned.

AI coding agents are spectacular. They are also obedient. They build what the spec says to build. SpecGraph is what makes the spec worth obeying. Every department, on the record. Conflicts resolved before code. One sealed pack, served over MCP.

Request access

Private beta. We're onboarding two teams a week.