debrief

Organize customer requirements into a Business Requirements Document with use cases.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/codihaus/claude-skills --skill debrief-codihaus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debrief
Source: https://github.com/codihaus/claude-skills/tree/main/.claude/skills/debrief
Command: npx skills add https://github.com/codihaus/claude-skills --skill debrief-codihaus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The debrief skill helps teams consolidate evolving customer requirements into a single, living Business Requirements Document (BRD) and associated plans, ensuring alignment across stakeholders.

Core Features & Use Cases

  • Unified BRD generation for new projects and feature additions
  • Use-case generation and organization under a hierarchical plans/brd structure
  • Change management with a repository of BRD changes and references

Quick Start

Provide the initial project brief and trigger the debrief process to generate BRD structure and starter use cases.

Frequently Asked Questions about debrief

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

FAQPage Schema
How do I organize customer requirements into a unified BRD?

To organize customer requirements into a unified BRD, the debrief process consolidates evolving inputs into a single living document, generating structured use cases, changes, and references to ensure stakeholder alignment. It manages context gathering through detailed planning.

What is the best way to generate use cases from a project brief?

Generating use cases from a project brief involves triggering the debrief process with your initial context, which automatically structures the use-case generation and organizes them under a hierarchical plans and BRD structure for stakeholder alignment.

Can I use this for feature additions and change requests, or only new projects?

You can use this for feature additions and change requests, not just new projects. The process supports phase-driven workflows including market research, use-case generation, and BRD assembly, while maintaining a repository of BRD changes and references.

How does stakeholder alignment work during BRD assembly?

Stakeholder alignment during BRD assembly works by integrating questionnaires and consolidating customer requirements into a single living Business Requirements Document. This guides teams from context gathering to detailed planning across evolving project scopes.

Do I need to provide a complete brief to start the BRD planning process?

You do not need a complete brief to start the BRD planning process. Providing an initial project brief is sufficient to trigger the debrief process, which then generates the BRD structure and starter use cases for further development.