One writes. One reviews. You decide.
A context-aware toolkit for Claude Code. Claude drafts the plan and the code — a fresh-context reviewer reads the plan before it's built and hunts for drift before it's committed. You stay in the conversation; the loop keeps the work honest.
$ curl -fsSL https://coderv.dev/install.sh | bash Plan. Review. Build. Ship.
Two contexts trade the work back and forth until it converges on one verified end-state. Watch the flow move through each stage.
- 01Plan · writer
Claude drafts
The plan is written and piped to the reviewer — before a single line of code.
- 02Review · reviewer
A clean context hunts flaws
A reviewer subagent that never saw the drafting reads the plan for bugs, security, and scope. The writer adjudicates and re-sends until it converges.
- 03Build · writer
Stamp & write
The approved plan is stamped to an immutable spec. Claude writes the code against it.
- 04Ship · reviewer
Drift-hunter gate
At commit, the diff is audited against the spec. Deviations get flagged before they land.
Five commands. One rhythm.
/docify lays the foundation once. Four more drive the plan → review → build → ship loop as you work.
"What should I read first?"
"Write down why, once."
"Docs stay fresh + honest."
"Where did I leave off?"
/session last reads it. Monday-you never asks "what was I doing?"
The cheapest bug to fix is the one you never build.
A context grading its own work drifts — it already believes the code is right. A reviewer that never saw the writing, checking the plan and the diff, catches what a single context misses.
The reviewer reads the plan, not just the diff — the cheapest time to catch a bad design is before it's built.
The diff is audited against an immutable, stamped spec — not anyone's memory of the conversation. What you approved is what ships.
The writer weighs the reviewer's findings — the reviewer advises, never silently blocks. And every finding is surfaced to you, so the final approval is always yours.
No more remembering slash commands.
Claude listens to how you naturally talk and suggests the right tool at the right moment. You stay in the conversation; the tool finds you.
Used once to transform a messy project into a professionally documented one. Every claim cited back to a source file.
Steps in before you code to prevent architectural blindness — reads docs, surfaces prior decisions, runs the plan past the reviewer.
Captures technical trade-offs while the logic is fresh — so nobody re-debates the same choice in six months.
Triggered at the moment of achievement — runs the drift-hunter gate, syncs docs with the new code, drafts a why-focused commit.
Builds a contextual bridge — Monday-you knows exactly where Friday-you left off.
Put two contexts on a project
you care about.
It's markdown. It's idempotent. It's uninstallable in one command. Nothing to lose.
No sign-up. No telemetry. No lock-in. Starring helps us a lot.