Skip to main content

Flow-state playbook

Phase 6 — the phase almost everyone leaves out, and RAPID's flagship differentiator. Flow-state makes building itself faster: remove friction, add polish, and capture what's learned so velocity compounds.

The cadence​

An ongoing loop (with Production, enhance ⇄ harden):

  • Friction removal — the recurring papercuts that slow every change: slow tests, awkward local setup, a confusing module. Fix the process, not just the output.
  • Docs & tests currency — keep them true as the product evolves (docs with build).
  • Memory pruning — remove stale gotchas so context stays sharp (repo context & memory).
  • Runbook additions — every operational lesson becomes a runbook step.

The capital-deposit checklist​

Every loop must deposit capital — this is the mechanism behind compounding velocity, so it's a checklist, not an aspiration:

  • Updated docs for what changed.
  • New/updated tests (regressions from any escaped defect).
  • Any gotcha captured.
  • Any playbook/runbook improvement recorded.

The capital-deposit rate is measured precisely because this is where the compounding comes from. Flow-state isn't polish-as-luxury; because the agent makes it cheap, it's named as a phase and done every loop.