← ClaudeAtlas

decidelisted

/cs:decide <memo> — Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference.
timdevai/proteus · ★ 1 · AI & Automation · score 74
Install: claude install-skill timdevai/proteus
# /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: 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) ##