stage

Routes /stage requests to the correct STAGE academic-writing workflow skill.

2|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/wanghao9610/STAGE --skill stage-wanghao9610
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stage
Source: https://github.com/wanghao9610/STAGE/tree/main/.kimi-code/plugins/stage/skills/stage
Command: npx skills add https://github.com/wanghao9610/STAGE --skill stage-wanghao9610

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about stage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route a /stage request to a STAGE writing workflow skill?

Invoke /stage with your request, and the router reads .agents/commands/stage.md from the project root as the authoritative roster. It then starts the matching stage-* skill via the Skill tool without reproducing that skill's workflow.

What happens when I run /stage with no arguments?

With no request argument, the router shows the current paper status instead of routing to a workflow skill. It does not select a stage-* skill on its own.

Does the stage router support Chinese language output?

Yes. When .env sets STAGE_LANG=zh, or it is unset and the conversation is in Chinese, user-facing wording comes from .agents/commands/stage.zh-CN.md while skill names and routing decisions still follow the English roster.

What does the dagger mark mean in the STAGE routing roster?

A skill marked with † requires confirmation before invocation. The router requests the confirmation required by the roster, shows the exact /skill:stage-<name> <argument> invocation, and waits for the user.

Why does the stage router report a missing routing roster?

The router depends on .agents/commands/stage.md in the current project root. If that file is missing, it reports that the project does not contain the STAGE routing roster rather than guessing from the plugin package.