A doc that drafts itself. Argus writes the spec from research notes; Scout 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).

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

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

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

Plan. Feature flag? Staged rollout? Migration?

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