leek/agent-skills / skills/implement-spec
implement-spec
VerifiedBuild a whole spec fast: parallel implementer subagents work the ticket frontier, each in its own worktree, merging onto one integration branch; then one review, one verification pass, and one PR or a stack of PRs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 28.9 KB |
| agents/openai.yaml | config | 228 B |
| references/laravel.md | markdown | 691 B |
| references/leftovers.md | markdown | 846 B |
| references/resume-and-gates.md | markdown | 3.5 KB |
| scripts/screenshots-report.shexecutable | script | 3.5 KB |
| scripts/spec-run-state.shexecutable | script | 5.6 KB |
| scripts/test-screenshots-report.shexecutable | script | 3.4 KB |
| scripts/test-spec-run-state.shexecutable | script | 7.2 KB |
| scripts/test-worktree-idle.shexecutable | script | 2.2 KB |
| scripts/worktree-idle.shexecutable | script | 2.1 KB |
references/leftovers.md
View on GitHub# What is left after cleanup
Read this in [`implement-spec`](../SKILL.md) step 8 when something this run created is left after the merged tickets' cleanup: a refused environment, the environment of an unmerged or released ticket, or the verify setup (the Herd workspace, database or worktree `verify` made for the run, when it made any).
What is left follows step 1's cleanup answer. When it was to remove them, remove each by step 8's ordered cleanup: a worktree that holds uncommitted work beyond agent notes is listed instead, and a branch `git branch -d` refuses stays and is named in the report. Otherwise ask once about them per **What is left** in [Remove a served worktree](../../laravel-herd-worktrees/SKILL.md#remove-a-served-worktree), one option per ticket's retained environment. Keeping a worktree keeps its associated resources.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |