What problem does it solve? When working on an academic paper with the STAGE toolchain, users face a roster of specialized workflow skills (story, outline, drafting, review, submission) and need a single entry point that dispatches each /stage request to exactly the right one without duplicating workflow logic. ## Core Features & Use Cases - Request Routing: Reads the authoritative routing roster at .agents/commands/stage.md and dispatches an explicitly invoked /stage request to exactly one stage-* workflow skill. - Status Display: With no request argument, shows the current paper status instead of routing. - Bilingual Support: Uses the Chinese roster wording when STAGE_LANG=zh or the conversation is in Chinese, while keeping English skill names and routing decisions. - Confirmation Gating: For roster entries marked with †, requests user confirmation and shows the exact invocation before proceeding. - Use Case: A researcher types /stage outline in their paper repository; the router reads the roster, selects the outline skill, and starts it via the Skill tool without re-implementing its workflow. ## Quick Start Type /stage followed by the writing task you want, such as asking to route my request to the drafting workflow, and the router will select and start the matching STAGE skill.