grill-melisted

# Brainstorm Engine (grill-me) Interview me relentlessly about every aspect of this plan. Walk down each branch of the design tree, resolving dependencies one-by-one. For each question, provide your recommended answer. Ask questions one at a time. If a question can be answered by exploring the codebase, explore the codebase instead of asking. ## Why this skill writes files during the interview If the brainstorm stays only in chat, a session timeout or `/compact` loses everything. Writing incrementally means every resolved question is immediately durable — the PRD builds up as you go, and a session crash loses at most the current question. The finalize step at the end cleans up the working draft into a polished document. ## Setup Before the first question, ensure a task exists: ```bash # Check for active task python3 scripts/codex_harness.py task current # If none exists, create one python3 scripts/codex_harness.py task create "<title from user's request>" python3 scripts/codex_harness.py task start <slug> ``` Note the task slug — you'll use it for every command below. ## The interview loop Each turn of the brainstorm follows this pattern: 1. **Ask one question** with your recommended answer 2. **Wait for the user's answer** (they may accept your recommendation, modify it, or reject it) 3. **Immediately write the decision** — this is the critical step, don't batch these ### What "immediately write" means After the user answers, run these before asking the next qu