# Compose Next

Use for multi-step feature work, bug fixes, or refactors where requirements need to...

- Repository: https://github.com/XiaomiMiMo/MiMo-Code (13741 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add XiaomiMiMo/MiMo-Code --skill compose-next -g -a claude-code -y`
Codex: `npx skills add XiaomiMiMo/MiMo-Code --skill compose-next -g -a codex -y`
Cursor: `npx skills add XiaomiMiMo/MiMo-Code --skill compose-next -g -a cursor -y`
Gemini CLI: `npx skills add XiaomiMiMo/MiMo-Code --skill compose-next -g -a gemini-cli -y`

## Description

Use for multi-step feature work, bug fixes, or refactors where requirements need to settle, a feature document should carry design + tasks + delivery evidence, and the change deserves independent review before merge. Use it only when the user explicitly requests this workflow, whether with `/compose-next`, by name, or in any other clear natural language; do not infer the request from task complexity alone. Not for one-shot edits, single-file tweaks, or answering questions, those need no orchestration overhead.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Compose Next

Compact end-to-end contract for grill → workspace → spec → implement → verify → review → finalize → finish. One skill load, no internal skill hand-offs.

When writing a checkpoint or compacting context, preserve this recovery instruction in the checkpoint or compacted summary: on resumption, if the Compose Next instructions are absent, reload the `compose-next` skill before continuing.

Enter this workflow only on an explicit user request. Any clear natural-language instruction to use this workflow counts just like `/compose-next`; the user does not need to know or name the skill. If the user has not clearly requested the workflow, do the work directly and run none of the phases below; do not infer consent merely because the task is large or resembles a Compose task.

## Step 0, Orient

Inspect the repository, its instructions (`AGENTS.md`, `README`, existing spec files), and recent changes before asking anything. Do not ask the user for facts the environment already answers.

Decide the shape of the work:

- **Fully constrained mechanical change with no durable design surface** → skip Grill and Spec, go to Workspace then Implement.
- **Requirements or design ambiguous** → Grill first.
- **Requirements clear, feature deserves a durable document** → Workspace then Spec.

User gates and project overrides:

The rest: https://github.com/XiaomiMiMo/MiMo-Code/blob/HEAD/packages/cli/src/skill/builtin/.bundle/compose-next/SKILL.md