---
title: "Spec-driven development workflows"
description: "How MySpec runs spec-driven development, what each SDD workflow writes, and how to pick the right one for your project."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.myspec.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Spec-driven development workflows

**Spec-driven development** (SDD) means you agree on a written specification
before anyone writes code. The spec says what to build, why, and how it will be
checked. Your team and your AI coding agent then build from it, and the spec
stays the source of truth when questions come up later.

Think of an architect's drawings for a building. Nobody pours concrete until the
drawings are approved, and every builder on site works from the same set. In
MySpec, the AI plays the architect: it interviews you, drafts each drawing, and
you approve it before the next one starts.

A **workflow** is the method MySpec follows to get there: a fixed series of
**stages**, where most stages write one spec file. You pick the workflow when
you start a chat.

## How MySpec runs SDD

Every Generate workflow follows the same pattern:

1. **Understand**

   The first stage (**Interview**, or **Explore** for OpenSpec) gathers what the
   AI needs: your product, its users and scope, or, for an existing codebase,
   the code itself and the change you want. It writes no file.
2. **Write one spec file per stage**

   Each later stage writes one spec file, building on the files before it. A
   constitution shapes the requirements, the requirements shape the solution,
   and so on.
3. **Review every file twice**

   You read each draft and approve it or ask for changes. Then an independent AI
   reviewer checks it against the earlier files and the stage's rules, and you
   decide which of its findings to apply.
4. **Build from the specs**

   When the last stage is done, you hand the bundle to your coding agent, or
   download it. See [Finish a session and build](https://docs.myspec.dev/guides/finishing-a-session/).

Inside a stage, the chat shows where you are with labels such as
**Requirements · Generating**. Greenfield stages go **Collecting** (a few more
questions) → **Generating** (the AI writes the file) → **Review**. Brownfield
workflows ask their questions up front, so their stages go straight from
**Generating** to **Review**. See
[How each stage runs](https://docs.myspec.dev/guides/generate-sessions/#how-each-stage-runs).

## The workflows

| Workflow | Shown in the picker as | Project type | Stages | Writes |
|---|---|---|---|---|
| [MySpec](https://docs.myspec.dev/workflows/myspec/) (default) | **MySpec generate-workflow (v1)** | Greenfield | Interview → Constitution → Requirements → Solution → Tasks | `constitution.md`, `requirements.md`, `solution.md`, `tasks.md` |
| [MySpec Enterprise](https://docs.myspec.dev/workflows/enterprise/) (Pre-Release) | **MySpec Enterprise generate-workflow (v1)** | Greenfield | Interview → Constitution → Requirements → Solution → Tasks → Quality | The MySpec files, written for enterprise rigour, plus `quality.md` |
| [SpecKit](https://docs.myspec.dev/workflows/speckit/) | **SpecKit generate-greenfield (v1)** | Greenfield | Interview → Constitution → Specify → Plan → Tasks | `constitution.md` (one per project), `spec.md`, `plan.md`, `tasks.md` |
| [MySpec brownfield](https://docs.myspec.dev/workflows/myspec-brownfield/) | **MySpec generate-brownfield (v1)** | Brownfield | Interview → Proposal → Requirements, with an optional Tasks stage | `proposal.md`, a requirements delta, and optionally `tasks.md` |
| [OpenSpec](https://docs.myspec.dev/workflows/openspec/) | **OpenSpec generate-brownfield (v1)** | Brownfield | Explore → Proposal → Specs → Solution → Tasks | `proposal.md`, one delta `spec.md` per capability, `design.md`, `tasks.md` |
| [MySpec edit](https://docs.myspec.dev/workflows/edit/) | **MySpec edit-workflow (v1)** | Greenfield | Reference → Describe → Review | Changes to spec files you already have |
| [MySpec edit for brownfield](https://docs.myspec.dev/workflows/edit-brownfield/) | **MySpec edit-brownfield (v1)** | Brownfield | Reference → Describe → Review, reading your code first | Changes to spec files you already have |

The first five are **Generate** workflows: they write a new bundle of spec
files. The last two are **Edit** workflows: they change files that exist.

Two more workflows build a website instead of spec files:

| Workflow | Shown as | Project type | Stages | Writes |
|---|---|---|---|---|
| [Website artifact](https://docs.myspec.dev/workflows/website-artifact/) (Pre-Release) | **Website artifact (v1)** | Any | Interview → Site plan → Build | One static website artifact: HTML, CSS and JavaScript |
| [Edit website artifact](https://docs.myspec.dev/workflows/edit-website-artifact/) (Pre-Release) | **Edit with AI** on an artifact | Any | Describe → Review | New revisions of one website artifact |

## Choose a workflow

Start from what you are doing, then pick the workflow that fits.

| You want to | Pick |
|---|---|
| Spec a new product or feature | [MySpec](https://docs.myspec.dev/workflows/myspec/). It is the default and suits most new work. |
| Spec a new product for a regulated or audited organization, with measurable quality targets, compliance requirements and release gates | [MySpec Enterprise](https://docs.myspec.dev/workflows/enterprise/) (Pre-Release) |
| Follow GitHub's Spec Kit method and folder layout, for example because your team or tools already use it | [SpecKit](https://docs.myspec.dev/workflows/speckit/) |
| Spec a change to an existing codebase | [MySpec brownfield](https://docs.myspec.dev/workflows/myspec-brownfield/). It is the shorter Brownfield workflow and suits most changes. |
| Spec a change that touches several parts of a system, or follow the OpenSpec method and folder layout | [OpenSpec](https://docs.myspec.dev/workflows/openspec/) |
| Fix, extend or restructure spec files you already have | [MySpec edit](https://docs.myspec.dev/workflows/edit/), or [MySpec edit for brownfield](https://docs.myspec.dev/workflows/edit-brownfield/) in a Brownfield project |
| Build a clickable prototype or a small static website | [Website artifact](https://docs.myspec.dev/workflows/website-artifact/) (Pre-Release) |
| Change a website artifact you already have | [Edit website artifact](https://docs.myspec.dev/workflows/edit-website-artifact/) (Pre-Release) |

Some quick rules of thumb:

- **New code or existing code?** Greenfield workflows design from your answers.
  Brownfield workflows read your code first and describe a change to it.
- **How much paperwork do you need?** MySpec brownfield is the lightest. MySpec
  and OpenSpec are thorough. MySpec Enterprise adds a quality plan and
  enterprise detail to every file, so it takes the longest.
- **Does a tool or team expect a format?** SpecKit and OpenSpec write their
  files in the folder layouts those methods use, so tools built for them can
  read the result.
- **Already have specs?** Don't start a new Generate session to change them. Use
  an Edit session, or `/goback` while the Generate session is still running.

You choose the workflow before you send the first message, and you can't change
it afterwards. To try another workflow, start a new chat.

## Which workflows a project offers

The **project type** you pick when you create a project decides which
workflows a new chat offers:

| Project type | Generate workflows | Edit workflow |
|---|---|---|
| **Greenfield** | MySpec, MySpec Enterprise (Pre-Release), SpecKit | MySpec edit |
| **Brownfield** | MySpec brownfield, OpenSpec | MySpec edit for brownfield |
| **Auto** | All of them | Either |

Website artifact is offered on every project type, after the workflows above.
Edit website artifact is never in the picker: start it from the artifact.

The first workflow in each list is selected by default. When only one workflow
fits, the chat shows a **Using …** badge instead of a picker. See
[Projects](https://docs.myspec.dev/guides/projects/) to change a project's type.

## What every workflow shares

- **You approve every file.** Nothing moves on until you accept a draft and act
  on its review. See [Review each spec file](https://docs.myspec.dev/guides/generate-sessions/#review-each-spec-file).
- **Questions come as multiple choice.** Pick an option, mark several, or
  choose **Other** and type your own answer. An option marked
  **(Recommended)** is the AI's suggestion.
- **`/btw`** answers a side question about the workflow, a spec file or these
  docs without changing the session.
- **`/goback`** returns a Generate session to an earlier spec stage. You can't go
  back to Interview or Explore, and you can't go back once the session is
  complete. See [Go back to an earlier stage](https://docs.myspec.dev/guides/generate-sessions/#go-back-to-an-earlier-stage).
- **Spec depth** sets how many rounds of questions and reviews the AI may use.
  See [Spec depth](https://docs.myspec.dev/guides/generate-sessions/#spec-depth).
- **One language per session.** The AI writes in the language you use MySpec in,
  and the language is locked once the session starts.

## Before a Brownfield workflow

Brownfield workflows must read your code before they write anything. Connect it
before you start the session: run the local MCP server's `reverse` command, or
mount the folder in your browser. If neither is connected, the AI stops and
asks you to connect one. See
[Let MySpec read your code](https://docs.myspec.dev/guides/brownfield/#let-myspec-read-your-code).

## Read each workflow

- [MySpec](https://docs.myspec.dev/workflows/myspec/) — The default for new products: constitution, requirements, solution and tasks.
- [MySpec Enterprise](https://docs.myspec.dev/workflows/enterprise/) — Pre-Release. MySpec with enterprise rigour and an ISO/IEC 25010 quality plan.
- [SpecKit](https://docs.myspec.dev/workflows/speckit/) — GitHub's Spec Kit method: one constitution per project, then spec, plan and tasks per feature.
- [MySpec brownfield](https://docs.myspec.dev/workflows/myspec-brownfield/) — A short workflow for changing existing code: proposal and requirements delta.
- [OpenSpec](https://docs.myspec.dev/workflows/openspec/) — The OpenSpec method for changes: delta specs per capability, design and tasks.
- [MySpec edit](https://docs.myspec.dev/workflows/edit/) — Change spec files you already have and review every change as a diff.
- [MySpec edit for brownfield](https://docs.myspec.dev/workflows/edit-brownfield/) — Edit specs for an existing codebase, checked against your code.
- [Website artifact](https://docs.myspec.dev/workflows/website-artifact/) — Pre-Release. Build a static website from a conversation: site plan, then HTML, CSS and JavaScript.
- [Edit website artifact](https://docs.myspec.dev/workflows/edit-website-artifact/) — Pre-Release. Change a website artifact and keep or discard each new revision.

Source: https://docs.myspec.dev/workflows/index.mdx
