obra/superpowers / skills/subagent-driven-development
subagent-driven-development
VerifiedUse when executing implementation plans with independent tasks in the current session
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.3 KB |
| implementer-prompt.md | markdown | 6.2 KB |
| re-review-prompt.md | markdown | 4.7 KB |
| references/batching.md | markdown | 583 B |
| references/cannot-verify.md | markdown | 513 B |
| references/final-review.md | markdown | 2.5 KB |
| references/fix-loop.md | markdown | 4.2 KB |
| references/handling-reports.md | markdown | 1.0 KB |
| references/preflight.md | markdown | 1.3 KB |
| references/resuming.md | markdown | 614 B |
| scripts/review-packageexecutable | script | 2.4 KB |
| scripts/sdd-repoexecutable | script | 2.3 KB |
| scripts/sdd-workspaceexecutable | script | 4.7 KB |
| scripts/task-briefexecutable | script | 4.7 KB |
| task-reviewer-prompt.md | markdown | 9.0 KB |
references/preflight.md
View on GitHub# The Pre-flight Scan
Part of superpowers:subagent-driven-development. Run it once, before
dispatching Task 1.
Before dispatching Task 1, scan the plan once for conflicts, writing down
what you checked as you check it:
- tasks that contradict each other or the plan's Global Constraints
- anything the plan explicitly mandates that the review rubric treats as a
defect (a test that asserts nothing, verbatim duplication of a logic block)
The scan's output is a table, not a verdict. One row for every pair of tasks
that share a file or an interface: the two tasks, what one produces against
what the other consumes, and what you found. One row for every task: whether
its own text agrees with itself — the tests it specifies against the code it
specifies, the files it creates against the files it later touches. "The scan
is clean" without those rows is not a scan you ran.
Write the table to the ledger. Rule on everything you find before execution
begins — each finding against the plan text that mandates it — and record
each ruling in the ledger. If the scan is clean, proceed without comment.
Rule on each conflict it surfaces — the spec is the binding authority, the
plan is its argument — record the ruling beside its row, and dispatch
Task 1. The review loop remains the net for conflicts that only emerge from
implementation.
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: 470k | Updated | Claude CodeCodex | Unverified | 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 |