kdd

Capture decisions, hypotheses, and lean-canvas updates during knowledge-work sessions.

1|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/slavochek2/claritypledge --skill kdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kdd
Source: https://github.com/slavochek2/claritypledge/tree/main/.claude/commands/slava/maintain/kdd
Command: npx skills add https://github.com/slavochek2/claritypledge --skill kdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Knowledge work often produces decisions, rationales, and learning that vanish between meetings. This Skill provides a structured way to capture and preserve why decisions were made, what hypotheses guided thinking, and what still needs validation.

Core Features & Use Cases

  • Capture and centralize decisions, trade-offs, and meta-reflections to improve traceability.
  • Open questions and hypotheses are linked to the relevant artifacts (e.g., decisions, lean-canvas) to reduce drift.
  • Guided workflow for post-session reviews, enabling teams to align on next steps and guardrails.

Quick Start

Run /kdd after finishing knowledge-work sessions to summarize decisions and commit updates to the project docs.

Frequently Asked Questions about kdd

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

FAQPage Schema
How do I capture the rationale behind product decisions during knowledge-work sessions?

Capturing the rationale behind product decisions during knowledge-work sessions is automated by logging trade-offs and meta-reflections directly into project docs. This preserves context and ensures structured updates to decisions and lean-canvas documents.

What is the best way to document hypotheses and open questions linked to a lean canvas?

Documenting hypotheses and open questions linked to a lean canvas requires structured metadata capture to reduce drift. Linking these artifacts ensures teams align on what still needs validation across sessions.

How do I preserve knowledge-management context across teams between planning meetings?

Preserving knowledge-management context across teams between planning meetings is achieved through guided post-session reviews. This workflow guardrail summarizes decisions and commits updates to project documents, preventing learning loss.

Can I use workflow guardrails to automate post-session reflections and document updates?

Using workflow guardrails to automate post-session reflections and document updates is the core mechanism. Running a guided review after knowledge-work sessions aligns teams on next steps and commits structured updates to decisions.

Does this knowledge-management workflow require any specific dependencies or components?

This knowledge-management workflow requires no specific dependencies or components to function. It operates independently to capture metadata and structured updates, making it easy to integrate into existing product-management environments.

When do I need to run structured updates to decisions and lean-canvas documents?

Structured updates to decisions and lean-canvas documents are needed after finishing knowledge-work sessions, such as planning meetings and design reviews. This prevents the rationale and learning from vanishing between meetings.