菜单
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 cross-harness integrations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Run pre-commit or pre-merge quality checks: tests, completeness scan (no stubs/TODOs/mocks), code review. Use when: "quality gate", "quality checks", "run tests before merge", "check for stubs", "scan for completeness", "is this ready to commit?", "pre-merge review", "品質檢查", "準備好可以 commit 了嗎", "跑一下檢查". Not for: writing new tests (→ TDD), debugging CI failures, or receiving external review feedback.
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 <goal>", "L6 <goal>", "全委", "全部派遣", "省 token 全外包", "delegate everything incl verification". Presets involvement=just-results, scope=Hold, project red lines plus -x additions (override --mode / --expand / --solo). Not for: /l5 when you still want to do verification yourself; /l4 all-Claude; /l3 inline.
Closing sequence forcing function — use at the END of any dev-flow workflow (L, H, Fix, S) to guarantee no step in the closing sequence gets silently compressed or skipped. On invocation, creates size-appropriate sub-tasks via TaskCreate so each step is individually trackable. MANDATORY for L-size (invoked at L-5) and H-size (invoked at step 9); optional for Fix/S. Use when: finishing L-size project, closing hotfix, "time to merge", "wrap this up", "跑完收尾", "收掉這個專案", "L-5 開始". Not for: mid-phase work, starting new work (→ dev-flow), authoring a plan doc (→ references/plan-template.md).
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 (→ references/plan-template.md), choosing what to work on (→ next), or running quality gates (→ quality-pipeline).
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", "回顧", "分析工作模式", "這週做了什麼". Not for: viewing specific commit diffs, comparison audits, or debugging test coverage drops.
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 practice 寫成 plan、有限 review 後展開成 project 照 dev-flow 跑", "把這個主題做成正式專案", "spec it out then ship it the rigorous way". Not for: full hands-off autonomy (→ ceo-agent), a quick fix / already-known implementation (→ dev-flow), research with no build (→ survey / deep-research), or a single irreversible decision (→ think-tank-dialectic).
| name | harness-maintenance |
| description | 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 cross-harness integrations. |
Use this skill to keep fast-moving harness facts out of memory and out of engine code.
Run the read-only capability report first:
node bin/autopilot.js harness report --stale-after 14d
For a bounded SessionStart-style warning:
node bin/autopilot.js harness report --stale-after 14d --required-level H3 --format warning
If any target harness is stale, unverified, warning, unavailable, or below the required harness level, do not implement H3+ dispatch, hooks, gating, or orchestration from memory. Run a survey or local spike first.
| Script | Use |
|---|---|
scripts/measure-profile-context.js | Produce content-free source, rule-inventory, or persisted Codex context summaries. A byte estimate is conservative evidence only; it cannot prove an exact-token budget or another host's prompt visibility. |
src/harness/capabilities/*.json.auth_domains; use it to separate driver availability
from native provider subscription quota and third-party provider quota.required_level warnings as blockers for H3+ work.For implementation level and role qualification decisions, read:
skills/engine-onboarding/references/role-and-harness-governance.mdUse that reference before changing scorecard rows, hook behavior, dispatch authority, or engine APIs.