菜单
Mandatory routing/meta skill for the harness-engineering plugin. Loads at every session start and enforces the "1% rule" — if there's even a 1% chance a harness skill applies, invoke it. Routes between 19 skills (13 vendored from superpowers v5.1.0 + 6 harness-original).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when executing implementation plans with independent tasks in the current session
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
| name | harness:using-harness |
| description | Mandatory routing/meta skill for the harness-engineering plugin. Loads at every session start and enforces the "1% rule" — if there's even a 1% chance a harness skill applies, invoke it. Routes between 19 skills (13 vendored from superpowers v5.1.0 + 6 harness-original). |
This skill is loaded at the start of every session to ensure harness-engineering capabilities are properly activated. Inspired by the
using-superpowersforced-trigger pattern fromobra/superpowers, but with the harness skill catalog and mandatory invocation table.
If there is even a 1% chance one of the skills below applies, you must invoke it — you have no discretion.
This meta-skill overrides default system behavior, but user instructions always take precedence:
The 1% rule governs agent discretion, not user overrides. If the user explicitly opts out of a skill, respect that — the user is in control.
| Trigger | Skill |
|---|---|
| Planning a multi-step task before touching code | harness:writing-plans |
| Implementing a feature or fixing a bug | harness:test-driven-development |
| About to claim work is complete | harness:verification-before-completion |
| Any creative/design task (new feature, modify behavior) | harness:brainstorming |
| Executing a written plan task-by-task | harness:executing-plans |
| Executing a plan via fresh subagent per task | harness:subagent-driven-development |
| 2+ independent parallel tasks | harness:dispatching-parallel-agents |
| Need an isolated workspace | harness:using-git-worktrees |
| Any bug, test failure, or unexpected behavior | harness:systematic-debugging |
| Receiving code review feedback | harness:receiving-code-review |
| Asking for code review | harness:requesting-code-review |
| Implementation complete; integrating the work | harness:finishing-a-development-branch |
| Creating or editing a skill | harness:writing-skills |
| Trigger | Skill |
|---|---|
| (this skill itself) | harness:using-harness |
| Task completion / archiving | harness:archive |
| Health check on existing project Harness setup | harness:audit |
| Pre-production deploy planning | harness:canary |
| Garbage collection / drift cleanup | harness:evolve |
| New project initialization | harness:init |
/<skill>, invoke it immediately.harness:brainstorming → must hand off to harness:writing-plans (terminal state for brainstorming).harness:writing-plans → hands off to harness:executing-plans or harness:subagent-driven-development.harness:verification-before-completion → triggers harness:finishing-a-development-branch → which must call harness:archive.