The MiniMax Code team open-sources MCode Stack Agent workflows and Skills
The MiniMax Code team has open-sourced MCode Stack, writing the Agent workflows and Skills the team uses daily into installable SKILL.md files and manifests, which can be integrated as plugins into MiniMax Code and any Agents that support Skills. The repository packages stacks by member, among which stacks/ronny/ is the most complete, containing 15 skills covering sub-Agent decomposition, context and tool budget auditing, long-session handoff, independent review, and hotfix judgment. The companion notes/ column MCode Engineering Notes explains the rationale; the six engineering-* entries are adapted from Google Engineering Practices, with the adapted portions under CC-BY 3.0 and the rest under MIT.
Why read this
AI score 65
The original article breaks down the team's daily Agent workflows into installable Skills and manifests, and provides concrete criteria for sub-Agent decomposition and context budgeting.
Topics
View original postWe just open-sourced MCode Stack: the actual workflows and skills the MiniMax Code team uses every day to build MiniMax Code. https://t.co/vREt7i8m2M
View original
We just open-sourced MCode Stack: the actual workflows and skills the MiniMax Code team uses every day to build MiniMax Code. https://t.co/vREt7i8m2M
Body · AI translation
MiniMax Code @MiniMax_Code team has open-sourced the Agent workflows and Skills they actually use every day!
MCode Stack includes when the team splits sub-agents, how long to wait for long commands, how to keep long sessions from degrading, what tokens to stuff into each round of context, and more; all of this is written as installable SKILL.md / checklists, and can be used as plugins in MiniMax Code and any Agents that support Skills.
Open-source address: https://t.co/tU3L7LxLF1
What's in the repo Packaged into stacks by person (one plugin set per person): · stacks/ronny/: the most complete, 15 skills · stacks/jiachen/: leans toward "breaking out of the Agent loop, turning notes into posts/videos" · notes/: companion column MCode Engineering Notes (articles explain the reasoning, skills are executable) · community/, templates/stack-template/: outsiders welcome to contribute their daily usage · Three kinds of objects: Skill (/skill-name or auto-loaded by description), Checklist (go through items one by one), Workflow (WORKFLOW.md describes how to use it day to day). Ronny's WORKFLOW.md is still marked Coming soon, so go by the skills for now.
Ronny's 15 Skills 1. Planning and splitting: subagent-split-check, engineering-small-prs, engineering-change-descriptions; whether to dispatch a sub-agent; split big changes into reviewable small PRs; write clearly what changed and why 2. Context and tools: tool-budget-audit, context-tax-audit; how much context tools eat; what is injected each round and its impact on prompt cache 3. Long sessions and long commands: long-session-check, handoff-doc, long-command-check; summarize/persist to disk/start a new session; handoff document; ten-point audit for long shell/background tasks 4. Review: independent-review, engineering-code-review, etc.; clean context looking only at diff+requirements+tests; code health review; write/reply to comments 5. Experiments and hotfixes: harness-experiment, trajectory-review, engineering-emergency-changes; change one thing at a time, look at the cases that flip; look at trajectories not just pass/fail; whether a hotfix is truly urgent
The six engineering-* are adapted from Google Engineering Practices, and the adapted parts remain under CC-BY 3.0 (see stacks/ronny/NOTICE.md); the rest are MIT.
Companion viewpoints (Notes 01 as an example) Sub-agents are first and foremost a tool for isolating context, not for spawning clones by "job type/problem type"; default to the main loop + load skills on demand, and only split when context is measured to be the bottleneck; code review gets an independent clean context. The same series also covers too many tools eating context, compaction vs memory, bash foreground blocking vs background, etc. (06-context-tax is marked upcoming).