Practical workflows

Use it before one confident AI answer becomes trusted work.

Round Table Workspace fits the review moment: generated code, launch claims, architecture tradeoffs, vague MVPs, and team habits that need a local evidence trail.

Star on GitHub AI feature demo Back to overview 
$ ./rtw ship-check "Should we merge this AI-generated feature?"

Decision: revise
Why: useful direction, but tests and public claims need tightening
Next: add evidence, weaken unsupported wording, rerun checks
ship-check

Pre-merge AI review

Use when generated work looks ready but still needs evidence.

  • missing tests
  • unsupported claims
  • ship / revise / reject
/room

MVP scope review

Use before a vague product idea turns into premature implementation.

  • smallest useful demo
  • riskiest assumption
  • what not to build yet
/debate

Launch claim check

Use before publishing support, release, or social copy.

  • claim boundary
  • fresh evidence
  • follow-up wording
/debate

Architecture tradeoff

Use when a refactor sounds convincing but may create maintenance drag.

  • real second use case
  • rollback path
  • proof before merge

Team review ritual

A lightweight habit: run ./rtw doctor --quick, then run ship-check before trusting generated work. The output stays local-first and gives reviewers something more concrete than a chat transcript.