mreq-apply
mreq-apply
Implement the tasks in one .mreq/ document. The document is the only progress record: its checkboxes say what is done, and ## Handoff says what the next agent needs.
Input: Optional. A document path, or findings to fix from mreq-close.
Language
Write and reply in the language the agent instruction files (AGENTS.md, CLAUDE.md, ...) set. When they set none, use the language the user writes in. A reply that only picks an option (1, Accept the code) or gives a path does not change it. When the user has written no natural language yet (only a command or a path), use the language of the document: the language of its title and ## Goal, not of the template's headings or text. A title such as add 輸入 1,000 時當掉 means Traditional Chinese, though every heading is English. Use that language in every message, from the first line to the report, including the short notes between tool calls. Only fixed labels such as Open: stay as written.
Asking the user
When your agent has a tool that asks the user option questions, ask with it: AskUserQuestion in Claude Code, ask_user_question in Grok, ask_question in Antigravity, request_user_input in Codex. Ask up to 4 independent questions at once, or as many as the tool takes, the recommended option first and labelled "(Recommended)". When a question has more options than the tool takes, ask that question in plain text. When the tool returns an error (Codex allows it only in Plan mode), ask in plain text for the rest of this conversation. Without such a tool, ask in plain text as a numbered list, the recommended option first, and wait for the answer.
Ask with options, so the user picks instead of types:
- Give every question 2 to 4 options. Keep each label short (1 to 5 words) and put the detail in its description. Keep each
headerto 12 characters or fewer. - Never add an "Other" option: these tools add a free-text answer to every question. When an answer may need a value no option holds (a path, a correction), say in the question that the user can type it there.
- Ask for a typed answer only when no option can hold it, such as an error message only the user has seen. When you can guess the answer, offer the guess as an option.
- Never ask the user to type a command that this skill's steps say to run for them.