Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/contract-builder
Convert approved planning artifacts into an execution contract.
Passed 6 of 16 test cases with the skill, and 3 of 16 without it.
and 5 more in the full report
6 fixed2 passed either way12 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
The user just approved the contract summary for changes/user-profile. Record DP-3 approval by creating a file dp_3_approval.txt in the change directory containing 'approved'.
| Checked | Without skill | With skill |
|---|---|---|
| Sets dp_3_result using ssf state set with the summary. | Missed | Passed |
| Sets dp_3_timestamp using ssf state set with an ISO UTC timestamp. | Missed | Passed |
The instructions your model reads when the skill loads.
Converts planning artifacts into a single execution handshake: execution-contract.md. Load the baseline with ssf runtime asset read templates/execution-contract.md.
Read before generating: .spec-superflow.yaml (especially dp_0_decisions),
proposal.md, specs/, design.md, tasks.md, then load
docs/artifact-contract.md with ssf runtime asset read docs/artifact-contract.md.
Read artifact_language=<concrete-language> from dp_0_decisions. Generate
execution-contract.md in the same language as that resolved value and the
approved planning artifacts. Preserve required schema keywords and code
identifiers verbatim; language consistency applies to explanatory prose and
headings. If the concrete artifact language is missing or still auto, route
back to workflow-start before writing the contract instead of guessing or
silently defaulting to English.
| Source | Extract |
|---|---|
proposal.md → ## Why + ## What Changes | Intent Lock (problem + scope) |
proposal.md → ## Scope > ### Out of Scope | Scope Fence |
specs/ → each ### Requirement: | Approved Requirements, Scenarios, Test Obligations |
design.md → ## Decisions | Architecture, Interface, Dependency Constraints |
tasks.md → numbered task groups | Execution Batches, Completion Definitions, Review Timing |
Before finalizing:
specs/Must make obvious: approved behavior, out-of-scope, constraints, batches, test obligations, review gates, and conditions that force a rewind to planning. Prefer compression over repeating planning details.
test cases passed, vs 3 / 16 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.