Docs/The web app
FOR HUMANS

The web app: write, review, publish.

How to set up an account and workspace, write and publish specifications, review proposals from AI agents, and move goals from idle to done.

Core concepts

Read this once. Every screen and every MCP tool builds on these terms.

Workspace
An isolated container for one project. Holds specifications and goals. Has members with roles.
Specification
A requirements document. Also called a spec. Comes in two scopes.
Feature scope
A spec with two sections: product (the problem and user context) and engineering (technical guidance for implementers).
Foundational scope
A spec with one foundational section. A self-contained document for cross-cutting concerns such as technical context, decision logs, and glossaries.
Section
A part of a spec that holds content. Sections version independently.
Draft
An editable copy of a section. Work in progress.
Proposal
A draft submitted for human review. Read-only until a person publishes or rejects it.
Published
The current accepted version of a section. Older published versions stay in history.
Goal
An implementation task linked to a specification. Carries a status and an assignee.
Assignee
The one AI agent or person responsible for a goal. Reassigning a goal is how work is handed off.
Activity stream
The running log on a goal: questions, blockers, and proposed spec changes.

Goal statuses

IdleIn progressDone

Getting started

Create an account

Go to the sign-up page and you'll be asked for:

  • A display name (optional).
  • Your email.
  • A password of at least 8 characters — a strength meter shows as you type.

Submit and you land on a Check your email screen. Open the email, click the verification link, and you're signed in and sent to your workspace list.

Arrived through an invitation link?
Sign in or sign up with the email the invitation was sent to. The login screen shows Sign in to accept your invitation in that case.

Sign in

Enter your email and password on the login page. From here you can also resend a verification email or start a password reset.

Workspaces

The workspace list

After login you land on Workspaces, a card grid of every workspace you belong to. Each card shows the name, description, and member count. If you own a workspace, a menu on the card gives you Workspace settings and Leave workspace.

Create a workspace

Click New workspace, enter a name and description, and submit. You go straight into the new workspace.

The workspace dashboard

Inside a workspace you have three tabs:

  • Dashboard — the overview, with recent activity and highlights.
  • Specifications — lists feature specs and foundational documents.
  • Goals — lists every goal.

From here you create specs, foundational documents, and goals.

Workspace settings

Workspace owners get a settings page with:

  • Name and description, editable.
  • Members, with a role badge on each: owner or member. You can remove a member as long as one owner remains.
  • Invite members. Search for a user by name, then click to send an invitation. A toast confirms it was sent. Pending invitations show with a Withdraw button.
  • AI agents. Create and manage the agent users that connect over MCP and pick up goals.
  • Delete workspace, which asks for confirmation.

Accept an invitation

Click the invitation link. SpecDeck accepts it and sends you to the workspace dashboard. If you are signed in as the wrong account, it offers to sign you in as a different one.

Specifications

Create a specification

From the Specifications tab:

  • New specification creates a feature-scope spec with a product section and an engineering section. You can seed either section from a template.
  • New document creates a foundational-scope spec with a single foundational section.

Edit a section

Open a spec to see its section tabs and the section editor. Each section is Markdown. To change a published section you work through a draft:

  1. 1
    If no draft exists, the section shows Create Draft. Click it. SpecDeck copies the current published content into an editable draft.
  2. 2
    Edit the Markdown.
  3. 3
    The versions rail on the right lists every branch and version: drafts, proposals, published versions numbered v1, v2, and so on, and published branches. Click any entry to view or edit it.

Add a Mermaid diagram

Sections are plain Markdown, so you can add a diagram with a fenced code block tagged mermaid. Put the diagram source inside and close the fence. There is nothing to enable or store.

MARKDOWN
```mermaid
graph LR
  A[Draft] --> B[Proposal] --> C[Published]
```

The diagram renders in the published spec view and the read view of sections, in goal views (summary and acceptance criteria), in the Markdown editor live preview pane, and in the Assistant chat. The raw Markdown view always shows the source.

Switch to the Markdown editor to preview a diagram
The Visual editor still shows a mermaid block as a code block. Switch to the Markdown editor to see it rendered in the preview pane. In diff and merge views an unchanged, added, or removed diagram renders (added and removed ones tinted), while an edited diagram falls back to its source so the change stays legible.

Submit and publish changes

When a draft is ready, publish it back to the section:

  • No conflict: the draft publishes immediately as a new version.
  • Conflict: SpecDeck opens the merge screen so you can resolve it.

Review a proposal

When an AI agent finishes editing a section, it creates a proposal. A proposal is a draft marked ready for review, and it is read-only until a person acts on it. When a proposal, or your own draft, conflicts with changes published since it branched, publishing it opens the three-panel merge screen:

LEFT (OURS)
Your draft changes, shown as a diff.
MIDDLE (CONFLICTS)
Each conflicting block, with a choice per block: Base (original), Accept Ours, Accept Theirs (the proposal), or Edit Manually.
RIGHT (THEIRS)
The proposed changes.

A counter tracks X of Y conflicts resolved. Once every block is resolved, click Complete merge. The result publishes as a new version and you return to the spec.

The Assistant

The Assistant is a panel that helps you write and refine specs. Open it from the toggle next to the section editor, and it also appears on the new-goal form. It works on the current section. It does not write code.

It can:

  • Chat about the section you have open.
  • Run quick actions. Under / Actions it offers Spelling & grammar and Workspace consistency, which checks the section against the published specs in the workspace.
  • Propose rewrites. Suggested edits arrive as an inline diff. You review and accept them before anything is published.
  • Draft a goal. On the goal form it can draft a goal from the selected specification.

An AI Level dropdown sets how much capability each request uses, from Lite (fastest and cheapest) up to Max (most capable). You choose the level, and SpecDeck runs the right model behind the scenes. Free workspaces include Lite and Standard; organization workspaces add Pro and Max. Usage is covered by a weekly per-user AI budget, shown as a meter in the panel, that resets each week.

Built in, and separate from coding agents
The Assistant runs inside the web app and needs no external tool. It is separate from the AI coding agents (Claude Code, Cursor, Codex) that connect over the MCP server. Your specifications and prompts are not used to train AI models.

Goals

Create a goal

From the Goals tab, New goal is a split button:

  • The main action opens the goal form. Link the goal to a specification, give it a title, and optionally add a summary and acceptance criteria.
  • The dropdown offers Generate goal prompt, which gives you a prompt to hand to an AI agent so the agent creates the goal through the MCP server instead.

On the goal form, the Assistant can draft a goal from the selected specification.

The goal view

A goal page shows:

  • Header: title, author, created date, and buttons to edit the goal and change its status or assignee.
  • Status: idle, in progress, or done, set from the header.
  • Summary and acceptance criteria: add or edit these inline.
  • Pending questions: questions an AI agent asked, each with an Answer button. Answer them here to unblock the agent.
  • Activity stream: every entry in time order, each tagged with a type and an author icon for human or AI. Blockers have a control to mark them resolved. At the bottom you can add a Note, Ask question, or Flag blocker.
  • Right rail: the goal's assignee, any spec-change branches this goal produced, and the linked specification section.

How goals move

A goal starts idle. Assign it to an AI agent or a teammate and it moves to in progress. When the work is finished and any proposed spec changes are reviewed, mark it done. Agents can claim, update, and submit goals through the MCP server.

IDLE
Created or awaiting input
IN PROGRESS
Assigned and underway
DONE
Work finished and reviewed

User settings

Your personal settings page covers:

  • Appearance: dark or light mode, saved on toggle.
  • Profile: display name (editable) and email (read-only).
  • Date and time: timezone, date format, and 12 or 24 hour clock, with a live preview.
  • Change password: current password plus a new one of at least 8 characters.
i
Save behavior
All settings except the theme toggle need an explicit Save.
CONTINUE READING
FOR AI AGENTS
The MCP server
OAuth flow, agent setup, and the full tool reference.