astra-to-speclisted
Install: claude install-skill thientranhung/astragentic
# To spec
Write from what the Align phase settled and the code shows. **Do not reopen the frontier**:
a question that stayed open goes into the spec as an open question, not into a new round.
## 1. Read before writing
- The **PRD** (`docs/prd.md` or the project's own): actor names and journeys `UJ-n` are used
verbatim; a synonym is a defect. Where the PRD has a Glossary, its terms win.
No PRD and the work changes a surface someone looks at → say so in the handback; `astra-ux`
has not run and the spec will name actors nobody agreed on.
- The code the work touches: a spec with no citations was written from memory. Respect ADRs in
the area; use the glossary's vocabulary.
## 2. Seams first, and check them with the owner
Sketch where the behaviour will be tested. Prefer seams that exist; use the highest seam that
still sees the behaviour; the fewer seams across the codebase the better, the ideal number is
one. **Put the seams to the owner before writing**: which ones, why each, what a test at each
one proves. Write only after the answer comes back through the pane that dispatched you.
## 3. Write the spec
Capabilities, not implementation. Every sentence carries load. **No file paths or code
snippets**; exception: a prototype snippet that IS the decision (state machine, schema, type
shape), trimmed to the decision-rich part.
```markdown
## Problem
From the actor's seat: what is wrong or missing today.
## Solution
From the actor's seat: what is true when this ships.