Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Maintain an execution contract only for an existing legacy change that requires one.
Install Contract Builder
$ npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MageByte-Zero/spec-superflow contract-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/contract-builder .claude/skills/contract-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "contract-builder" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/contract-builder into .claude/skills/contract-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/contract-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MageByte-Zero/spec-superflow contract-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/contract-builder .agents/skills/contract-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "contract-builder" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/contract-builder into .agents/skills/contract-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MageByte-Zero/spec-superflow contract-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/contract-builder .cursor/skills/contract-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "contract-builder" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/contract-builder into .cursor/skills/contract-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MageByte-Zero/spec-superflow.git --path skills/contract-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MageByte-Zero/spec-superflow contract-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/contract-builder .gemini/skills/contract-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "contract-builder" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/contract-builder into .gemini/skills/contract-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MageByte-Zero/spec-superflow contract-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/contract-builder .github/skills/contract-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "contract-builder" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/contract-builder into .github/skills/contract-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MageByte-Zero/spec-superflow contract-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/contract-builder .opencode/skills/contract-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "contract-builder" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/contract-builder into .opencode/skills/contract-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
contract-builder- GitHub stars
- 839
- Used in
- 1 other repo
- Token cost
- ~1.3k tokens
- SKILL.md length
- 605 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Maintain an execution contract only for an existing legacy change that requires one.
- Works in 4 steps: List every SHALL/MUST from specs/ → Verify each is reflected in Approved… → Flag unmapped requirements in Escalation… → …
- Development work in your project
- SKILL.md covers Bundled runtime, Artifact Language, Artifact Mapping and Cross-Check: Requirement…, plus 7 more sections
- Calls node
What it does
Contract Builder is an agent skill from MageByte-Zero/spec-superflow. Maintain an execution contract only for an existing legacy change that requires one. New direct/planned changes do not invoke this skill when a contract is absent.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: 源码级融合 OpenSpec 规划引擎 + Superpowers 执行纪律的 AI 编程工作流插件。17 平台支持，9 skills，Spec-first，契约驱动。 The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/contract-builder”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- List every SHALL/MUST from specs/
- Verify each is reflected in Approved Behavior, has a test obligation, and appears in at least one batch
- Flag unmapped requirements in Escalation Rules
- Note cross-batch dependencies
What it can do on your machine
Read from SKILL.md and the folder at commit 25d9b0c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Contract Builder loads about 1.3k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 605 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from MageByte-Zero/spec-superflow at commit 25d9b0c, republished under its MIT licence (© MageByte-Zero). 605 words, ~1,286 tokens.
Download SKILL.mdSave it as
.claude/skills/contract-builder/SKILL.md (or your agent's skills folder).- name
- contract-builder
- description
- Maintain an execution contract only for an existing legacy change that requires one. New direct/planned changes do not invoke this skill when a contract is absent.
Contract Builder
Bundled runtime
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.
Artifact Language
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.
Artifact Mapping
| 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 |
Cross-Check: Requirement Coverage
Before finalizing:
- List every SHALL/MUST from
specs/ - Verify each is reflected in Approved Behavior, has a test obligation, and appears in at least one batch
- Flag unmapped requirements in Escalation Rules
- Note cross-batch dependencies
Contract Structure
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.
Approval Model (DP-3)
After drafting: summarize handoff rules, identify ambiguity and flag unmapped requirements. Reuse explicit approval already covering this exact contract; otherwise request it once, together with any still-pending planning decisions and the default Native execution choice. Approval of scope alone does not approve a contract that has not been shown. Never ask the user to approve the same unchanged contract twice. After approval:
SSF state set <change-dir> dp_3_result "approved: <summary>"
SSF state set <change-dir> dp_3_timestamp now
SSF state rebuild <change-dir>Advance the state after approval:
SSF state transition <change-dir> approved-for-buildDP-3 is a hard gate — no implementation without this record.
Show full SKILL.md (204 more words)Show less
Stale Contract Detection
Refresh if: scope changed in proposal, requirements changed in specs, constraints changed in design, batches changed materially in tasks, or the contract no longer matches intent.
Hotfix Mode
Generate a minimal contract only for a legacy Hotfix: Intent Lock (one sentence), Task List (numbered), Approval Gate (DP-3). Skip Scope Fence, Build Rules, Review Gates, Test Evidence. Still requires DP-3 approval. Quick direct execution and direct incident Hotfix do not invoke this skill; they use the signed receipt and finish with test_result: pass instead.
Guardrails
- Do not continue to implementation if ambiguity remains
- Do not approve the contract on the user's behalf
- Do not skip the contract because planning docs look complete
- Flag unmapped requirements; do not silently drop them
Post-Generation
The approved contract is recorded by state rebuild in the DP-3 sequence above, before the guarded transition. This applies to Full and legacy Hotfix. Do not refresh hashes merely to suppress an unapproved content change.
Exception Handling
- Parse failures: Report specific file and section. Suggest re-running
spec-writer. - Missing files: List every missing artifact. Route back to
spec-writer. - User interruption: Re-read all artifacts on resume; check contract staleness via content comparison.
- Validation failure: Flag unmapped requirements in Escalation Rules and approval summary.
© MageByte-Zero, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/contract-builder of MageByte-Zero/spec-superflow.
Open the folder on GitHubat commit 25d9b0c
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in MageByte-Zero/spec-superflow, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Contract Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Contract Builder this skillMageByte-Zero/spec-superflow | 839 | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from MageByte-Zero/spec-superflow
All 9 skills in this repoBug Investigator
MageByte-Zero/spec-superflow
A skill your agent uses when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes.
Need Explorer
MageByte-Zero/spec-superflow
Clarify intent, scope, constraints, and success criteria before artifact creation.
Spec Writer
MageByte-Zero/spec-superflow
Create or refine spec-superflow planning artifacts. An agent skill from MageByte-Zero/spec-superflow.
Build Executor
MageByte-Zero/spec-superflow
Execute an active direct request or approved planned change.
Release Archivist
MageByte-Zero/spec-superflow
Close out a spec-superflow change with verification, summary, and archive readiness.
Workflow Start
MageByte-Zero/spec-superflow
Primary entry point for the spec-superflow state-machine workflow.
Related
Categories
Questions about Contract Builder
What does Contract Builder do?
Maintain an execution contract only for an existing legacy change that requires one. Contract Builder is an agent skill from MageByte-Zero/spec-superflow. Maintain an execution contract only for an existing legacy change that requires one.
When should I use Contract Builder?
Contract Builder fits situations like: development work in your project.
How do I install Contract Builder in Claude Code?
Run `npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a claude-code`. Or copy the skill folder (skills/contract-builder in MageByte-Zero/spec-superflow) into .claude/skills/contract-builder in your project. Claude Code loads it when a task matches its description.
How do I install Contract Builder in Codex?
Run `npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a codex`. Or copy the skill folder (skills/contract-builder in MageByte-Zero/spec-superflow) into .agents/skills/contract-builder in your project. Codex loads it when a task matches its description.
Can I use Contract Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MageByte-Zero/spec-superflow --skill contract-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contract-builder, .gemini/skills/contract-builder, .github/skills/contract-builder and .opencode/skills/contract-builder in your project.
What does Contract Builder need to run?
Going by SKILL.md and its folder, Contract Builder needs the command-line tools its instructions call (node).
Does Contract Builder access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Contract Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Contract Builder use?
Contract Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Contract Builder use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Contract Builder?
Skills that share tags, products or a category with Contract Builder: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Contract Builder?
MageByte-Zero (a GitHub user) maintains it in MageByte-Zero/spec-superflow, which has 839 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 1, 2026.
Source: MageByte-Zero/spec-superflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.