Skip to content

jnMetaCode/superpowers-zh / skills/subagent-driven-development

subagent-driven-development

Verified

当在当前会话中执行包含独立任务的实现计划时使用

FileKindSize
SKILL.mdskill md17.7 KB
implementer-prompt.mdmarkdown6.0 KB
re-review-prompt.mdmarkdown5.0 KB
references/example-workflow.mdmarkdown2.5 KB
references/final-review.mdmarkdown1.6 KB
references/finishing.mdmarkdown868 B
references/fix-loop.mdmarkdown4.3 KB
references/preflight-and-resuming.mdmarkdown3.8 KB
references/report-handling.mdmarkdown1.6 KB
scripts/review-packageexecutablescript2.4 KB
scripts/sdd-repoexecutablescript2.3 KB
scripts/sdd-workspaceexecutablescript4.7 KB
scripts/task-briefexecutablescript4.6 KB
task-reviewer-prompt.mdmarkdown9.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
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: 463kUpdated Claude CodeCodexVerifiedInstall
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: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall