メニュー
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.
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.
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.
| name | flow-finish |
| description | 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. |
Ship work only after fresh verification. Present options, wait for an explicit choice, execute it.
Never auto-merge or auto-push. Present the 4 options and wait. Per the OpenClaw safety model, pushing, PR creation, and branch deletion are side-effectful — the user must choose explicitly, and irreversible deletion requires the exact typed word `discard`.
npx tsc --noEmit && bun test; Py ruff check . && mypy . && pytest; Rust
cargo check && cargo test. If tests fail → STOP, show full output, return control.git branch --show-current; prefer main, else master, else ask.Tests pass. What would you like to do with this branch?
1. Merge back to <base> locally
2. Push and create a Pull Request
3. Keep the branch as-is
4. Discard this work
git branch -d; on fail keep branch + report.git push -u origin <branch> then gh pr create with summary from the plan Goal +
test results. Report the PR URL. (Push/PR require this explicit option — see safety model.)git log <base>..HEAD --oneline, require the user to type exactly
discard (reject "yes"/"ok"); then checkout base + git branch -D. Irreversible.git worktree remove if one exists; for PR/Keep, leave it.Merge without fresh tests · push without option 2 · delete without the typed discard ·
force-push unless explicitly requested · proceed with failing tests.