CLI

Core verbs are invoked bare (rcf init); every other verb carries its group (rcf define validate, rcf audit view). Most of these are run by your agent; the ones a human genuinely reaches for are the core set and the audit group.

• core: init, doctor, guidance, mcp, help, plus the --version flag. Bootstrap the project and its harness wiring; print help.
• discover: intake, preflight, req-classify, req-baseline, ui-classify, ui-baseline. Learn what is already true for this project: classify supplied artefacts, elicit third-party dependencies, propose baseline defaults.
• define: create, read, update, delete, link, unlink, validate, design, blueprint, standards. Author the RCF tree: create, edit, link, validate, compose blueprints, register standards.
• build: queue, bundle, mark, finalise, review, fbs, test-suite. Drive the FBS queue and the five-stage build cycle for each item.
• verify: run, report, provision, cleanup, mcp, browser. Run the independent adversarial ship-gate verifier.
• audit: view, coverage, trace, impact. Inspect the tree and its rollups (live HTML view, coverage, trace, impact).

rcf help prints the same grouped surface; rcf help <group> prints one group; and rcf help <group> <verb> is the flag reference for one verb. The single-page form of this surface is the cheatsheet.

Where to read next

• CLI cheatsheet: every command on one page, one line each.
• Exit codes: what 0 to 4 mean, verb by verb.
• MCP surface: the tool-by-tool map of what the same package serves a connected agent.