dew-debrief

What problem does it solve?

This skill helps teams conduct a rigorous post-mortem of a completed dew development cycle, turning observations into specific, actionable configuration changes for the next run.

Core Features & Use Cases

• Structured retrospective facilitation: Guides collaborative inquiry across Discover, Design, Demonstrate, Develop, Document, and the Debrief stage to surface what worked and what didn’t.
• Root-cause and hypothesis testing: Pushes beyond surface explanations by identifying likely causes (skill prompts, workflow design, communication, tooling, or problem complexity) and validating them with falsifiable hypotheses.
• Knowledge institutionalization: Prepares and records “lessons learned” directly into the relevant SKILL.md files, so improvements persist into future cycles.
• Optional DAG evidence review: Uses the project dependency graph to quantify completion, backtracks/invalidations, stage alignment, and remaining/pending nodes.

Quick Start

Use the dew-debrief skill after a completed Discover → Design → Demonstrate → Develop → Document cycle to generate a debrief and write confirmed lessons back into the participating skill configurations.