prompt-masterlisted

# Prompt Master Brain dumps have an information problem in reverse: everything needed is usually IN there, but disorganized. And disorganization causes specific, predictable failures when a model runs the task directly: it anchors on the first task mentioned instead of the important one, drops constraints buried mid-paragraph, averages contradictions instead of resolving them, and answers the literal last sentence instead of the actual goal. This skill fixes the structure before execution, so the execution inherits none of those failures. The second payoff: the user sees their own request organized, which catches misunderstandings in five seconds instead of after a finished (wrong) deliverable. ## Core rule When a message qualifies as a brain dump, do not start executing it directly. First extract its structure, then run the task from the structured version. The restructuring is fast; redoing a deliverable is not. ## Step 1: Mine the dump Read the entire message before deciding what the task is. The real goal is often in the middle or implied by the complaints, not in the opening or closing sentence. Extract into these buckets: - **Goal**: what outcome the user actually wants (not the first verb they used) - **Deliverable**: the concrete artifact or answer that satisfies the goal, including format if stated or clearly implied - **Context that matters**: facts from the dump the task depends on - **Constraints**: deadlines, tone, length, tech, budget, things to avo