A doc that drafts itself. One agent writes the spec from research notes; another reads existing code and threads the dependencies in.

Product spec: [feature name]

## Problem

Who's affected, what hurts, what evidence makes this real (interviews, support tickets, dashboards).

## Goals

- Goal 1: measurable outcome
- Goal 2: measurable outcome

## Non-goals

What's explicitly out of scope so the next person reading this doesn't expand it.

## Approach

Architectural sketch. Pseudo-code where it helps. Diagrams as ASCII or linked images.

## Open questions

Use the **Open questions** surface to track these. Don't bury them in prose.

## Acceptance criteria

- [ ] Concrete, testable
- [ ] Concrete, testable

## Rollout

Plan. Feature flag? Staged rollout? Migration?

## Risks

What could go wrong, what we'll watch for.

Fork to next cycle

When you're done, fork the workspace for the next cycle. The new workspace will be seeded with your structure, your customizations, and this cycle's retro as your agent's first Status entry — so it picks up context-aware from where this one left off. Same template, next cycle, no manual setup.

Product spec

Product spec: [feature name]

Fork to next cycle

Make this yours. Edit, extend, run agents on it.