Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/build-executor
Govern implementation from an approved execution contract.
Passed 13 of 19 test cases with the skill, and 2 of 19 without it.
and 18 more in the full report
14 fixed3 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
In `changes/data-pipeline`, we have recorded 3 failed fix attempts via `ssf debug attempt record`, but the bug persists. The user explicitly confirms escalating to abandon the change with reason 'unresolvable memory leak'. What exact CLI command executes DP-5 debug escalation?
| Checked | Without skill | With skill |
|---|---|---|
| Executes ssf debug escalate changes/data-pipeline --decision abandon --reason "unresolvable memory leak" --confirm. | Missed | Passed |
| Refrains from modifying DP-5 state using raw ssf state set. | Passed | Passed |
The instructions your model reads when the skill loads.
Controls the implementation phase. Uses execution-contract.md as the workflow authority.
For Full or legacy Hotfix, read execution-contract.md, tasks.md, relevant specs/, and relevant design.md. Quick, direct incident Hotfix, and Tweak require only their receipt, request boundary, changed files, and verification command.
Check workflow mode and receipt first. Tweak → direct edit mode. Quick or a valid direct incident Hotfix → Direct Quick and Hotfix. Full or legacy Hotfix → standard contract-first discipline.
Branch/worktree preflight before ANY implementation edit (mandatory — do not skip):
ssf isolate <change-dir>
main/master it creates a
git worktree (preferred) or a new branch, and exits non-zero if it cannot and you
have not approved --force.ssf isolate exits non-zero: STOP. Do not edit main/master in place.
Ask the user for explicit approval (and re-run with ssf isolate <change-dir> --force
only after they approve).For Full and legacy Hotfix, the execution contract is the approved handoff artifact, not chat history. Direct Quick and incident Hotfix use their valid direct receipt plus bounded verification instead; they must not create or require a contract.
RED (write test, see it fail) → GREEN (write minimal code, see it pass) → REFACTOR (clean up, suite stays green).
Quick follows the verification strategy persisted in its receipt: tdd, new-test, or bounded (targeted test, syntax/static check, or other stated evidence). A direct Hotfix must still demonstrate that the original symptom is gone.
Red Flags: ignoring the selected verification strategy, reporting a manual check as if it were automated evidence, or silently expanding a bounded Quick change. Full and legacy Hotfix still require RED → GREEN → REFACTOR.
Before selecting or reviewing test evidence, read
skills/build-executor/writing-good-tests.md. Apply its behavior-falsifiability
test cases passed, vs 2 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.