decision-ledgerlisted

# Decision Ledger ## Purpose Record, track, and surface major decisions that materially affect the project. This skill exists to prevent decisions from disappearing into chat history, becoming invisible to downstream execution, or being silently reversed without acknowledgment. It should ensure that: - major decisions are written down when they are made - decisions are retrievable by any agent or stage - visible alternatives and rationale are preserved - reversibility and risk are acknowledged - downstream execution starts with full decision visibility ## When to Use Use this skill when: - a major technical, architectural, product, or scope decision has been made - an agent identifies a decision that should be formally logged before continuing - the orchestrator needs to preserve a decision for downstream reference - QA surfaces a decision that materially affects readiness - handoff requires a clear record of active decisions ## When Not to Use Do not use this skill when: - the decision is trivial and has no meaningful downstream impact - the task is only to inspect or resume context without new decisions - no decision has actually been made — do not log intent or speculation as a decision ## Required Context Minimum required inputs: - decision title: a short, unambiguous name for the decision - decision context: why this decision was needed - decision made: what was decided, stated clearly Helpful optional inputs: - alternatives considered - rationale for the