brief-melisted

# /brief-me A single trigger the user types to receive a structured, converged team advisory report. The conversation that established the ask happens before the slash call. The brief is the team's report, not the agent's. The agent assembles the report from team voices, renders it locally from the shipped template, and opens it on the user's screen. There is no server, no upload, and no external posting step — the brief is a single self-contained HTML file opened in the user's browser. ## Trigger The user types `/brief-me`. Nothing else. No flags. No arguments. If the slash call lands without a clear preceding conversation that established what is being decided or researched, ask one clarifying question in chat before doing anything else. ## The user's standing directive (verbatim, codified 2026-05-08) The following is the user's instruction in their own words. It is preserved verbatim because every prior agent who paraphrased it lost the meaning. Read it before assembling any brief and obey every clause. > Somehow agents have thought that I only want three cards in each brief. I have wondered why they are so terribly lacking in detail. they are to be three cards wide (not more, not that many if less are needed) but they do NOT need to be limited to three. I have had nine cards and it was fine. This is about style not about limit. There needs to be GREAT detail in these briefs and they need to be PLAIN speak, no technical jargon. The job of these briefs is three fold,