Specz
Get started

✦ Multiplayer product development for AI delivery

Turn team conversation into tested product output.

Every feature becomes a shared room for product, design, engineering, QA, and agents. Promote decisions into a verified brief, deliver it through CLI or MCP, then test what gets built.

Get started See the handoff

Multiplayer feature rooms Verified briefs CLI + MCP delivery

INT-201READY

Delegated from Linear

Bulk CSV import
Maya Torres · Product
FEATURE ROOM / CSV · 4 PEOPLE + AGENT In review
FEAT / CSV

Bulk CSV import

83%
01

As an admin, I want to import contacts in bulk, so setup does not become manual work.

✓
CRITERIA4 / 4defined
APPROVALS2 / 3one pending
TESTS4 / 4passing
LIVE READ CODEX ↔ SPECZ

read get_stories() → 2 stories

read get_criteria() → 4 criteria

read get_code_refs() → 2 refs + contract

run run_validation() → 4/4 passing

HTMLLIVE
MDLIVE
MCPLIVE

01 The context gap

The ticket is not the specification.

A title and a paragraph cannot carry the conversations, decisions, design intent, edge cases, architecture constraints, and proof behind the work. When context stays scattered, every coding session starts with reconstruction—and every missing assumption becomes rework.

01REQUESTLinear

Intent and activity

02INTERFACEDesign

Behavior and states

03BOUNDARIESCode

Contracts and constraints

04DECISIONSPeople

Ownership and approval

05EVIDENCETests

What actually passed

✦ One verified brief

02 The brief

Everything the agent needs. Nothing left implicit.

Every Specz feature gives the team a shared room, then promotes reviewed decisions, implementation context, and evidence into the brief agents consume.

STORY / 01Grounded

ADMIN · CONTACT OPERATIONS

“As an admin, I want to import contacts in bulk, so setup does not become manual work.”
Business value
Reduce setup time
Risk level
Medium
Verification
4 criteria linked
INDEPENDENTVALUABLETESTABLE

03 The gate

The publish button answers to evidence.

Specz checks completeness, team approval, and passing validation on the server. A polished screen cannot bypass a missing requirement.

CONTEXT COMPLETENESSFEATURE / CSV
83%

of what the agent will read

  • Stories2✓
  • Criteria4✓
  • Designs2✓
  • Code refs2✓
  • Approvals2 / 3!
  • Passing tests4 / 4✓
HELD BACK · 1 BLOCKERSERVER GATE
Engineering approval pending

The handoff stays private until every required discipline signs off.

Waiting for evidence

State transitions happen on the server, not in presentation code.

04 The handoff

Readable by the team. Callable by the agent.

Publish once. Review the brief in the browser, give CLI agents durable context inside the repository, or serve the latest approved truth as live MCP tools.

01HTML Hosted brief

Review the complete feature in a browser.

specz.ai/briefs/csv
02CLI CLI-ready Markdown

Load approved context from the repository on every run.

agent/briefs/csv.md
03MCP MCP server

Read the latest verified context as callable tools.

mcp.specz.ai/lumen/csv
AGENT SESSION / CONNECTEDREAD ONLY · TENANT SCOPED
connectcodex ↔ mcp.specz.ai/lumen/csv200 OK
readget_stories()2 stories
readget_criteria()4 criteria
readget_code_refs()2 refs + contract
runrun_validation()4 / 4 passing

05 The flow

From request to ready.

  1. 01
    CAPTURE

    Work enters with its history.

    Delegated requests keep their source, activity, and human owner.

    INT-201Delegated from LinearMaya Torres · Product
  2. 02
    SHAPE

    The feature becomes a shared room.

    Product, design, engineering, QA, and agents resolve questions together, then promote decisions into the brief.

    THREAD 04DECISION 03QUESTION 01PEOPLE 04
  3. 03
    VERIFY

    Evidence closes the gaps.

    Approvals and persisted results map back to the requirement.

    VALIDATION / LATEST4 of 4 passingAPI + end-to-end
  4. 04
    DELIVER

    Every agent run starts informed.

    CLI-ready Markdown and live MCP tools carry the approved context into the build.

    HANDOFF / PUBLISHEDHTML · CLI · MCP100% complete

06 Inside Specz

Not a promise. A working product.

Follow a feature from portfolio status through stories, design, technical context, validation, and a published agent handoff.

app.specz.ai/features/csv
Read the walkthrough transcript
  1. Portfolio: live feature status, completeness, approvals, and tests.
  2. Feature brief: stories and acceptance criteria from the API.
  3. Design context stays beside the brief.
  4. Technical context connects code references and API contracts.
  5. Validation maps persisted tests to acceptance criteria.
  6. The server blocks publishing until every requirement passes.
  7. Intake retains activity, context, and ownership.
  8. People connects ownership and review responsibilities.
  9. A validated feature publishes hosted review, CLI-ready Markdown, and live MCP context.

✦ Ready when the work is

Give the agent a brief it can trust.

Start with one feature. Make every assumption visible. Publish only when the work is ready.

Get started Sign in
Your product context stays scoped to your workspace.
CONTEXT COMPLETE100%
  • Stories ✓
  • Criteria ✓
  • Approvals ✓
  • Validation ✓
PUBLISHEDHTML · CLI · MCP
PRIVATE BETA / REQUEST ACCESS

Join the waitlist

Tell us where better product context would make the biggest difference.

We will only use your details to contact you about the private beta.