decision-capture

Record decision rationale and context at Gates into Notion entries and ADRs.

341|48|Updated Apr 4, 2025
One-click install
npx skills add https://github.com/WellApp-ai/Well --skill decision-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-capture
Source: https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/decision-capture
Command: npx skills add https://github.com/WellApp-ai/Well --skill decision-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The decision-capture skill records the rationale and context behind decisions made at Gates to preserve institutional knowledge, reduce rework, and support audits when KO, challenges, or pattern-based learnings arise.

Core Features & Use Cases

  • Notion MCP integration: Create a centralized decision record with key metadata (domain, gate, decision, rationale, impact).
  • ADR generation for high-impact decisions: Automatically scaffold and attach ADRs when decisions have cross-domain implications.
  • Kaizen/Hansei captures: Silently capture learning from patterns, corrections, and delays to feed improvements.
  • Phase-based prompting and metadata: Gather rationale, who/when, and context, then store in the appropriate artifact.
  • Searchable lineage: Link decisions to related tasks, PRs, or datasets for traceability.

Quick Start

Trigger the skill during Gates (KO or challenge) or when a pattern worth remembering is observed. The system will prompt you to capture a concise summary, rationale, and context, then store the record in Notion and generate an ADR when applicable.

Frequently Asked Questions about decision-capture

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

FAQPage Schema
How do I record decision rationale in Notion during project Gates?

To record decision rationale in Notion, the skill triggers during Gates 1-5 events to capture context and generate entries via Notion MCP integration. It enforces a structured phase-driven workflow to preserve institutional knowledge.

When do I need to create an ADR for high-impact decisions?

You need to create an ADR when decisions have cross-domain implications during project Gates. The capture workflow automatically scaffolds and attaches ADRs to preserve rationale for high-impact choices.

Does this decision capture workflow support Kaizen and Hansei learning patterns?

Yes, the decision capture workflow supports Kaizen and Hansei by silently capturing learnings from patterns, corrections, and delays. It feeds these observations into structured records to drive continuous improvement.

Can I link decision records to related tasks and pull requests for traceability?

Yes, you can link decision records to related tasks, PRs, or datasets for searchable lineage. The capture skill enforces metadata gathering to maintain institutional knowledge and support audits.

What is the best way to capture debug patterns and prevent knowledge loss?

The best way to capture debug patterns is to trigger the skill when a pattern worth remembering is observed. It gathers concise summaries and rationale, storing them as inline records to prevent knowledge loss.