---
title: "Product spec"
excerpt: "A doc that drafts itself. Argus writes the spec from research notes; Scout reads existing code and threads the dependencies in."
category: "Template"
---

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