spec-to-done
Automates the lifecycle from approved specification to merged code.
Install
mkdir -p .claude/skills/spec-to-done && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12635" && unzip -o skill.zip -d .claude/skills/spec-to-done && rm skill.zipInstalls to .claude/skills/spec-to-done
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when a brainstormed spec already exists under docs/superpowers/specs/ and the user asks to autonomously drive it to a merged PR (e.g. 「跑 spec-to-done」「用 spec-to-done 跑 <spec 路徑>」), or when resuming a previously held spec-to-done run.Key capabilities
- →Advance an approved spec to a merged PR.
- →Execute planning, implementation, and evidence phases.
- →Resume a previously held spec-to-done run.
- →Generate browser evidence.
- →Handle phase transitions based on gate rules.
How it works
The skill autonomously progresses an approved spec through defined phases (plan, implement, evidence) to a merged PR, using subagents and gate rules for transitions.
Inputs & outputs
When to use spec-to-done
- →Completing spec-based features
- →Automating PR creation
- →Driving specs to merge
About spec-to-done
Executes defined workflows (planning, implementation, evidence) to take a spec to a completed, merged state.
Use when a brainstormed spec already exists under docs/superpowers/specs/ and the user asks to autonomously drive it to a merged PR (e.g. 「跑 spec-to-done」「用 spec-to-done 跑 <spec 路徑>」), or when resuming a previously held spec-to-done run.
When not to use it
- →When the user has not explicitly invoked spec-to-done.
- →When the task is not an approved spec.
- →When the request is only "實作 spec", "完成需求", or "使用 agents".
Limitations
- →The process requires an already user-approved spec.
- →Consent carve-out / destructive / production-data / credentials / billing / user-account type gates require pausing.
- →Browser evidence is a hard gate for user-facing changes.
How it compares
This skill automates the entire lifecycle from an approved spec to a merged PR with evidence, unlike a manual, multi-step development and review process.
Compared to similar skills
spec-to-done side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| spec-to-done (this skill) | 0 | 3mo | No flags | Advanced |
| github-script | 1 | 4mo | No flags | Intermediate |
| lfg | 0 | 5mo | No flags | Advanced |
| executing-plans | 0 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
github-script
githubnext
Best practices for writing JavaScript code for GitHub Actions using github-script
lfg
nabilban
Full autonomous engineering workflow
executing-plans
liujiarui0918
Use to execute a written plan. Run tasks in batches with human checkpoints.
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
command-development
anthropics
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.