Produce a spec/PRD from settled conversation and repo evidence. Do not reopen decisions; put material missing decisions in Further Notes rather than assume.

Use tracker/triage vocabulary from docs/agents/. If absent, return chat output and mention optional /work-automation-kit setup.

Process

Explore current code. Use the domain glossary and respect relevant ADRs.
Choose the highest existing public test seam; propose a new one only when needed, minimizing seam count. Use /read-the-damn-docs for current external behavior, /plan-arbiter for plausible competing plans, and /visual-plan only when that extra artifact was requested.
Return the template in chat. Publish/apply ready-for-agent only when requested.
For implementation breakdown, hand the approved spec to /to-tickets.

Problem Statement

User-perspective problem.

to-spec

Process

Problem Statement

Solution