rite-speclisted

# /rite-spec: investigate and write the spec Investigate and resolve material gaps into a placed, covered `spec.md`. `/rite-clarify` audits topology next. Write no plan, task, or code here. > Use `/rite-quick` for a typo, copy/config edit, or one-function fix. It returns > here for auth, data, migration, public API, or multi-slice work. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull `documentation.md` for significant decisions and `principles.md` for declared invariants; an unavoidable principle violation is blocking. For behavioral/high-risk acceptance, use `spec-grammar.md` plus workspace schema; simple criteria stay flat `AC-###`. Apply [`acceptance-criteria.md`](reference/acceptance-criteria.md) so each is binary and observable. ## Operating rules (DevRites core) - No silent assumptions or guessing; prefer conventions; ask on scope, placement, data, UX, security, migration, or acceptance changes. - **Root authority:** controlling chat asks humans, decides, and writes workspace; evidence work follows [`agents.md`](../devrites-lib/reference/standards/agents.md). - **Author one section at a time:** problem → goal → requirements → acceptance → edges. For contested requirements/boundaries/assumptions, apply [`elicitation.md`](../devrites-lib/reference/standards/elicitation.md) before continuing. ## Workflow 0. Read core; if `.devrites/ACTIVE` exists, require its `state.md`. 0a. **Adoption check.** For a never-adopt