skills.rest
buchananwill
buchananwillCOMMUNITY
Explore all skills by this author →
GitHub

debrief-protocol

Enforces a mandatory debrief audit before builds for code traceability.

2|Updated Mar 17, 2026
Search Tags:#documentation#audit#compliance#code-quality#traceability#debrief#build-process
One-click install
npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill debrief-protocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debrief-protocol
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/debrief-protocol
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill debrief-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol enforces a mandatory debrief audit before builds to ensure traceable, auditable changes and a verifiable audit trail across commits.

Core Features & Use Cases

  • File location & naming: mandates storing debriefs in Notes/docker-claude/debriefs/ and using a consistent debrief-NNNN-keyword-keyword-keyword.md filename pattern.
  • Timing discipline: requires writing the debrief prior to initiating a build and updating it after failures or changes.
  • Structured content: defines required sections (Task Summary, Changes Made, Design Decisions, Build & Test Results, Open Questions / Risks, Suggested Follow-ups) for comprehensive accountability.

Quick Start

Create the first debrief file under Notes/docker-claude/debriefs/ using the debrief-NNNN-keyword-keyword-keyword.md format before requesting a build.

Frequently Asked Questions about debrief-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a mandatory code audit before builds for compliance traceability?▼

You enforce a pre-build audit by mandating a structured debrief document with defined sections like Task Summary and Changes Made, ensuring changes are reviewed and verified before initiating any build process.

What sections are required in a pre-build debrief for change auditing?▼

Required debrief sections for change auditing include Task Summary, Changes Made, Design Decisions, Build & Test Results, Open Questions or Risks, and Suggested Follow-ups to ensure comprehensive accountability across commits.

How do I structure debrief filenames for consistent build verification?▼

Structure debrief filenames for build verification using the debrief-NNNN-keyword-keyword-keyword.md pattern, storing them in a mandated directory like Notes/docker-claude/debriefs/ to maintain a verifiable audit trail.

When do I need to update a build audit debrief during development?▼

You need to update a build audit debrief prior to initiating a build and after any failures or changes, ensuring the document accurately reflects the current state of commits for compliance reviews.

Does a pre-build debrief protocol work without external dependencies?▼

Yes, a pre-build debrief protocol works without external dependencies, imposing file location and naming schemes directly within your software development pipeline to enforce timing discipline and structured content.

Related Skills

Explore More Software Engineering Skills→
withzombieswithzombies
80

skills-auto-activation

Automate skill activation in Claude prompts via a configurable hook pipeline.

Community
Advanced
idealic-aiidealic-ai

review

Audit debriefs, logs, and templates against defined standards.

Official
Advanced
danieldev24danieldev24

ci-cd-and-automation

Automates CI/CD pipeline setup and quality gates for code verification.

Community
Advanced
NVIDIANVIDIA
2.8k

code-style

Enforces Python code style and quality standards for Megatron Bridge via Ruff and pre-commit hooks.

Official
Intermediate