devrites weekly downloads statistics

<p align="center"> <a href="https://devrites.com"> <img src="images/logo.png" alt="DevRites: AI can write the diff. Make it prove the release. Spec, Clarify, Define, Vet, Build, Prove, Polish, Review, and Seal are checked; Ship waits for a human GO." width="100%"> </a> </p> <p align="center"> <a href="https://www.npmjs.com/package/devrites"><img src="https://img.shields.io/npm/v/devrites?style=flat-square&label=npm&labelColor=191816&color=ab4737" alt="npm version"></a> <a href="#hosts"><img src="https://img.shields.io/badge/hosts-Claude_Code_·_Codex_·_omp_·_pi_·_Devin-2d617e?style=flat-square&labelColor=191816" alt="Supported hosts"></a> <img src="https://img.shields.io/badge/node-%E2%89%A518-504b45?style=flat-square&labelColor=191816" alt="Node.js 18 or later"> <a href="LICENSE"><img src="https://img.shields.io/badge/license-source--available-504b45?style=flat-square&labelColor=191816" alt="Source-available license"></a> </p> <p align="center"> <a href="https://devrites.com"><b>Website</b></a> · <a href="docs/quick-reference.md"><b>Quick reference</b></a> · <a href="docs/command-map.md"><b>Command map</b></a> · <a href="docs/usage.md"><b>Worked examples</b></a> · <a href="CHANGELOG.md"><b>Changelog</b></a> </p> <br>

DevRites is a repository-local workflow for AI coding agents. It turns a feature request into a spec, a sliced plan, working code, recorded proof, a release decision, and an explicit ship step. It runs inside Claude Code, Codex, omp, pi, and Devin CLI.

DevRites keeps that work in .devrites/ inside your repository, where chat history can't lose it. After you clear the conversation, switch hosts, or hand the feature to another engineer, the next session reads the same plan, decisions, and evidence before it continues.

Status: v7.0.2: see CHANGELOG.md for release notes.

This is the latest published release; main may contain unreleased work.

Why DevRites

Without a workflow	With DevRites
The plan lives in a chat window and disappears on /clear.	Spec, plan, decisions, and questions are Markdown files in .devrites/work/<slug>/.
The agent says "tests pass".	Proof must be positive and discriminating, and it is bound to a digest of the exact candidate files.
The agent that wrote the code also reviews it.	Seventeen fresh-context specialist agents plan, review, audit, and prove. Only one of them can write code.
Commits and pushes happen whenever the agent decides.	Seal decides GO or NO-GO. Ship acts only after you type a fresh, literal GO.
Every change gets the same ceremony.	/rite-quick handles a small reversible change. The full lifecycle is for features and risky work.

Quick start

1. Install from the root of your project. Node.js 18 or later is required to install and run DevRites. Development in this repository (npm ci, which .npmrc runs with engine-strict=true) needs Node.js 22.22.2 or later within 22.x, or 24.15 or later; Node 23.x and 24.0 through 24.14 fail with EBADENGINE.

npx devrites@latest

Or paste this to your coding agent:

Install DevRites in this project: run `npx devrites@latest` from the repository
root, then run /rite-doctor ($rite-doctor in Codex) and report any FAIL line
with its fix.

The installer adds project-local support for Claude Code, Codex, omp, pi, and Devin CLI. It does not write skills, agents, or hooks to ~/.claude, ~/.codex, ~/.pi, or ~/.config/devin.

2. Pick the smallest route that still protects the work.

You want to…	Claude Code, omp, pi, Devin	Codex
Make a small, reversible change	/rite-quick fix the CSV header typo	$rite-quick fix the CSV header typo
Build a new feature or risky behavior	/rite-spec add-csv-export	$rite-spec add-csv-export
Resume an active feature	/rite-status	$rite-status
Baseline an existing codebase	/rite-adopt	$rite-adopt
Run the whole lifecycle unattended	/rite-autocomplete	$rite-autocomplete

3. Follow the next recorded step. /rite-status reads the active workspace and reports the phase, open questions, evidence, and the next command.

[!TIP] The shortest path is Spec, Build, Prove. Clarify and Vet still run, but they ask nothing when the contract is already complete.

The lifecycle

<p align="center"> <img src="images/run-order.png" alt="Run order. Shape: 1 /rite-spec, 2 /rite-clarify, optional /rite-temper, 3 /rite-define, 4 /rite-vet. Build: 5 /rite-build, repeated for every slice. Prove: 6 /rite-prove, 7 /rite-polish, 8 /rite-review. Ship: 9 /rite-seal, 10 /rite-ship, then you type GO." width="100%"> </p>

In the default HITL mode, you run each command yourself, in this order. Each one stops when its phase is done and records the next step in the workspace. If you lose track, /rite-status prints the next command.

/rite-spec add-csv-export   #  1  answer its questions; writes spec.md
/rite-clarify               #  2  asks nothing when the spec is complete
/rite-temper                #     optional: big or risky features only
/rite-define                #  3  plan + vertical slices in tasks.md
/rite-vet                   #  4  plan review; nothing builds before READY
/rite-build                 #  5  builds slice 1, then stops
/rite-build                 #  5  builds slice 2; repeat until every slice is done
/rite-prove                 #  6  once, after the last slice
/rite-polish                #  7  cleans code and touched UI
/rite-review                #  8  checks the diff against spec and standards
/rite-seal                  #  9  GO or NO-GO; Git untouched
/rite-ship                  # 10  shows the exact Git plan, then waits for you to type GO
```…