Skip to content

MiniMax-AI/mcode-stack / stacks/ronny/skills/agent-brief

agent-brief

Unverified

Write the brief before handing a non-trivial task to an agent or subagent, covering stakes, your own hypothesis, goal and scope in your words, what "verified" will mean, and whether the agent is thinking with you or for you. Use before starting a MiniMax Code session, spawning a subagent, or delegating a PR, analysis or doc.

Agent Brief

We delegate a lot. What we try not to delegate is knowing what we asked for. If we cannot write the task down in a few plain lines, the idea is not ready, and the agent will fill the gaps with defaults we never chose. Five minutes here saves a review that cannot tell right from plausible.

1. Set the stakes

Decide how much of this skill to run.

  • Cheap to be wrong: a throwaway script, a rename, formatting, a local experiment we will delete. Hand it off and skip the rest.
  • Someone else lives with it: code that ships, a change to the harness, anything touching users, money, permissions or data, a number that goes into a decision. Run every step, and plan to use evidence-first-review after.

When unsure, ask: if this is quietly wrong, who finds out, and when?

2. Write a hypothesis first

One line on what we expect the answer or the fix to be, written before the agent starts. A wrong guess is fine. Its job is to give us something to compare against, so a polished answer does not become the default.

Hypothesis: the flaky compaction.e2e test is a race between the summary write and the next turn, not a model issue.

3. Brief in our own words

  • Goal: the outcome, not the steps.
  • Who uses it: a reviewer, a user, another agent.
  • Out of scope: what it must not touch (public API, lockfile, other packages).
  • Constraints: versions, style, files it may edit, commands it may run.

If we get stuck writing this, we ask the agent to interview us first, or give it what we know and ask what we have not thought of. We do not ask it to write the brief for us.

4. Define "verified" before seeing output

Pick something we can check later, decided now so we cannot bend it to fit whatever comes back:

  • a named test passes, and a new test fails on the old code;
  • a command and its expected output (mcode -p "..." --json returns X);
  • a screenshot or log line from the real app;
  • a number recomputed from the source data.

Give the agent the same means to check itself (test command, fixture, a running dev server), so it loops before we look.

5. Name the mode

Are we asking it to help us think, or to think for us? Both are fine. In the second case, we owe a stricter review, because we will not have the reasoning in our heads.

Card

Paste this at the top of the task:

Stakes: low | high
Hypothesis: ...
Goal / users / out of scope: ...
Done = (tangible check): ...
Mode: think with me | do it for me
When done: show commands run and their output first, then the summary,
then the decisions and assumptions you made.

References

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall