brain-dump
Optional discovery before /grilling. Unstructured thoughts or a monologue may reveal several independent tracks; preserve them instead of forcing one objective.
Return the brief in chat unless asked to save or publish. Do not implement, create tickets, or commit to opportunities.
1. Absorb
Treat the conversation, notes, attachments, articles, files, and links as one dump. If the user is still talking, acknowledge and wait; otherwise proceed. Read supplied material and repo evidence. Extract external claims, conclusions, constraints, timing, and implications; use /read-the-damn-docs or /research when current primary sources matter.
Separate source/repo facts, user observations, labelled inferences, contradictions, and unknowns. Never ask the user to repeat an answer already present.
2. Reconstruct
Extract actors, pains, outcomes, systems, triggers, constraints, ideas, rejected directions, urgency, and success signals. Name the surface; separate need from solution. Record implied answers in an Answer ledger:
- Settled: explicit or directly supported.
- Tentative: inferred and safe to challenge.
- Unknown: missing and able to change direction.