rite-speclisted

# /rite-spec: investigate and write the spec Turn a request into a **fully covered, correctly placed `spec.md`** by investigating the existing system and resolving every material gap found during authoring. `/rite-clarify` audits the full topology before `/rite-define` plans it. **Do not write a plan, tasks, or code here.** Those belong to `/rite-define` and `/rite-build`. > **Use `/rite-quick` for a small change.** A typo, copy edit, config bump, or > one-function fix does not need a full workspace and lifecycle. Run > `/rite-quick <change>`. It returns here if the work touches auth, data, a migration, a > public API, or more than one slice. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) Pull `documentation.md` via `Read` when capturing significant spec decisions (why-not-what, ADR-style notes in `decisions.md`); pull `principles.md` when the project has declared invariants (`.devrites/principles.md`): a new spec must respect them, and a requirement that can only be met by breaking one is a blocking gap. Pull `spec-grammar.md` and `devrites-lib/reference/workspace-artifact-schema.md` when writing acceptance for a behavioral / high-risk requirement (auth, data model, state machine, public API, money, migration): the structured `### Requirement:` / `#### Scenario:` (SHALL · WHEN/THEN) form, lint-checked by `devrites-engine spec-validate`. Simple criteria stay flat `AC-###` bullets; the grammar is opt-in by rigor, never forced. Us