brief

Topics in the source

• /c-level-agents:brief — One-Page Strategy Brief
• Pipeline Position
• Inputs
• Output
• Workflow
• Why This Step Exists
• Routing
• Related

Command: /c-level-agents:brief or /c-level-agents:brief Turns intake (raw question or office-hours output) into a one-page strategy brief that the boardroom can deliberate on. This is Step 1 of the strategic sprint pipeline. A topic string, or An office-hours brief (preferred — more rigor) /.claude/company-context.md (loaded automatically) A single Markdown file under /.claude/briefs/YYYY-MM-DD- .md with this structure: 1. Load company-context.md via context-engine 2. If input is office-hours output, parse the 6 answers 3. If input is a raw topic, prompt the founder for the missing pieces 4. Draft 2-3 options (never just one — every brief needs a counterfactual) 5. Make assumptions and constraints explicit 6. Identify affected roles → drives panel composition for /c-level-agents:boardroom 7. Write success + kill criteria BEFORE the decision (this is the rigor moment) 8. Save to /.claude/briefs/ The biggest decision-making failure is debating implementation before agreeing on the question. The brief locks the question, options, and success criteria so the boardroom can deliberate without scope creep. This is also the artifact handoff — the next command consumes this file, not your m

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