decision-meeting-format
Run meetings that actually decide — the pre-read-then-decide format, the options-on-the-table rule, the decider named before debate starts, and the recorded-or-it-didn't-happen close. Use when asked run this decision meeting, we discuss forever and never decide, structure the meeting where we pick the vendor/plan/design, or why do our decisions get relitigated. Produces the meeting design: pre-read, the in-room sequence, the decision rule, and the recording that makes it stick.
npx skills add mohitagw15856/pm-claude-skills --skill decision-meeting-format --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Decision Meeting Format Skill Meetings fail to decide for structural reasons, not character ones: the options were never written down (so debate invents them live), the decider was never named (so consensus is assumed and never arrives), and the decision was never recorded (so it gets relitigated by everyone who remembers it differently). The format fixes all three before the room opens: a pre-read with the options steelmanned, the decider and decision rule announced in the invite, a timeboxed sequence that separates clarifying from advocating, and a close where the decision — with its why and its dissent — lands in the log before anyone leaves. ## What This Skill Produces - **The pre-read spec** — the options doc (each steelmanned, with the recommendation) shipped 24h+ ahead - **The in-room sequence** — clarify → advocate → decide, timeboxed, with the facilitator moves per phase - **The decision rule** — who decides and how (decider-decides / consent / vote), announced before debate - **The record** — decision, why, dissent noted, owner and date — logged before adjourning ## Required Inputs Ask for these if not provided: - **The decision and its options** — what's being decided,
- What This Skill Produces
- Required Inputs
- Framework: The Format Rules
- Output Format
- The Pre-Read (ships [date])
- The Sequence ([N] min total)
- The Record (last 5 minutes, on screen)
- Quality Checks
- Anti-Patterns
What does the decision-meeting-format skill do?
Run meetings that actually decide — the pre-read-then-decide format, the options-on-the-table rule, the decider named before debate starts, and the recorded-or-it-didn't-happen close. Use when asked run this decision meeting, we discuss forever and never decide, structure the meeting where we pick the vendor/plan/design, or why do our decisions get relitigated. Produces the meeting design: pre-read, the in-room sequence, the decision rule, and the recording that makes it stick.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill decision-meeting-format --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.