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.
Primary entry point for the spec-superflow state-machine workflow.
Install Workflow Start
$ npx skills add MageByte-Zero/spec-superflow --skill workflow-start -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MageByte-Zero/spec-superflow workflow-start --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/workflow-start .claude/skills/workflow-start && 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 "workflow-start" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/workflow-start into .claude/skills/workflow-start/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-start", 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/workflow-startType 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 workflow-start -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MageByte-Zero/spec-superflow workflow-start --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/workflow-start .agents/skills/workflow-start && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workflow-start" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/workflow-start into .agents/skills/workflow-start/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-start", 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 workflow-start -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MageByte-Zero/spec-superflow workflow-start --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/workflow-start .cursor/skills/workflow-start && 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 "workflow-start" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/workflow-start into .cursor/skills/workflow-start/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-start", 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/workflow-start--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 workflow-start -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MageByte-Zero/spec-superflow workflow-start --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/workflow-start .gemini/skills/workflow-start && 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 "workflow-start" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/workflow-start into .gemini/skills/workflow-start/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-start", 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 workflow-startInstalls 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 workflow-start -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/workflow-start .github/skills/workflow-start && 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 "workflow-start" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/workflow-start into .github/skills/workflow-start/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-start", 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 workflow-start -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 workflow-start --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/workflow-start .opencode/skills/workflow-start && 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 "workflow-start" agent skill from https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/workflow-start into .opencode/skills/workflow-start/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-start", 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
workflow-start- GitHub stars
- 839
- Used in
- 1 other repo
- Token cost
- ~1.3k tokens
- SKILL.md length
- 660 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Primary entry point for the spec-superflow state-machine workflow.
- Explicitly requests spec-superflow
- SKILL.md covers Bundled runtime, Resume, New request and Legacy changes
- Calls node
- An active change contains .spec-superflow.yaml and the user asks to continue that change
What it does
Workflow Start is an agent skill from MageByte-Zero/spec-superflow. Primary entry point for the spec-superflow state-machine workflow. Invoke only when the user explicitly requests spec-superflow or an active change contains .spec-superflow.yaml and the user asks to continue that change. Generic proposal, specs, design, task, or contract files are not activation signals.
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
- Explicitly requests spec-superflow
- An active change contains .spec-superflow.yaml and the user asks to continue that change
Example prompts
- “/workflow-start”
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
Workflow Start loads about 1.3k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 660 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). 660 words, ~1,311 tokens.
Download SKILL.mdSave it as
.claude/skills/workflow-start/SKILL.md (or your agent's skills folder).- name
- workflow-start
- description
- Primary entry point for the spec-superflow state-machine workflow. Invoke only when the user explicitly requests spec-superflow or an active change contains .spec-superflow.yaml and the user asks to continue that change. Generic proposal, specs, design, task, or contract files are not activation signals.
Workflow Start
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.
Use only for an explicit spec-superflow request or an existing change. Ordinary coding does not require a spec workflow.
Resume
Run SSF resume <change-dir> --json once. It combines state, handoffs, checkpoints and current-plan inspection. Use the returned absolute change.path for all subsequent operations: recovery may redirect a stale source copy into its recorded worktree. Follow next_action; do not repeat all component commands unless diagnosing that result. A blocked continuation is not a retry instruction; resolve its named cause before running it again. Read only the artifacts relevant to the next action.
debugging: diagnose first, even if a plan is stale. Never dispatch an eligible wave during diagnosis.closing: logical completion. If a recorded isolation still has physical finish pending, route to release-archivist for that remaining action, subject to existing merge authorization. Otherwise stop.abandoned: stop.- A ready handoff needs review through
SSF handoff resolve; an active handoff is non-blocking. Stale checkpoints are history, not current evidence. - Missing/stale Full plans block implementation, not investigation. Valid short paths and Tweak do not require plans.
Update checks are optional (SSF runtime check-update), cached and non-blocking. Never make network access a recovery prerequisite.
New request
Infer scope and risks from the request and repository; do not turn CLI fields into a questionnaire. Validate the change name as a single safe relative path segment under changes/ and create only that directory. Reuse authorization already given. Never infer approval from artifact existence.
Offer only two paths, without a mode-selection interview:
- Direct: clear requested change with a bounded proof. In the same turn run
SSF workflow start <dir> --path direct --scope "<requested outcome and bounds>". No planning pack, recommendation receipt or execution plan is needed. Use affected tests or checks;--verificationcan record tdd/new-test/bounded when relevant. Task/file counts are advisory, not hard limits. - Planned: uncertain behavior, architecture or a user-requested plan. Draft proposal.md (scope, acceptance, risks) and tasks.md (ordered tasks and proof) together. Add specs/design only when their information is needed. Check shared interfaces against actual code once. Present one concrete plan for approval, reusing approval already covering it. Then run
SSF workflow start <dir> --path planned --confirm --reason "<existing approval>". The CLI derives the execution plan and enters executing; no contract-builder, handwritten contract, DP-0..DP-4 sequence or execution recommend is required. Native + final is the default; add--mode sddonly for explicit delegation.
Show full SKILL.md (237 more words)Show less
Continue to build-executor without another question. Ordinary debugging stays in executing. Scope changes update the affected planning sections and repeat planned start once with actual reapproval; do not traverse intermediate states. Nonsemantic corrections can use execution resync with a recorded reason, retaining review history.
Completion uses SSF workflow complete <dir> --verification-command "<required check command>". It runs the check once and preserves failures. Planned work also requires its current review and completed tasks; existing delta specs require synchronization. A user can explicitly accept known risks with workflow complete --accept-risk --confirm --reason "<decision and remaining issues>"; this records accepted-risk, never pass, and does not authorize integration.
Legacy changes
Do not convert an active legacy change or discard its receipts automatically. Resume its recorded obligations: Full/legacy Hotfix may still need contract-builder and old approval/review gates; old Quick/Tweak/Lightweight/direct Hotfix use their existing receipts. Read docs/decision-points.md only for the applicable old decision, not for every task. Use SSF runtime asset read docs/state-machine.md only when a legacy transition is unclear. Legacy SSF state init precedes SSF workflow recommend; a nonrecommended choice requires acknowledgment. Legacy Quick/direct Hotfix use workflow accept --verification and persist test_result: pass before closing; use SSF state set <change-dir> dp_0_timestamp now for portable timestamps.
Continue authorized internal work without phase-by-phase handoff questions. For all paths, read only the current task's source and evidence. Progress updates use one short paragraph; ask only for a new material decision, never “continue?” for authorized work.
© 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/workflow-start 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
Workflow Start 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 |
|---|---|---|---|---|---|---|
| Workflow Start 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.
Contract Builder
MageByte-Zero/spec-superflow
Maintain an execution contract only for an existing legacy change that requires one.
Release Archivist
MageByte-Zero/spec-superflow
Close out a spec-superflow change with verification, summary, and archive readiness.
Related
Categories
Questions about Workflow Start
What does Workflow Start do?
Primary entry point for the spec-superflow state-machine workflow. Workflow Start is an agent skill from MageByte-Zero/spec-superflow. Primary entry point for the spec-superflow state-machine workflow.
When should I use Workflow Start?
Workflow Start fits situations like: explicitly requests spec-superflow; an active change contains .spec-superflow.yaml and the user asks to continue that change.
How do I install Workflow Start in Claude Code?
Run `npx skills add MageByte-Zero/spec-superflow --skill workflow-start -a claude-code`. Or copy the skill folder (skills/workflow-start in MageByte-Zero/spec-superflow) into .claude/skills/workflow-start in your project. Claude Code loads it when a task matches its description.
How do I install Workflow Start in Codex?
Run `npx skills add MageByte-Zero/spec-superflow --skill workflow-start -a codex`. Or copy the skill folder (skills/workflow-start in MageByte-Zero/spec-superflow) into .agents/skills/workflow-start in your project. Codex loads it when a task matches its description.
Can I use Workflow Start 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 workflow-start -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-start, .gemini/skills/workflow-start, .github/skills/workflow-start and .opencode/skills/workflow-start in your project.
What does Workflow Start need to run?
Going by SKILL.md and its folder, Workflow Start needs the command-line tools its instructions call (node).
Does Workflow Start 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 Workflow Start 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 Workflow Start use?
Workflow Start 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 Workflow Start use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Workflow Start?
Skills that share tags, products or a category with Workflow Start: 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 Workflow Start?
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.