Overview
Convert a rough request into a spec that is specific enough for architecture and implementation planning.
Start Here
Read ../../references/vara-domain-overview.md first.
Use ../../assets/spec-template.md as the output shape.
Write the result to docs/plans/YYYY-MM-DD-<topic>-spec.md.
Workflow
- Clarify the user goal, scope, and non-goals.
- Identify actors, state changes, messages, replies, and events.
- Record invariants, failure paths, and edge cases that follow from Gear/Vara actor semantics.
- Turn the result into explicit acceptance criteria.
- Stop when the next step is architecture, not coding.
Guardrails
- Treat async messaging as the default execution model.
- Name recovery and retry behavior when the feature crosses actor boundaries.
- Keep the spec implementation-agnostic enough that architecture still has work to do.
- Do not skip invariants or acceptance criteria.