Decision and Governance Records
Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.
Read conflicting reviews when valid review findings appear to require incompatible changes.
Workflow
- Identify the decision question, scope, affected capabilities, authority, and required decision date.
- Record current evidence, constraints, assumptions, and unresolved questions.
- Compare feasible options using explicit criteria, risks, reversibility, and downstream effects.
- Name the decision owner, consulted parties, and the evidence required for ratification.
- Record status as proposed, ratified, rejected, superseded, or unresolved; never infer status.
- Document consequences, obligations, follow-up actions, review date, and supersession path.
- Link related decisions and explain conflicts or dependency order.
Boundaries
- Do not mark a proposal ratified without evidence from the named owner.
- Do not rewrite history when a decision changes; supersede it with traceability.
- Do not use a governance record as authorization for implementation, publication, or deployment.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Decision question, Status, Context, Options, Evidence, Owner, Consequences, Follow-up, and Review triggers.
Example
Synthetic example; not an observed client result.
Input: Two storage options are documented, but the owner has not selected one.
Output: Status: proposed. Preserve both options and their tradeoffs, name the decision owner, and keep implementation dependent on selection.
1---2name: record-decisions3description: "Writes or reviews a decision record when asked to document options, rationale, ownership, or approval status; separates a proposal from a ratified decision."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/record-decisions7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-operations"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Decision and Governance Records1617Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.1819Read [conflicting reviews](references/conflicting-reviews.md) when valid review findings appear to require incompatible changes.2021## Workflow22231. Identify the decision question, scope, affected capabilities, authority, and required decision date.242. Record current evidence, constraints, assumptions, and unresolved questions.253. Compare feasible options using explicit criteria, risks, reversibility, and downstream effects.264. Name the decision owner, consulted parties, and the evidence required for ratification.275. Record status as proposed, ratified, rejected, superseded, or unresolved; never infer status.286. Document consequences, obligations, follow-up actions, review date, and supersession path.297. Link related decisions and explain conflicts or dependency order.3031## Boundaries3233- Do not mark a proposal ratified without evidence from the named owner.34- Do not rewrite history when a decision changes; supersede it with traceability.35- Do not use a governance record as authorization for implementation, publication, or deployment.3637## Output3839Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.4041Return Decision question, Status, Context, Options, Evidence, Owner, Consequences, Follow-up, and Review triggers.4243## Example4445Synthetic example; not an observed client result.4647Input: Two storage options are documented, but the owner has not selected one.4849Output: Status: proposed. Preserve both options and their tradeoffs, name the decision owner, and keep implementation dependent on selection.