Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
epic-status - Prompt - OpenSmartRoute
Promptv1.0.0
epic-status
Run node .claude/scripts/pm/epic-status.js ${arguments} using the Bash tool and show me the complete output.
Prompt file imported from rafeekpro/voucher (.claude/commands/pm/epic-status.md). Fill in {{arguments}} before use. Copyright stays with the author.
Run node .claude/scripts/pm/epic-status.js {{arguments}} using the Bash tool and show me the complete output.
DO NOT truncate.
DO NOT collapse.
DO NOT abbreviate.
Show ALL lines in full.
DO NOT print any other comments.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
Run `node .claude/scripts/pm/epic-status.js {{arguments}}` using the Bash tool and show me the complete output.
- DO NOT truncate.
- DO NOT collapse.
- DO NOT abbreviate.
- Show ALL lines in full.
- DO NOT print any other comments.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "Run `node .claude/scripts/pm/epic-status.js {{arguments}}` using the Bash tool and show me the complete output.\n\n- DO NOT truncate.\n- DO NOT collapse.\n- DO NOT abbreviate.\n- Show ALL lines in full.\n- DO NOT print any other comments.",
"variables": [
"arguments"
],
"notes": "Run `node .claude/scripts/pm/epic-status.js ${arguments}` using the Bash tool and show me the complete output. Tools: Bash.",
"metadata": {
"source": {
"provider": "github-claude-commands",
"repository": "https://github.com/rafeekpro/voucher",
"path": ".claude/commands/pm/epic-status.md",
"ref": "88be2fccfbc3054824f1130b3157277043122964",
"url": "https://github.com/rafeekpro/voucher/blob/88be2fccfbc3054824f1130b3157277043122964/.claude/commands/pm/epic-status.md",
"key": "rafeekpro/voucher/.claude/commands/pm/epic-status.md"
}
}
}
Installed into a catalogue, chosen by a router
Install epic-status and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.