Team Decision Register
A one-row-per-decision register with decider, owner, reversibility, review dates, and actions, plus a weekly overdue and review sweep.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you capture your board meeting decisions. Here's what I'd typically record for each one: - The decision made - The context and rationale - Who's responsible for any follow-up - Deadlines for action items - Any dissent or conditions If you share your notes or the transcript, I can organize these into a clean record. It's good practice to distinguish between discussion points and actual decisions — not everything discussed becomes a decision. Would you like to paste your meeting notes?
Two-layer log. Layer 1 keeps the raw transcript; Layer 2 holds only
approved decisions. Nothing enters Layer 2 without founder sign-off —
that gate is the point.
FROM TODAY'S TRANSCRIPT — 4 decisions, 3 discussions, separated
DECISIONS (pending your approval → Layer 2)
D1 Raise the Series A in Q1, target $8M
Rationale: 15 months runway, metrics hit A bar by Dec
Owner: CEO · Action: engage bankers by Jan 15
D2 Pause the EU expansion until post-raise
Rationale: capital discipline; revisit at board+1
Owner: COO · no action until raise closes
D3 Approve the $200K security budget (Tier 2)
Owner: CTO · Action: SOC 2 kickoff this month
D4 Move to quarterly board cadence from monthly
DISCUSSED, NOT DECIDED (stays in Layer 1 only)
• Pricing increase — explored, no resolution, revisit next board
• A potential exec hire — CEO to bring a proposal, not a decision
• Competitor's raise — context, no action
WHY THE SPLIT MATTERS
The pricing item felt like a decision in the room. It wasn't — no owner,
no approval. Logging it as decided would have someone acting on a
conversation. The gate catches exactly this.
ACTION ITEMS WITH DATES
D1 → bankers engaged by Jan 15 (CEO)
D3 → SOC 2 kickoff by month-end (CTO)
Approve D1–D4 for Layer 2? Anything you approve becomes reviewable later
with /cs:decisions, and the two dated items surface in /cs:review when
they're overdue.About this skill
Teams forget what they agreed, who owns it, and when to look at it again. This skill keeps one simple register that answers all three, in the tool your team already uses.
What it does
- Keeps one row per decision: decider, owner, one-way or two-way door, status, review date, actions
- Pulls candidate decisions out of meeting notes and asks you to approve them before logging
- Separates real decisions from discussion, and flags tabled items and silent reversals
- Runs a weekly sweep: overdue actions, decisions due for review, stale or ownerless rows
- Answers "what did we decide about X?" with the row and date
What you get
A ready-to-use register schema, approved rows for each meeting, and a short weekly sweep with up to three suggested follow-ups.
Best for
Leadership teams, managers, and founders who keep re-deciding things or losing track of action items after meetings.
SKILL.md preview
---
name: decision-logger
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →First VA Hiring and Handoff Kit
Hire your first assistant and hand work off: what to delegate first, a filtered job post, paid trial, safe access, handoff SOPs.
Claude Workspace Admin
Administer a Claude Team or Enterprise workspace: members, roles, connectors, SSO, offboarding. Scoped, verified, logged.
Delegation-Ready SOP for Recurring Tasks
Turns a task that lives in your head into an SOP a new VA or contractor can run solo, with decision rules, a done-check, and a handoff plan.
Company OS Designer
Sets up how your company runs: EOS-style, OKR, or custom, with accountability chart, quarterly priorities, scorecard, meeting cadence.