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.
gsd:audit-uat - Prompt - OpenSmartRoute
Promptv1.0.0
gsd:audit-uat
Cross-phase audit of all outstanding UAT and verification items
Copy one of these into your project. Installing also returns the manifest and these snippets.
<objective>
Scan all phases for pending, skipped, blocked, and human_needed UAT items. Cross-reference against codebase to detect stale documentation. Produce prioritized human test plan.
</objective>
<execution_context>
@M:/Prince-Picker-main/.claude/get-shit-done/workflows/audit-uat.md
</execution_context>
<context>
Core planning files are loaded in-workflow via CLI.
**Scope:**
Glob: .planning/phases/*/*-UAT.md
Glob: .planning/phases/*/*-VERIFICATION.md
</context>
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "<objective>\nScan all phases for pending, skipped, blocked, and human_needed UAT items. Cross-reference against codebase to detect stale documentation. Produce prioritized human test plan.\n</objective>\n\n<execution_context>\n@M:/Prince-Picker-main/.claude/get-shit-done/workflows/audit-uat.md\n</execution_context>\n\n<context>\nCore planning files are loaded in-workflow via CLI.\n\n**Scope:**\nGlob: .planning/phases/*/*-UAT.md\nGlob: .planning/phases/*/*-VERIFICATION.md\n</context>",
"variables": [],
"notes": "Cross-phase audit of all outstanding UAT and verification items Tools: Read, Glob, Grep, Bash.",
"metadata": {
"source": {
"provider": "github-claude-commands",
"repository": "https://github.com/mudasirhub/Prince-Picker",
"path": ".claude/commands/gsd/audit-uat.md",
"ref": "6d5530fdc328d9dd26aea9e49868c22417a0ddff",
"url": "https://github.com/mudasirhub/Prince-Picker/blob/6d5530fdc328d9dd26aea9e49868c22417a0ddff/.claude/commands/gsd/audit-uat.md",
"key": "mudasirhub/Prince-Picker/.claude/commands/gsd/audit-uat.md"
}
}
}
Installed into a catalogue, chosen by a router
Install gsd:audit-uat 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.