菜单
Dogfood orchestrator for working on the bop repo itself. Use when working on the bop jobcard system — create cards before coding, execute through dispatcher flow, and verify system output.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Almanac reference for dates, holidays, time zones, business days, and astronomical events. Use when checking if a date is a business day, calculating date differences, converting time zones, looking up holidays, or checking for astronomical events like solstices, equinoxes, and moon phases. Also for seasonal calculations, workday schedules, and calendar arithmetic.
Toyota Production System (TPS) and Toyota Way for software engineering — lean thinking, waste elimination, root cause analysis, and continuous improvement. Use when identifying waste (muda/muri/mura), running blameless postmortems, doing 5 Whys, writing A3 problem statements, or connecting lean philosophy to TRIZ contradiction resolution.
Local multilingual translation via Ollama — 119 languages, no API key, no network, no data leaves the machine. Use when translating to/from Japanese, Chinese, Korean, French, Spanish, German, Portuguese, Russian, Arabic, or any other language. Also for localization, i18n text, and roundtrip validation. Qwen3:32b on Apple Silicon — faster and cheaper than cloud APIs.
TRIZ contradiction matrix oracle for software and systems design. Use when improving one quality worsens another — speed vs correctness, isolation vs sharing, autonomy vs control, simplicity vs completeness. Trigger phrases: "tradeoff", "tension between", "can't have both", "worsens when", "at the cost of", "faster but less reliable", "more isolated but harder to share". Not for bugs, merge conflicts, or tool choices. Prerequisite: triz binary must be installed (run `triz doctor` to verify).
Deploy and manage software on Linux/BSD fleet hosts (Pis, NAS, workstations) via Ansible. Use when user mentions deploy, ansible, fleet, hosts, inventory, or deployment.
Use when operating, debugging, or deploying the elixir-gastown Elixir/BEAM fleet — cluster federation, release builds, worker deploys, seccomp fixes, sname/name distribution issues, rate limiter, or any gastown service on Pi workers or coordinator nodes.
| name | bop-team |
| description | Dogfood orchestrator for working on the bop repo itself. Use when working on the bop jobcard system — create cards before coding, execute through dispatcher flow, and verify system output. |
Use when working on the bop repo itself. Before writing code, deal a card. After finishing, verify the system ran it.
Every unit of work on bop becomes a bop card. No exceptions.
| Agent | Binary | Cost | Best for |
|---|---|---|---|
| ollama | ollama | free | fast local, drafts, docs |
| opencode | opencode | $ | code tasks, mid-complexity |
| codex | codex | $ | code tasks, OpenAI models |
| claude | claude | $$ | complex reasoning, architecture |
Check availability:
for a in ollama opencode codex claude; do which $a 2>/dev/null && echo " $a: available"; done
Four shipping templates in .cards/templates/:
| Template | Stages | Use When |
|---|---|---|
| implement | implement → qa | Clear requirements |
| full | spec → plan → implement → qa | Complex/ambiguous |
| cheap | implement (local) | Small fix, local model |
| ideation | ideation → qa | Brainstorming (bop bstorm) |
| qa-only | qa | Code review, audit |
bop factory install # generate + load plists (includes icon watcher)
bop factory status # check if services are running
bop factory start # start dispatcher + merge-gate + icons
bop factory stop # stop all services
bop factory uninstall # unload + remove plists
# 1a. Deal an implement card
bop new implement <id>
# 1b. Or brainstorm first
bop bstorm <topic words>
# 2. Note the card ID and session name printed
# 3. Work inside the zellij session (or your current session)
# 4. Write output to output/result.md
# 5. Verify it ran
make check
./target/debug/bop status
# 6. The card auto-moves to done/ when dispatcher exits 0
# Build in Xcode → Product → Build
# Then register:
LSREG=/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister
$LSREG -f ~/Applications/JobCardHost.app
# Preview a card
qlmanage -p examples/running-feat.jobcard
┌────────────────┬────────────────┐
│ bop status │ spec.md │
│ (board) │ (current card)│
├────────────────┼────────────────┤
│ dispatcher │ agent stdout │
│ log --follow │ │
├────────────────┼────────────────┤
│ merge-gate │ agent stderr │
│ log --follow │ │
├────────────────┴────────────────┤
│ shell (bop commands live here)│
└─────────────────────────────────┘
Use layouts/bop.kdl to launch this layout: zellij --layout layouts/bop.kdl
All adapters in this repo use MIT/Apache-2.0-licensed tools only:
Sessions are named bop-<card-id>. Always resumable:
zellij attach "bop-<id>" 2>/dev/null || zellij -s "bop-<id>"
The zellij_session field in meta.json is the source of truth.
Quick Look renders a live "Attach" button (green) when the field is present and stage is running.
Nested Claude sessions: When dispatching from inside Claude Code, CLAUDECODE=1 blocks spawning. The adapter already runs unset CLAUDECODE, but if launching dispatcher manually use env -u CLAUDECODE bop dispatcher --once.
Stale worktrees: If a card fails, its git worktree persists and blocks re-dispatch. Clean with:
git worktree remove --force .worktrees/job-<card-id>
git branch -D job-<card-id>
Icon\r (macOS): Finder drops Icon\r files in directories with custom icons. The dispatcher and bop status filter by .jobcard extension to ignore these.
Provider cooldowns: When a provider hits rate limits (exit 75), the dispatcher rotates to the next provider in provider_chain. If ALL providers are rate-limited, cards requeue until cooldowns expire (default 300s).
Before marking any bop work complete, verify:
bop status)make check passes