---
title: "MySpec Enterprise workflow"
description: "MySpec with enterprise rigour. Compliance and governance in every file, plus a fifth Quality stage that writes an ISO/IEC 25010 quality plan."
---

> 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.

# MySpec Enterprise workflow

> **Pre-Release**
>
> This feature is still rolling out, so it may not be available in your
> organization yet. It can change before general release.

The **MySpec Enterprise** workflow is the [MySpec workflow](https://docs.myspec.dev/workflows/myspec/)
written for organizations that must prove their quality: regulated industries,
teams with auditors, or anyone who signs off a release against written gates. In
the picker it is **MySpec Enterprise generate-workflow (v1)**.

It runs the same stages as MySpec, asks for more detail in each, and adds a
fifth spec stage, **Quality**, that writes a quality plan.

## At a glance

- **Best for:** New products that need measurable quality targets, compliance and release gates
- **Project type:** Greenfield (or Auto)
- **Stages:** Interview → Constitution → Requirements → Solution → Tasks → Quality
- **Files:** `constitution.md`, `requirements.md`, `solution.md`, `tasks.md`, `quality.md`
- **Folder:** `specs/<bundle>/`

Expect a longer session than MySpec: there is one more stage, and every file
carries more detail.

## How it differs from MySpec

Each inherited stage asks the same kind of questions as in
[MySpec](https://docs.myspec.dev/workflows/myspec/#stages), and its file adds:

| File | Adds |
|---|---|
| `constitution.md` | **Quality Principles**, **Compliance & Regulatory Obligations**, **Governance & Decision Rights** and a **Definition of Done** |
| `requirements.md` | An ISO/IEC 25010 quality characteristic and a verification method on every non-functional requirement. Compliance obligations become their own requirements (`CR-001` …), and the file lists its **Assumptions & Constraints**. |
| `solution.md` | **Architecture Decision Records** (`ADR-001` …), **Quality Attribute Tactics** and **Operational Readiness**: observability commitments, disaster recovery and a capacity plan |
| `tasks.md` | A verification step and a quality gate on every task |

## The Quality stage

The last stage turns everything before it into a plan for proving quality. It
reads the requirements, solution and tasks first, so most of the plan comes from
them. What it asks you for is your organization's **standard**, which the
earlier files can't tell it.

**Collecting** asks:

- which quality characteristics block a release, and which are secondary;
- which compliance or regulatory regimes apply, if any, such as SOC 2, ISO
  27001, GDPR, HIPAA or PCI-DSS;
- your availability and performance targets, offered as concrete choices;
- which test levels are mandatory, such as unit, integration, end-to-end, load,
  security and accessibility;
- whether gate evidence must be kept, and for how long;
- how strict release gates are, and who signs them off.

**Generating** writes `quality.md`, a quality plan based on the ISO/IEC 25010
product quality model:

- **Quality Objectives** (`QO-001` …), each with an owner.
- **Quality Characteristics**: all nine ISO/IEC 25010 characteristics
  (`QC-01` Functional Suitability to `QC-09` Safety). Each has a measurable
  target, how it is measured and how it is verified, or is marked
  **Applicable: No** with a reason. None is left out.
- **Quality Attribute Scenarios** (`QAS-001` …), each with the number that
  decides pass or fail.
- A **Verification & Validation Plan** and a **Traceability Matrix** from each
  requirement to its characteristic, scenario, task and verification.
- **Defect Management**, a **Risk Register** (`RSK-001` …), **Quality Gates &
  Acceptance** with a gate flow diagram, **Metrics & Reporting** and, when a
  regime applies, **Compliance & Audit Evidence**.

**Review** checks that every characteristic is covered, every target is
measurable, every non-functional requirement is traced, and every gate points at
a real milestone and names the evidence that proves it passed.

When you finish the Quality review, the session is complete.

## Tips

- **Answer the compliance questions precisely.** A regime you name becomes
  compliance requirements, constitution obligations and audit evidence in the
  quality plan.
- **Targets need numbers.** "Fast" and "secure" are not targets; the reviewer
  flags them. If you already know a target, such as a response time, say it in
  the Requirements stage and the Quality stage carries it forward.
- **`/goback` works from the Quality stage**, so you can revise an earlier file
  when the quality plan exposes a gap.

## When to pick another workflow

If you don't need audit-grade quality evidence, [MySpec](https://docs.myspec.dev/workflows/myspec/) is
faster and writes the same four core files with less detail.

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