Agent skill · alirezarezvani
decide
/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.
What it needs
About 2k tokens when loaded.
What this skill does
/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 Two-Layer Memory Model The decision-logger skill maintains two layers: 1. Raw transcripts — every boardroom session, every advisor's Phase 2 position, every dissent. Stored under ~/.claude/decisions/raw/. Reference only, never feeds back automatically. 2. Approved decisions — only the founder-signed memos. Stored under ~/.claude/decisions/approved/. Feeds into future /cs:office-hours and /cs:founder-mode calls. This split prevents the system from "remembering" unresolved debates as if they were decisions. Input A board memo file (output of /cs:boardroom). Workflow 1. Read the memo path 2. Verify it has founder approval (status: APPROVED) 3. Extract structured decision record: Decision title Date decided Option chosen Success + kill criteria Dissent (preserved) Review checkpoint date 4. Append to ~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md 5. Update the raw transcript pointer 6. If llm-wiki bridge configured, write to vault (~/company-vault/10-decisions/) 7. Schedule auto-revisit (90 days) Output Record Format 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/decide--d5e20c