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 |
scripts/sdd-repo
View on GitHub#!/usr/bin/env bash
# Print the top-level directory of the git working tree the SDD scripts use:
# the current directory's, exactly as git itself picks one. A caller that
# means a different working tree says so with the scripts' -C DIR, which
# they apply (cd) before calling this.
#
# The plan file's location never picks the repository. An executor working
# in a linked worktree commonly holds an absolute path to the plan in the
# main checkout (writing-plans leaves the plan uncommitted there), and its
# workspace and commits belong to the worktree it is working in. And a
# caller standing outside any repository, such as the skill's own directory
# in an installed plugin, is in the wrong place: guessing a repository from
# the plan would silently act on whichever checkout the path points into.
#
# Outside any working tree, stop. --with-commit also stops on a repository
# with no commit yet, for callers that need HEAD as a BASE or a review
# range. The message covers both ways to get here: running from the wrong
# directory (where 'git init' would be the wrong fix) and a new project
# that has no repository or commit yet.
#
# Single source of truth for which repository the SDD and executing-plans
# scripts work in, so no two of them can disagree.
#
# Usage: sdd-repo [--with-commit]
set -euo pipefail
with_commit=false
if [ "${1:-}" = "--with-commit" ]; then
with_commit=true
shift
fi
if [ $# -ne 0 ]; then
echo "usage: sdd-repo [--with-commit]" >&2
exit 2
fi
if root=$(git rev-parse --show-toplevel 2>/dev/null); then
if [ "$with_commit" = false ] || git -C "$root" rev-parse --verify --quiet HEAD >/dev/null; then
printf '%s\n' "$root"
exit 0
fi
said=$(git -C "$root" rev-parse --verify HEAD 2>&1 >/dev/null) || true
else
said=$(git rev-parse --show-toplevel 2>&1 >/dev/null) || true
fi
# git's own first line always follows the shared message: where git refuses
# a working tree the caller is inside (dubious ownership, git missing from
# PATH, the cwd inside .git), the shared message alone would be wrong, and
# git's line names the real fix.
echo "SDD scripts must run from inside the git working tree you're executing in, with at least one commit (current directory: $PWD). If this is a new project, run 'git init' and make a first commit, then rerun." >&2
echo "git said: ${said%%$'\n'*}" >&2
exit 2
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 |