Built for product and engineering teams

Spexd holds your product’s features, requirements, designs and tasks on one line that your team and your coding agents build from.

It understands how they relate to each other, which ones a change will affect, and how each one maps to your actual codebase. That lets you and your agents understand your product, the decisions behind it and the constraints it has to meet.

  1. FeatureFEAT-2
    Password self-service

    What are we building, and why?

    A capability someone could demo or point at: the problem it solves and the value it brings.

    e.g. Password self-service

  2. RequirementREQ-4
    Reset links expire after one use

    What must it do?

    One thing the feature has to do, proven by acceptance criteria that say how you’ll know it’s done.

    e.g. Reset links expire after one use

  3. DesignDES-12
    Single-use token validation

    How will it work?

    How the system meets a requirement: the architecture, data and flows behind it.

    e.g. Single-use token validation

  4. TaskTASK-32
    Offer a new link on rejection

    Who’s building which part?

    A unit of work that delivers a design, linked to the branches and pull requests that ship it.

    e.g. Offer a new link on rejection

01 · Discover

Start from the product you already have.

Connect your repositories and bring your existing docs and tickets. Spexd discovers your features, requirements and designs from what is already there, because not everyone has the luxury of a greenfield product.

Setup’s import step: fifteen features discovered from the connected sources, one fully imported with its requirements and designs listed beneath it
  • Discovers features, requirements and designs from your code, docs and tickets
  • Discovered specs are put to a human for initial validation
  • Tied to your actual code, from day one

02 · Regulatory packs

Start with the regulation already written down.

Apply a requirement pack, such as GDPR or GLI-33, and its requirements land in your own specification, reused wherever you already cover them. Each criterion records where it came from, so anyone can see why a rule exists, how regulations are being met, and (hopefully not!) any gaps that exist.

The requirement packs catalogue with the GLI-19 pack open: each acceptance criterion cites the clause it comes from and is marked regulatory or legal
  • Ready-made packs for GDPR, iGaming, Fintech and more
  • Understand the exact constraints on your product and how it meets them
  • Every criterion keeps its source and its evidence

03 · Traceability tree

Every decision, and the reason behind it.

Each feature holds its requirements, the acceptance criteria that prove them, the designs that meet them and the tasks that build them. Anyone on your team can open a task, see why it exists and how it fits into the big picture. Coding agents get the same context before they start: not just the task, but the context, constraints and decisions it should work within.

The navigator open on a requirement: its feature’s requirements to the left, its acceptance criteria each linked to the design that meets it, and those designs in the column to the right
  • Product, requirements and architecture in one place
  • Decisions that outlast code, not constrained by repository structure or organisational silos
  • Follow any link up to the reason or down to the code

04 · Specs, for humans

AI first doesn’t mean Markdown for everyone.

Every spec in Spexd opens in a rich editor that anyone in your business can read and edit. AI first doesn’t mean sacrificing the human experience, or forcing everyone to work in Markdown. People and agents edit the same document together, and Spexd writes an overview of each spec so you can skim it before you dive in.

PlaceholderA spec open in the editor, with a collaborator’s cursor and its overview above it
  • Friendly spec reading and writing, no Markdown required
  • Real-time collaboration across people and agents
  • Automatic overviews and summaries, so specs are easy to skim

05 · Approvals & invalidation

Decision making, without decision fatigue.

Accountability through human approval: every approval records who agreed to which exact version. When a requirement changes, Spexd works out which approved designs and tasks the change actually reaches and sends those back for review with the reason, before anything is published.

PlaceholderThe publish-impact preview dialog
  • Full, easily readable, auditable history of all changes
  • See a change’s impact without relying on institutional or siloed knowledge
  • Decisions presented in context, at the right level, so you only worry about what matters

06 · Relations

Catch the conflict between two teams before it ships.

Spexd reads across your whole specification, not one project at a time. It finds requirements that contradict each other, work that overlaps, and changes in one place that another part of the product has to honour, and shows them to your team and your agents.

A design’s related specifications: a requirement it contradicts, quoted side by side, and the designs and requirements its change affects
  • Contradictions and overlaps across projects and teams
  • The knock-on effect of one change on someone else’s work
  • The same findings for people and coding agents

07 · Reviews

Keep the spec and the code telling the same story.

Before an approver sees a draft, Spexd flags any gaps. With GitHub connected, your specs are reviewed as your code changes, ensuring they always stay up-to-date and accurate. Similarly, pull requests are reviewed against your requirements, ensuring change is well informed and intentional. Every finding cites what it read, and a person decides what changes.

PlaceholderA review verdict on a design, citing the commit it read
  • Gaps flagged as soon as a spec is marked ready for review
  • Designs judged against the code that implements them, acceptance criteria judged against the tests that prove them
  • Pull requests reviewed against the specs they affect, whether or not the author realised

08 · Ask Spex

Ask your product a question.

Ask Spex is the assistant built into Spexd. It answers from your current specs and your code. It can draft and update specs as well, and shows you every change before it is saved.

Ask Spex answering “What RG features does Longshot offer?” with the responsible gambling feature, its goals and the requirements it is built from
  • Answers grounded in your current specification and code
  • Drafts requirements and designs for you to review
  • Everything it can do is also available to external agents over MCP