alirezarezvani/decide
c-level-advisor/c-level-agents/skills/decide/SKILL.md
/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.
$ install --global
skillsauthnpx skillsauth add alirezarezvani/claude-skills decideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 4:11 AM47.4s1 file scanned
SKILL.md
- 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
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
Related Skills
alirezarezvani/weekly-review
development
VerifiedTrustedCommunity
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/meetings
development
VerifiedTrustedCommunity
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/fable-goal
development
VerifiedTrustedCommunity
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/deep-work
development
VerifiedTrustedCommunity
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.
22,702SKILL.mdUpdated Jul 18, 2026