Skip to main content

write-a-meeting-decision

Write a meeting decision with its question, outcome, authority, rationale, conditions, dissent, owner, effective date, and follow-up. Use when a group has made a choice that others must understand and execute.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
write-a-meeting-decision
category
start
description
Write a meeting decision with its question, outcome, authority, rationale, conditions, dissent, owner, effective date, and follow-up. Use when a group has made a choice that others must understand and execute.
# write-a-meeting-decision Record the decision separately from discussion notes. ## When to use - Use after a meeting, review, approval, incident, or governance forum. - Do not describe a proposal or unresolved discussion as an approved decision. ## Procedure 1. State the exact decision question and meeting, date, participants, and decision authority. 2. Write the approved outcome in one unambiguous sentence. 3. Record scope, exclusions, conditions, effective date, expiry or review date, and superseded decision. 4. Summarize the evidence and rationale needed to understand the choice. 5. Record material alternatives, dissent, unresolved risks, and conflicts without attributing private remarks unnecessarily. 6. Assign actions, owners, due dates, communication, and verification. 7. Confirm wording with the authorized decision owner and link the source record. ## Done - A decision record documents question, outcome, authority, scope, rationale, alternatives, risks, owner, dates, and source link - Authority, wording, action, effective-date, supersession, and recipient checks verify the decision is executable
View on GitHub