decide

Topics in the source

• /c-level-agents:decide — Log the Decision
• Pipeline Position
• Two-Layer Memory Model
• Input
• Workflow
• Output Record Format
• Why Preserved Dissent
• Routing

Command: /c-level-agents:decide Logs the founder's decision via the decision-logger skill. This is the gate where in-session deliberation becomes durable company memory. 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 /c-level-agents:office-hours and /c-level-agents:founder-mode calls. This split prevents the system from "remembering" unresolved debates as if they were decisions. A board memo file (output of /c-level-agents:boardroom). 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/ - .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) The biggest risk in approved decisions i

This is an excerpt. Refer to the complete source and its current requirements.