fakoli-claw

Choose how to handle a new coding request — native for tiny edits vs a fakoli-claw flow for multi-file, risky, design, or explicit crew/Fakoli work.

Design phase — refine an idea into an approved spec through structured one-question-at-a-time dialogue, propose 2-3 approaches, present the design section by section, write the spec, and hand off to flow:plan. Works headless over any channel.

Execute phase — wave-based crew dispatch on OpenClaw with critic gates and evidence-based verification. Load an intent-driven plan, group tasks into dependency waves, sessions_spawn specialists in parallel per wave (local SGLang tier), run a critic gate after every code wave, then a sentinel evidence gate.

Ship phase — re-run fresh tests, then present exactly four options (merge locally, push+PR, keep as-is, discard) and execute only the explicit choice. Never auto-merge, auto-push, or discard without the typed word discard.

Plan phase — break an approved spec into an intent-driven task list for OpenClaw crew execution. Verify assumptions with a scout sub-agent, map files to owners, write WHAT-not-HOW tasks with acceptance criteria and Depends on, then hand off to flow:execute.

Fast path — skip brainstorm/plan/waves for small tasks under 3 files. Estimate scope, dispatch a single specialist (welder by default), run verification, run a one-cycle critic gate, done. Escalates to flow:execute if scope or fixes exceed the limit.

Verify phase — evidence-based validation. Detect language, run the full check suite, dispatch the sentinel against the plan's acceptance criteria, and produce a pass/fail scorecard where every PASS cites fresh command output from this session.

Manage the Fakoli Style operating-model principles ledger — add principles, advance lifecycle status, validate the ledger, and read the current status report. The canonical source is data/principles.json; docs/fakoli-style.md is a generated projection.