القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
Load FIRST in any sentropic repo — establishes the harness method (branch/scope/test/debug/review/brainstorm/plan) and supersedes superpowers for those acts.
| name | adopt |
| description | 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. |
Native repo-onboarding. The harness engine (parser, C1/C2 checks, verify) is generic; all repo-specific
policy is DATA in a profile. adopt maps a foreign repo onto that SPI so the method runs unchanged.
harness init [--profile sentropic|stub] [--json] prints a profile descriptor. Save it
as harness.profile.json at the repo root and edit it to fit:
forbiddenPathDefaults — globs forbidden unless a BRANCH.md explicitly Allows them.exceptionIdPattern — the grammar of a valid scope-exception id (e.g. ^BR\d+-EX\d+$).conditionalRequiresException — whether a Conditional path needs a matching declared exception.branchMatch — exact or prefix for the C1 branch check.make vs npm/nx), and the environment data-lifecycle (which envs are disposable vs protected).harness audit --staged-files "<changed files>" --branch-md <path> --json diffs the repo
against the active profile and emits a VerificationRun (static) listing drift: forbidden touches,
undeclared (unknown) paths, missing scope declaration.scope-check/verify step to the repo's pre-commit or CI using the profile, so the
method is enforced, not just documented.A second stub profile diverging from sentropic on a checked dimension is the proof-of-genericity:
the same kernel yields different, correct verdicts per profile. Adoption succeeds when a third repo can
declare its OWN profile and the unchanged engine governs it.