harness
Installation
SKILL.md
Harness
Harness makes a repository legible and provable enough for a software factory to change it without rediscovering the system or guessing whether the result is safe. Repository knowledge and validation stay in the repository; task execution, grading, and proof receipts stay with the factory.
Choose a workflow
| Request | Load | Done when |
|---|---|---|
| Prepare or overhaul a repo | ./adopt.md |
The repo has a ratified baseline, concise guidance, an executable proof contract, enforced prerequisites, and a fresh Doctor result. |
| Assess adoption without edits | ./adopt.md with assess |
The report identifies adoption facts, unknowns, blockers, and a remediation plan without changing the repo. |
| Audit readiness or review a diff | ./doctor.md |
The report names observed facts, unknowns, blockers, required proofs, and what actually ran. |
| Protect one behavior before changing it | ./capture.md |
Characterization proof passes against unchanged code and remaining gaps are named. |
Advanced phases are directly addressable when the user names them: