> For the complete documentation index, see [llms.txt](https://planetz.gitbook.io/planetz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://planetz.gitbook.io/planetz/the-product-screen-by-screen/spec-studio.md).

# Spec Studio & Intent

> Status: The product · Target version 0.1.x ｜ Verify labels against your build

## What you'll learn

Spec Studio is where your **intent** lives — where you decide what you want, lock it in, and later check whether the implementation actually matched. It's the human-facing front end of the [Intent Ledger](/planetz/core-ideas/intent-ledger.md).

***

## A three-phase flow

Spec Studio walks a spec thread through three phases:

1. **Pin down intent** — capture the **Decided intent**: *what it satisfies*, *why* (background and aim), and what's **out of scope**. You can write it directly, or **auto-generate it from a conversation**.
2. **Lock in the spec** — turn the intent into a spec with requirements and decisions (an ADR-style record). This is what later work is held accountable to.
3. **Check implementation drift** — once tasks run against the spec, the **Trace** view shows which decisions each run referenced and where the implementation **drifted** from what you decided.

## Decided intent, in plain language

Note the phrasing the product uses — *what it satisfies*, *why*, *out of scope*. You're not writing a formal specification language; you're stating, in human terms, what you want and what you don't. That's the **recognition-first** approach: intent is something you can express and confirm without being a senior engineer.

## Decisions and trace

Each decision in a spec records whether it **satisfies** or **deviates** from your intent, and its provenance (Required / Designed / Assumed / Observed). When you review them you can say **It's correct**, **Reverse it**, **Adopt** an observation into a requirement, or **Create fix task**. Validation surfaces gaps like *requirements without an intent link* or *decided intents with no linked requirement*.

> This is the truth-source inversion in practice: the spec and its decisions are the anchor, and each run is checked against them — not the other way around.

## Next

* [Decisions](/planetz/the-product-screen-by-screen/decisions.md) — the focused queue for adjudicating what agents decided.
* [The Intent Ledger](/planetz/core-ideas/intent-ledger.md) — the concept and mechanism behind this screen.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://planetz.gitbook.io/planetz/the-product-screen-by-screen/spec-studio.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.