guild-decisions

Capture uncertainty and decision rationale into ADR-lite wiki pages.

6|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/lookatitude/guild --skill guild-decisions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guild-decisions
Source: https://github.com/lookatitude/guild/tree/main/skills/meta/decisions
Command: npx skills add https://github.com/lookatitude/guild --skill guild-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specialists frequently reach uncertain questions during work, and the rationale for choices lives only in memory or run transcripts; this skill formalizes those moments into ADR-lite decision pages under .guild/wiki/decisions, creating a discoverable, auditable history.

Core Features & Use Cases

  • Turns uncertainty into structured decisions stored as ADR-lite pages under .guild/wiki/decisions/.
  • Automatically updates the wiki index and a chronological log to keep decisions navigable and traceable.
  • Enforces an escalation workflow (ask, rate significance, persist only for medium/high) to control decision noise.

Quick Start

Invoke guild:decisions when you encounter a meaningful uncertainty and provide the fields question, why-it-matters, and options.

Frequently Asked Questions about guild-decisions

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

FAQPage Schema
How do I document architecture decisions and rationale in a wiki?

Document architecture decisions by encoding them as ADR-lite wiki pages. This captures the context, options considered, decision, and consequences into structured files under a wiki directory for discoverability and auditability.

How do I persist specialist task choices and uncertainty for auditability?

Persist specialist choices by enforcing an escalation workflow that asks, rates significance, and saves only medium or high impact decisions. This controls noise while keeping non-trivial choices traceable in a chronological log.

What frontmatter fields are required for an ADR-lite decision page?

Required frontmatter fields include type, owner, confidence, created_at, updated_at, expires_at, supersedes, date, asker, task, and category. Enforcing this metadata shape ensures decisions are navigable and auditable.

How do I start logging a technical decision during specialist work?

Start logging by invoking the decision skill when encountering meaningful uncertainty and providing the required fields: question, why-it-matters, and options. This triggers the creation of a structured ADR-lite page.

Does this decision documentation approach work for low significance questions?

This approach filters out low significance questions through an enforced escalation workflow. It asks you to rate significance and only persists decisions rated medium or high to control decision noise in the wiki.