/cs:decide <memo — Log a decision to two-layer memory
/cs:decide — Log the Decision
/cs:decide <memo> — Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference.
---
name: "decide"
description: "/cs:decide <memo> — Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference. Use when the founder has approved a boardroom memo and the decision must become durable company memory — e.g. right after /cs:boardroom concludes."
---
# /cs:decide — Log the Decision
**Command:** `/cs:decide <memo-path>`
Logs the founder's decision via the `decision-logger` skill. This is the gate where in-session deliberation becomes durable company memory.
## Pipeline Position
```
/cs:office-hours → /cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem
↑ you are here
```
Overview
Logs the founder's decision via the decision-logger skill. This is the gate where in-session deliberation becomes durable company memory.
Manual install (npx, ZIP)
Claude Code
npx skills add alirezarezvani/claude-skills --skill decide -g -a claude-codeClaude Code (manual)
mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \
| tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/c-level-agents/skills/decideWindows (PowerShell)
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/d5c8065e97e78627d95f/decide.zip" -OutFile "$env:TEMP\decide.zip"; Expand-Archive "$env:TEMP\decide.zip" -DestinationPath "$HOME\.claude\skills" -ForceClaude.ai / desktop
Codex, Cursor, other agents
Connects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md3.4 KB
Read the files here
alirezarezvani/
Shared references3SKILL.md reads these from elsewhere in the repo. Not in the ZIP.
- SKILL.mdc-level-advisor/skills/decision-logger/5.5 KB
- cs-chief-of-staff.mdc-level-agents/agents/5.5 KB
- llm-wiki-bridge.mdc-level-agents/references/3.7 KB
SKILL.md
Show the full text105 lines
/cs:decide — Log the Decision
Command: /cs:decide <memo-path>
Logs the founder's decision via the decision-logger skill. This is the gate where in-session deliberation becomes durable company memory.
Pipeline Position
/cs:office-hours → /cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem
↑ you are here
Two-Layer Memory Model
The decision-logger skill maintains two layers:
- Raw transcripts — every boardroom session, every advisor's Phase 2 position, every dissent. Stored under
~/.claude/decisions/raw/. Reference only, never feeds back automatically. - Approved decisions — only the founder-signed memos. Stored under
~/.claude/decisions/approved/. Feeds into future/cs:office-hoursand/cs:founder-modecalls.
This split prevents the system from "remembering" unresolved debates as if they were decisions.
Input
A board memo file (output of /cs:boardroom).
Workflow
- Read the memo path
- Verify it has founder approval (status: APPROVED)
- Extract structured decision record:
- Decision title
- Date decided
- Option chosen
- Success + kill criteria
- Dissent (preserved)
- Review checkpoint date
- Append to
~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md - Update the raw transcript pointer
- If llm-wiki bridge configured, write to vault (
~/company-vault/10-decisions/) - Schedule auto-revisit (90 days)
Output Record Format
# Decision: <title>
**Decided:** YYYY-MM-DD
**By:** <founder name>
**Memo:** <link to boardroom memo>
**Brief:** <link to original brief>
**Review checkpoint:** YYYY-MM-DD (90d default)
## Decision
**Chose:** <option>
**Rejected:** <other options + one-line why>
## Success Criteria (binding)
- <metric, threshold, timeframe>
## Kill Criteria (binding)
- <metric, threshold, action>
## Preserved Dissent
- **<dissenter>:** <unresolved concern>
- (preserved verbatim; dissent never erased)
## Next Action
- `/cs:execute` → 90-day plan due <date>
## Status History
- YYYY-MM-DD: APPROVED
Why Preserved Dissent
The biggest risk in approved decisions is forgetting why someone disagreed. When the kill criteria trigger, the dissent often turns out to have been correct. Preserving it verbatim — not summarized — keeps the company honest at post-mortem time.
Routing
/cs:execute <decision>— build the 90-day plan/cs:freeze <decision> <days>— lock if irreversible- (Auto-scheduled)
/cs:post-mortem <decision>— at 90-day checkpoint
Stale-Decision Audit
cs-chief-of-staff runs a weekly stale audit:
- Decisions > 90 days without revisit → flag for
/cs:post-mortem - Decisions with kill criteria triggered → flag immediately
- Decisions whose company-context.md basis has changed → flag for re-examination
Related
- Skill:
decision-logger - Agent:
cs-chief-of-staff - Bridge:
../../references/llm-wiki-bridge.md
Version: 1.0.0
| 1 | |
| 2 | name "decide" |
| 3 | description "/cs:decide <memo> — Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference. Use when the founder has approved a boardroom memo and the decision must become durable company memory — e.g. right after /cs:boardroom concludes." |
| 4 | |
| 5 | |
| 6 | # /cs:decide — Log the Decision |
| 7 | |
| 8 | **Command:** `/cs:decide <memo-path>` |
| 9 | |
| 10 | Logs the founder's decision via the `decision-logger` skill. This is the gate where in-session deliberation becomes durable company memory. |
| 11 | |
| 12 | ## Pipeline Position |
| 13 | |
| 14 | |
| 15 | /cs:office-hours → /cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem |
| 16 | ↑ you are here |
| 17 | |
| 18 | |
| 19 | ## Two-Layer Memory Model |
| 20 | |
| 21 | The `decision-logger` skill maintains two layers: |
| 22 | |
| 23 | **Raw transcripts** — every boardroom session, every advisor's Phase 2 position, every dissent. Stored under `~/.claude/decisions/raw/`. Reference only, never feeds back automatically. |
| 24 | **Approved decisions** — only the founder-signed memos. Stored under `~/.claude/decisions/approved/`. Feeds into future `/cs:office-hours` and `/cs:founder-mode` calls. |
| 25 | |
| 26 | This split prevents the system from "remembering" unresolved debates as if they were decisions. |
| 27 | |
| 28 | ## Input |
| 29 | |
| 30 | A board memo file (output of `/cs:boardroom`). |
| 31 | |
| 32 | ## Workflow |
| 33 | |
| 34 | Read the memo path |
| 35 | Verify it has founder approval (status: APPROVED) |
| 36 | Extract structured decision record: |
| 37 | Decision title |
| 38 | Date decided |
| 39 | Option chosen |
| 40 | Success + kill criteria |
| 41 | Dissent (preserved) |
| 42 | Review checkpoint date |
| 43 | Append to `~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md` |
| 44 | Update the raw transcript pointer |
| 45 | If llm-wiki bridge configured, write to vault (`~/company-vault/10-decisions/`) |
| 46 | Schedule auto-revisit (90 days) |
| 47 | |
| 48 | ## Output Record Format |
| 49 | |
| 50 | |
| 51 | # Decision: <title> |
| 52 | **Decided:** YYYY-MM-DD |
| 53 | **By:** <founder name> |
| 54 | **Memo:** <link to boardroom memo> |
| 55 | **Brief:** <link to original brief> |
| 56 | **Review checkpoint:** YYYY-MM-DD (90d default) |
| 57 | |
| 58 | ## Decision |
| 59 | **Chose:** <option> |
| 60 | **Rejected:** <other options + one-line why> |
| 61 | |
| 62 | ## Success Criteria (binding) |
| 63 | - <metric, threshold, timeframe> |
| 64 | |
| 65 | ## Kill Criteria (binding) |
| 66 | - <metric, threshold, action> |
| 67 | |
| 68 | ## Preserved Dissent |
| 69 | - **<dissenter>:** <unresolved concern> |
| 70 | - (preserved verbatim; dissent never erased) |
| 71 | |
| 72 | ## Next Action |
| 73 | - `/cs:execute` → 90-day plan due <date> |
| 74 | |
| 75 | ## Status History |
| 76 | - YYYY-MM-DD: APPROVED |
| 77 | |
| 78 | |
| 79 | ## Why Preserved Dissent |
| 80 | |
| 81 | The biggest risk in approved decisions is forgetting why someone disagreed. When the kill criteria trigger, the dissent often turns out to have been correct. Preserving it verbatim — not summarized — keeps the company honest at post-mortem time. |
| 82 | |
| 83 | ## Routing |
| 84 | |
| 85 | `/cs:execute <decision>` — build the 90-day plan |
| 86 | `/cs:freeze <decision> <days>` — lock if irreversible |
| 87 | (Auto-scheduled) `/cs:post-mortem <decision>` — at 90-day checkpoint |
| 88 | |
| 89 | ## Stale-Decision Audit |
| 90 | |
| 91 | `cs-chief-of-staff` runs a weekly stale audit: |
| 92 | Decisions > 90 days without revisit → flag for `/cs:post-mortem` |
| 93 | Decisions with kill criteria triggered → flag immediately |
| 94 | Decisions whose company-context.md basis has changed → flag for re-examination |
| 95 | |
| 96 | ## Related |
| 97 | |
| 98 | Skill: [`decision-logger`] |
| 99 | Agent: [`cs-chief-of-staff`] |
| 100 | Bridge: [`../../references/llm-wiki-bridge.md`] |
| 101 | |
| 102 | |
| 103 | |
| 104 | **Version:** 1.0.0 |
| 105 |
Details
- Updated
- Aug 30, 2026
- License
- MIT
- Stars on the repo
- ★ 26,349
- Checked
- Source
- alirezarezvani/claude-skills ↗
- Creator
- alirezarezvani · 363 listings
Similar skills
See all →
SkillPaste the plan or decision you're about to make and get backPoke Holes In My Plan Before I Commit
Jeffallan/claude-skills · by https://github.com/JeffallanPaste the plan or decision you're about to make and get back its strongest weaknesses, blind spots, and hidden assumptions — plus a tougher version of the plan.★ 11.6k GitHub stars
SkillTurns an answer into a one-page visual HTML explainerAnswer me with HTML: answer a complex question with one HTML page
QingYunA/answer-me-with-html · by QingYunATurns an answer into a one-page visual HTML explainer: the model writes a short Markdown draft and the bundled CLI builds one page. Use it proactively and liberally, without being asked, whenever a page would help the reader more than plain text, even if plain text would also work: any explanation of how something works or how parts relate (flow, request path, architecture, code or folder structure, state machine, lifecycle, history); any comparison, trade-off or decision with pros and cons; any diagnosis, review or investigation, especially with several causes or findings to rank; any answer with a table, a numbered or ranked list, steps, branches or several sections; or when the user says "I don't get it / draw it / explain visually / 讲讲原理 / 没看懂 / 画个图". When in doubt, use it: a page is quick and cheap to make. Also for explainer videos ("make a video", "做个视频") and for changing its settings. Skip only for small talk, a trivial one-line answer, or when the user asks for plain text.★ 3.7k GitHub stars
SkillPrepare and validate research-only clinical decision-supportClinical Decision-Support Research and Evaluation
K-Dense-AI/scientific-agent-skills · by K-Dense-AIPrepare and validate research-only clinical decision-support evaluation, evidence-profile, cohort, survival, biomarker/model, privacy, and governance artifacts. Use for aggregate or synthetic research documentation and traceability—not patient care or live clinical operation.★ 46k GitHub stars
SkillHand in a decision you're stuck onTough Decision Advisor: Every Angle ConsideredK-Dense-AI/scientific-agent-skills · by K-Dense-AIHand in a decision you're stuck on. Get back a clear breakdown of every angle — the trade-offs, the risks, the blind spot, and a recommended path.★ 46k GitHub stars
SkillWrite and maintain Architecture Decision Records following
wshobson/agents · by wshobsonWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.★ 39.9k GitHub stars
SkillRun a pre-mortem risk analysis on a PRD or launch planPre-Mortem: Risk Analysis for Product Launch
phuryn/pm-skills · by phurynRun a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.★ 26.6k GitHub starsMore from alirezarezvani
SkillResume a paused experiment/ar:ar-resume — Resume Experiment
alirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub stars
SkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub stars
SkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub stars
SkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub stars
SkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub stars
Skill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars