← ClaudeAtlas

rite-autocompletelisted

Run the DevRites lifecycle end-to-end unattended; --ship confirms the final gate. Use when the user says "autocomplete", "one-shot this feature", or "ship it autonomously". Not for a single phase.
ViktorsBaikers/DevRites · ★ 1 · Code & Development · score 63
Install: claude install-skill ViktorsBaikers/DevRites
# /rite-autocomplete: full lifecycle, unattended Runs every DevRites phase in order without pausing for discretionary input. It asks clarifying questions **before** unattended work begins. Safety gates remain active: hard irreversible-risk,<!-- pack-scan-ignore: negated statement: gates are NOT disabled --> blocking / escalating gates, and any NO-GO still pause. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) **Step 0:** Read `.claude/skills/devrites-lib/reference/standards/core.md` and `.claude/skills/devrites-lib/reference/standards/afk-hitl.md` first. ## Operating rules - **Use one initial human window.** Run spec and topology-first clarify; arm AFK only after `Decision coverage: CLEAR`. Later discretionary calls are recorded, not asked ([decision policy](reference/decision-policy.md)). - **Safety gates are not bypassable.** AFK never auto-passes destructive migration / auth-authz change / public-API break / external-contract change; blocking and escalating gates and any open `gate: validating` always pause. `--ship` auto-confirms the **final** type-GO only: nothing else. A change that violates a declared project principle (`.devrites/principles.md`) with no recorded exception pauses too: autocomplete never grants a principle exception on its own (`principles.md`: that's a human decision). Red checks never advance the loop: autocomplete runs the shared bounded debug recovery, then stops as `blocked` if the ob