decision-capture_skill

This skill captures decision patine at Gates when KO or challenges, recording rationale and alternatives for future reference.

TypeScript

306

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill wellapp-ai/well --skill decision-capture

SKILL.md7.5 KB

Overview

This skill captures decision "patine" — the concise wisdom behind why decisions were made and alternatives were rejected — at Gates and during notable events. It records who decided, when, the domain, the rationale (if provided), and stores entries in Notion by default, with ADR files created only for high-impact technical decisions. The goal is lightweight, scannable institutional memory that prevents repeat debates and surfaces recurring patterns.

How this skill works

When a human issues a KO, challenges a proposal, or an automatic pattern trigger fires, the skill classifies the decision (Technical, UX, or Process), prompts for a one-sentence rationale where appropriate, and captures metadata (who, when, domain, Gate, related task). Entries are saved to the Decision Patine Notion database. For high-impact technical items the skill generates an ADR file and small code comments for micro decisions as needed.

When to use it

At any Gate when a human provides KO or rejects a proposal
When a reviewer requests changes or PR feedback causes a decision
When an automated debug pattern emerges (repeated error or repeated refinement)
When a significant technical decision has cross-domain impact
When the team corrects an AI assumption or a phase exceeds takt warnings

Best practices

Capture at the moment of friction — decisions are most valuable when fresh
Keep rationale scannable: 1–2 sentences; accept skipped rationale
Classify as Technical, UX, or Process to aid future queries
Only create ADRs for high-impact or cross-domain technical choices
Prefer Notion entries for routine captures and aggregate Kaizen/Hansei during the session

Example use cases

Wireframe rejected at Gate 1: record why the layout was unsuitable and what was tried before
Scope option rejected at Gate 2: note chosen phasing and rejected alternatives for future planning
Recurring error fixed multiple times: capture a Kaizen entry describing the fix pattern and impact
Technical approach rejected at Gate 4 with high impact: create ADR file and link Notion record
AI mis-assumption corrected during review: capture a Hansei entry describing the incorrect assumption

FAQ

No. It prompts for a one-sentence rationale when a human is available, but will record the decision without rationale if declined.

When is an ADR created?

An ADR is created only for high-impact items or technical decisions with cross-domain effects; routine or micro choices stay in Notion or as inline comments.