recap-doc

Run /recap-doc with a ScopeReport JSON produced by scripts/detect-scope.js, for example /recap-doc --scope /tmp/scope.json --depth normal. The skill collects git evidence for the changed files and writes a briefing-recap markdown to the temp directory.

recap-doc generates the walkthrough document for the current round of changes. recap-ask answers interactive follow-up questions over an existing recap, while tech-brief produces a stable technical share-out narrative for teammates across a whole feature.

Output is ephemeral by default, written to <tmp>/sd0x-dev-flow-recap/briefing-recap-<date>.md where <tmp> resolves via $TMPDIR, os.tmpdir(), then /tmp. To commit it with feature docs, pass --output with a path that resolves inside the repo root or temp directory.

Depth controls the top-N changed files covered: 5 for brief, 10 for normal, 15 for deep. Brief omits the Anticipated Questions section and caps blind spots at three; deep adds inline code snippets and diff stats in the evidence section.

Writes are rejected when the realpath-resolved target escapes both the repo root and the temp directory, or when security-redact.js detects a high-confidence secret in the output. Choose a path inside the repo or temp directory and remove any secret-shaped strings.

Avoid it for interactive Q&A over an existing recap (use recap-ask), teammate-oriented technical share-outs (use tech-brief), single-function explanations (use codex-explain), or first-principles reasoning over an existing document (use fp-brief).