메뉴
Load FIRST in any sentropic repo — establishes the harness method (branch/scope/test/debug/review/brainstorm/plan) and supersedes superpowers for those acts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when bringing the harness method to a NEW or non-sentropic repo — maps the repo's conventions into a harness profile so the same scope/branch/verify kernel applies anywhere.
Use before any creative/design work (a feature, a package, an evolution) — explores intent and design via the spec-ladder with multi-peer adversarial review BEFORE implementation.
Use on any bug, test failure, or unexpected behaviour BEFORE proposing a fix — runs the generic evidence-first root-cause loop.
Use when you have a spec/decisions and need an executable plan — writes a lot-based BRANCH.md from the template and completes with track for realization state.
Use when completing a feature, a design step, or before merging — runs a ≥2-peer consensus review and reconciles the findings, instead of a single rubber-stamp pass.
Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.
| name | using-harness |
| description | Load FIRST in any sentropic repo — establishes the harness method (branch/scope/test/debug/review/brainstorm/plan) and supersedes superpowers for those acts. |
@sentropic/harness is the native dev-discipline layer for sentropic repos. Its verbs and harness/*
skills are the SINGLE front door for code-work and PR-workflow. This skill is the index — load it
before any other so the supersede directive below is in effect.
When superpowers (or any other discipline pack) is installed, harness/* takes precedence for the
acts it covers. Do NOT invoke the superpowers skill for these — use the harness equivalent:
| Act | Use | NOT |
|---|---|---|
| ideation / spec design | harness/brainstorm | superpowers:brainstorming |
| tests | harness/test | superpowers:test-driven-development |
| debugging | harness/debug | superpowers:systematic-debugging |
| code review | harness/review | superpowers:requesting/receiving-code-review |
| planning | harness/plan | superpowers:writing-plans / executing-plans |
| branch lifecycle | `harness branch init | close` |
| scope / verification | harness verify · `harness check scope | branch` |
| repo onboarding | harness/adopt | — |
The user may opt to keep superpowers per repo (a profile policy) — absent that opt-out, harness wins. superpowers is never a dependency or backend of harness.
harness <verb> [<subject>] [--<option>] — homogeneous with the sibling sentropic CLIs (stp harness …):
VerificationRun): check scope|branch, verify --category,
audit, init.WorkEvent + point to a skill): brainstorm, test, debug, review,
plan, branch init|close, skills install.A recorder verb does NOT do the thinking — it scaffolds + records, and the harness/<verb> skill carries
the reasoning. Run the verb to open the act, then follow its skill.
Process skills (harness/brainstorm, harness/debug) decide HOW to approach the task — invoke them
before implementation skills. "Let's build X" → brainstorm first. "Fix this bug" → debug first.