Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →magebyte-zero/contract-builder
Convert approved planning artifacts into an execution contract.
Passed 14 of 20 test cases with the skill, and 5 of 20 without it.
and 16 more in the full report
11 fixed5 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our `.spec-superflow.yaml` file, `dp_0_decisions` lists `artifact_language=auto`. We are ready to draft `execution-contract.md` for our legacy module. Should you default to English and proceed with generating the contract?
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to default to English when artifact_language is auto. | Missed | Passed |
| Routes the workflow back to workflow-start prior to contract writing. | Missed | Passed |
The instructions your model reads when the skill loads.
Before executing a CLI line below, replace its leading SSF with node "<plugin-root>/scripts/spec-superflow.mjs"; <plugin-root> is the absolute directory two levels above this file. Never run SSF literally or call an ssf from PATH.
Legacy compatibility only: new planned changes use proposal.md + tasks.md and SSF workflow start --path planned. Do not generate a contract or request a second approval for them. Read the remaining instructions only for an existing legacy change.
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.
Enter bridging before writing the contract; skip the transition if already there. Honor configured specs/design omissions. Reference requirement IDs and task IDs instead of copying their full text; preserve scope, obligations, tests, and review policy.
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/test cases passed, vs 5 / 20 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.