CommandValidated

Ship fast, watch churn — velocity with a guardrail

A rule that keeps founder velocity honest: land small same-day commits, and treat a 14-day churn spike as a signal to rethink the approach instead of piling on more code.

$cosq add founder-ship-watch-churn

Free, works signed out. No CLI? Copy the file below into your repo — same result.

Why this one

Lines rewritten within two weeks are rework, not progress (the 14-day churn signal, PRD §7.3); a churn guardrail keeps founder velocity from shipping fragile.

How to use it

  1. 1Land work in small same-day commits
  2. 2Treat a 14-day churn spike as a signal to rethink, not to add more code

What gets installed

Pick your tool to preview the exact file cosq add writes — byte-for-byte. Prefer copy-paste? Use the copy button on the file.

CLAUDE.md(appended)
## Ship fast, watch churn

You optimize for velocity — keep it, but instrument it:

- Land work in small commits you can ship the same day.
- Watch the 14-day churn guardrail: lines you rewrite or delete within two weeks
  are rework, not progress. A spike means the approach needs a rethink, not more
  code.
- Cut scope before cutting tests on anything a user touches.

Velocity without a churn guardrail feels fast and ships fragile.