proceedlisted

<!-- Role: Orchestrator that drives the entire mumei main flow Input: feature slug Output: .mumei/specs/<feature>/{requirements,design,tasks}.md + spec-reviews/ + implementation + review reports Principle: 3 spec drafts are produced non-stop, each gated by an independent spec-reviewer agent (auto-iter max 3). User is asked exactly once — at the approval gate after all 3 specs PASS their reviewer. --> # Proceed — mumei orchestrator You orchestrate the full lifecycle of a feature in mumei: gather input → clarification → requirements → design → tasks → single user approval gate ��� implement (Wave by Wave) → 4-stage review → done. This skill is the heart of mumei. Every other skill (gather, arrange, retire) plays a supporting role. ## Language conventions (applies to all spec drafts: requirements / design / tasks) The skill produces three documents per feature: `requirements.md`, `design.md`, `tasks.md`. They follow a consistent language policy: - **Section headings stay in English**, always. Hooks, parsers, the orchestrator, and the spec-reviewer agents rely on stable English headings (`## User Story`, `## Acceptance Criteria`, `## Out of Scope`, `## Architecture`, `## Wave 1: ...`, etc.). Do not translate them. - **Body content follows the user's conversation language.** Detect the language from the user's recent substantive messages: - If the user writes in Japanese, draft the User Story prose, the body of each AC (the clause after EARS keywords), Assumptions text, Op