A skill for writing after-action notes when a planned development phase is complete. It records decisions, departures from the plan, lessons learned, and effects on later work.

Use it to document the outcome of a completed plan phase and capture changes or lessons for subsequent phases.

It preserves what happened during a phase while the details are fresh, making future planning more informed.

sdd-debrief — Skill for Claude Code and Codex by danweinerdev

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add danweinerdev/claude-sdd-planner --skill sdd-debrief

Clone the repo

git clone --depth 1 https://github.com/danweinerdev/claude-sdd-planner

Made for: Claude Code, Codex.

Or install sdd-planner, the plugin that ships this one along with the rest of its 34 skills, 8 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/danweinerdev/claude-sdd-planner/sdd-debrief/github.svg)](https://agentmods.dev/skills/danweinerdev/claude-sdd-planner/sdd-debrief)

Your own site

<a href="https://agentmods.dev/skills/danweinerdev/claude-sdd-planner/sdd-debrief"><img src="https://agentmods.dev/badge/skills/danweinerdev/claude-sdd-planner/sdd-debrief/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/danweinerdev/claude-sdd-planner/sdd-debrief"><img src="https://agentmods.dev/badge/skills/danweinerdev/claude-sdd-planner/sdd-debrief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,476 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.01476
Opus 5	$0.00012	$0.00738
Sonnet 5	$0.00005	$0.00295
Haiku 4.5	$0.00002	$0.00148

Measured 4d ago against content hash ecfdf443277e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

sdd-debrief scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

debrief — 86% identical, 17 lines differ

.codex-plugin/skills/sdd-debrief/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

After-Action Phase Notes

Resources

Before opening shared/..., follow symlinks in this loaded file's path, then derive <plugin-root> from <plugin-root>/skills/<name>/SKILL.md; fallback search roots are repository/user .agents/ (including $HOME/.agents/plugins/*/), Codex ${CODEX_HOME:-$HOME/.codex}/plugins/cache/*/*/*/, and runtime-configured skill roots. Accept only a root containing this skill, shared/agent-runtime.md, and the matching plugin manifest; never use the working directory. Then read <plugin-root>/shared/agent-runtime.md and <plugin-root>/shared/path-resolution.md, and resolve every shared/<path> reference in this skill against <plugin-root>.

Resource boundary: Read the plugin, all SKILL.md files, and shared/ resources in place. Never copy or symlink them into the working directory, target repository, or planning root. Only generated SDD outputs may be materialized from bundled resources.

When to Use

When a plan phase has been completed (or substantially completed) and you want to capture what happened: decisions made, deviations from plan, lessons learned, and impact on future phases.

Process

Identify Target
- Scan Plans/ for plans whose README frontmatter status is active and that have in-progress or completed phases (debriefs happen during active work)
- Ask which plan and phase to debrief (or infer from context)
- Read the phase document to understand what was planned
- Read the plan README for overall context
Gather Information
- Review the phase's tasks and subtasks for completion status
- Read every task's ### Completion Evidence — an absent or pending section on a complete task is a legacy evidence gap (shared/completion-evidence.md); report it in the debrief, never treat it as proof
- Read related designs from Designs/ to identify deviations from intended architecture
- Read related specs from Specs/ to assess requirements coverage
- If more than ~3 related documents are involved, delegate the sweep to the researcher prompt (shared/agent-prompts/researcher.md) instead of reading them all yourself
- Ask the user about:
  - Key decisions made during implementation
  - What deviated from the original plan or design
  - Problems encountered and how they were resolved
  - Insights to carry forward

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago Changed · +2 lines ecfdf443277e
8d ago First seen · 86 lines · 24 tokens per session scan A 96f1cf68dd66

Subscribe to this mod's changes

sdd-debrief is a skill published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,476 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning Project Management agentic-coding agentic-workflow ai claude sdd

sdd-debrief

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

After-Action Phase Notes

Resources

When to Use

Process

What this file has done since we first saw it

Other skills, from other repositories

moai-platform-chrome-extension

moai-framework-electron

moai-foundation-context

moai-domain-uiux

moai-platform-database-cloud

moai-workflow-jit-docs