Skill Claude CodeCodex
Full delegation — you own the goal end-to-end, user just wants results. Triggers: "CEO mode", "get it done", "you decide", "handle everything", "I trust you", "take over", "full authority", "just do it", "搞定 X", "幫我處理", "全權處理", "你決定". Not for: research-only (→ survey), participatory planning (→ dev-flow), or parallel…
Skill Claude CodeCodex
Evidence-first debugging for correctness issues. Invoke when diagnosing bugs, crashes, logic errors, data corruption, connectivity problems, intermittent failures (incl. flaky tests with environment divergence), or 'works on my machine' issues. For performance issues (slow / high latency / CPU / memory), use the…
Skill Claude CodeCodex
Start here before writing any code — sizes task (S/L/H/Fix), sets up branch and session rules. Use when: "I'm starting on X", "quick fix for Y", "continuing from yesterday", "hotfix needed", "let's implement X", "skip to coding", "我要開始做 X", "快速修一下", "接續昨天的進度", resuming a feature branch, or any task that touches code.…
Skill Claude CodeCodex
Distill your recurring procedures and corrections from local conversation history into personal custom skills, routed into YOUR own skill dirs — never into autopilot. Boundary: learn records facts/gotchas; distill produces reusable procedures. Use when: "/distill", "what do I keep redoing", "turn my repeated workflow…
Skill Claude CodeCodex
Audit docs against actual code and find drift (wrong / stale / missing claims), report-only. Use when: "do the docs match the code", "check for doc drift", "audit docs vs code", "did this change make docs stale", "doc-sync", "文件跟 code 同步嗎", "查文件有沒有過時", "對照文件與實作", post-merge doc verification, periodic doc accuracy…
Skill Claude CodeCodex
Onboard a new heterogeneous engine into the autopilot lifecycle. Use when: "onboard a new engine", "qualify gpt-X / a new model as a reviewer", "is model Y good enough", "add an implementer engine", "add a planner engine", "add a verifier engine", "evaluate a model as orchestrator", "route a model by role", "new model…
Skill Claude CodeCodex
Write a standardized mid-work handoff doc for session continuation, and resume from one. Triggers: "寫 handoff", "寫 handover", "ctx 太滿", "context 快滿", "clear session 後繼續", "write a handoff", "hand off to the next session", "接手上個 session", "resume from handoff". Not-for: end-of-project closing (→ finish-flow), machine…
Skill Claude CodeCodex
Audit or refresh Autopilot harness capability state. Use when checking whether Codex, Claude Code, agy, Grok, MiniMax, Copilot CLI, or another harness currently supports skills, hooks, agents, status lines, headless dispatch, DI, gating, or runner roles; when platform facts may be stale; or before expanding…
Skill Claude CodeCodex
Terse CEO front-door — Level 3: full autonomy, CEO executes inline on this thread, escalate only at the DOA boundary. Use when: "/l3 ", "L3 ", you want the "全權處理 / get it done" behavior as one command without the CEO startup Q&A. Presets involvement=just-results, scope=Hold, project red lines plus -x additions…
Skill Claude CodeCodex
Terse CEO front-door — Level 4: dispatch ONE background, worktree-isolated sub-orchestrator "foreman" that runs dev-flow unattended and returns a verdict; CEO context stays clean and the authoritative qc verdict is held at depth 0. Use when: "/l4 ", "L4 ", you want a long autonomous run offloaded off the main thread.…
Skill Claude CodeCodex
Terse CEO front-door — Level 5: like /l4 (background worktree-isolated foreman, depth-0 control loop + authoritative qc) but the IMPLEMENTER is orchestrated by the engine CLI and dispatched through the canonical engine implement-review path. Use when: "/l5 ", "L5 ", you want cost-arbitrage or a decorrelated second…
Skill Claude CodeCodex
Terse CEO front-door — Level 6: like /l5 (worktree-isolated hetero implementer + authoritative qc) but the VERIFICATION AUTHORING is also leaf-dispatched to a heterogeneous engine; depth-0 remains pure orchestration. Use when: "/l6 ", "L6 ", "全委", "全部派遣", "省 token 全外包", "delegate everything incl verification". Presets…
Skill Claude CodeCodex
Recommend what to work on next by scanning all projects, plans, backlog, and proposals. Use when: "/next", "what should I work on", "what's the highest priority", "what to pick up now", "I have N hours — what fits?", "下一步做什麼", "最高優先是什麼", "現在該做什麼", or right after archiving a completed project. Not for: creating plans…
Skill Claude CodeCodex
Scaffold a consuming project's autopilot config (.claude/-config.md DI) from its detected reality — the bridge from "fresh repo" to "autopilot-calibrated repo". Use when: "onboard this repo to autopilot", "set up the .claude config", "scaffold autopilot for this project", "calibrate autopilot to this codebase"…
Skill Claude CodeCodex
Evidence-first performance profiling — tool selection, methodology, interpretation. Use BEFORE guessing at performance issues. Tools first, logs second, code last. Covers: slow queries, high latency, CPU spikes, memory growth, throughput regressions (including 'got slower after deploy' — measure before assuming the…
Skill Claude CodeCodex
Bootstrap, organize, or archive project tracking docs. Use when: "archive this project", "bootstrap from plan", "set up project tracking", "clean up project docs", "update INDEX", "reorganize docs/projects/", "歸檔這個專案", "建專案", "整理專案文件", project is done and merged — needs cleanup. Not for: authoring a plan doc (→…
Skill Claude CodeCodex
Pinned participatory pipeline — research industry best-practice → write a plan → bounded, rubric-frozen plan review (maximum two generations) → expand into a tracked project → execute per dev-flow. Each phase ends at a human approval gate. Use when: "research best practice on X then build it properly", "查業界 best…
Skill Claude CodeCodex
Engineering retrospective from git history — velocity, test ratio, focus score, commit patterns. Use when: "/retro", "retro on last N days", "how productive was this sprint", "analyze my commit history", "work patterns", "session analysis", "回顧", "分析工作模式", "這週做了什麼". Note: "session analysis" here means commit-window…
Skill Claude CodeCodex
Research what the industry does — dual-agent (researcher + skeptic) tech investigation. Use when: "research X", "survey", "investigate options/tradeoffs", "what do others use", "industry standard for X", "compare X vs Y vs Z", "I'm not sure which to pick", "業界怎麼做", "調研一下", "別人怎麼處理的". Not for: strategic priority…
Skill Claude CodeCodex
Team allocation and dependency-aware parallelization — decide when to use teams, select roles, dispatch parallel work safely. Invoke for L-size tasks to evaluate whether team dispatch reduces wall-clock time.
Skill Claude CodeCodex
Testing strategy and baseline management — test pyramid placement, baseline守則, failure investigation funnel, regression scoping, flaky-test systemic handling. Invoke when validating changes or designing test approach. Not for: TDD red-green-refactor coding cycle (→ superpowers:test-driven-development if installed…
Skill Claude CodeCodex
Hegelian dialectic (Thesis → Antithesis → Synthesis) for irreversible or high-stakes decisions with genuine stalemate — NOT a "better think-tank", a different tool for a different situation. Use when: "this decision is hard to reverse", "both sides have real merit", "genuinely torn between X and Y", "irreversible…
Skill Claude CodeCodex
Multi-role debate (architect, ops, QA, product, UX, finance) for strategic decisions. Use when: "I want perspectives from different roles", "let's debate this", "tradeoff analysis", "which should we prioritize", "blast radius of X", "scope decision", "hear from architect/ops/product", "what's the impact?", "要辯論一下"…