メニュー
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.
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 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 | plan |
| description | 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. |
Native sentropic planning. Turns an EVOL spec's decisions into an executable, scoped BRANCH.md. Open it
with harness plan "<spec>" [--lots <n>] (records a WorkEvent; harness writes BRANCH.md, then
track branch import indexes it).
Use plan/BRANCH_TEMPLATE.md strictly — checkboxes only, no prose, no ###. First iteration must be
detailed:
Allowed / Forbidden / Conditional paths (default forbidden: Makefile,
docker-compose*.yml, .cursor/rules/**). Exceptions via BRxx-EXn (reason + impact + rollback).git add <files> — never git add .); commit via make commit MSG="type: …".BRANCH.md checkboxes WITHIN each commit.PLAN.md (waves ≤4 orthogonal branches).harness OWNS the BRANCH.md (the master plan artifact) and EMITS WorkEvents; track ingests them and
owns the realization state — Items, links, Decisions, acceptance, and the AWAITED / DROPPED / DONE / TO-DO
projections. Don't duplicate status in BRANCH.md prose — let track project it. Execute lots in order
autonomously; only interrupt for a real fork or blocker.