メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | style-ops |
| description | 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. |
Operate the Fakoli Style principles ledger. The canonical source of truth is
data/principles.json (in this skill dir); fakoli-style.md is a generated projection — edit
the data, never the doc, then regenerate.
Lifecycle rule: a principle cannot reach proven unless its proof field resolves to a real
test file on disk. The validator enforces this and exits non-zero on any violation.
The four operating-model invariants the whole fakoli-claw suite preserves:
Append a new principle to data/principles.json (defaults to aspirational, requires open_work).
Then regenerate + validate.
Advance a principle's status by editing its entry:
asserted: add proof (repo-relative path) + non-empty embodied_in.proven: as asserted, but proof must point to a test file (test_*.py, *_test.py, or under
a tests/ dir). The validator rejects a non-test proof on a proven entry.Run the full ledger validator: schema validity, duplicate IDs, proof-path existence, embodiment-path existence, the proven-requires-test rule, and staleness of the generated doc.
# Preferred (PEP 723 inline deps): requires uv
uv run --script scripts/validate.py
# Fallback if uv is absent: plain python3 (ensure jsonschema is available)
python3 scripts/validate.py
Exits 0 with OK: ledger and generated doc are valid and in sync; exits 1 with FAIL: <reason>.
Read principle statuses.
# Counts by status (no deps beyond jq):
jq '[.principles[].status] | group_by(.) | map({(.[0]): length}) | add' data/principles.json
# Or read the generated table:
cat fakoli-style.md
openclaw skills install <this-dir> --agent main --as style-ops --force (also installed
for fakoli-orchestrator so wave output can be checked against the operating model).generate.py / validate.py scripts use uv's inline-script deps; if uv is not installed,
run them with python3 after installing their deps, or brew install uv.