Results for “decision-record”

Write a new ADR when a non-trivial or hard-to-reverse decision is made. Use for architecture, workflow, tooling, or policy decisions that should persist in docs/adr.

Logs board meeting decisions with a two-layer memory architecture, separating raw transcripts from approved decisions, and provides commands to review past decisions and overdue action items.

Save the current diagnosis state to disk for cross-session recall, including conclusions, rejected directions, and next steps.

Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer work, or when the user invokes $add. Over-register freely; the developer drops with "drop A", "drop A,C", or "drop all".

Meeting to doc

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.

Selects a minimal, non-redundant set of facts, artifacts, skills, and references for a working decision when context is stale, uncertain, or over budget.

Maintains a PARA-structured knowledge base on disk for persistent project context, decisions, and architecture records across agent sessions.