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.
Prompt file imported from ClockIn215/Clockin (.claude/commands/gsd/ai-integration-phase.md). Fill in {{arguments}} before use. Copyright stays with the author.
Copy one of these into your project. Installing also returns the manifest and these snippets.
<objective>
Create an AI design contract (AI-SPEC.md) for a phase involving AI system development.
Orchestrates gsd-framework-selector → gsd-ai-researcher → gsd-domain-researcher → gsd-eval-planner.
Flow: Select Framework → Research Docs → Research Domain → Design Eval Strategy → Done
</objective>
<execution_context>
@C:/Users/Gaski/Clockin/.claude/gsd-core/workflows/ai-integration-phase.md
@C:/Users/Gaski/Clockin/.claude/gsd-core/references/ai-frameworks.md
@C:/Users/Gaski/Clockin/.claude/gsd-core/references/ai-evals.md
</execution_context>
<context>
Phase number: {{arguments}} — optional, auto-detects next unplanned phase if omitted.
</context>
<process>
Execute end-to-end.
Preserve all workflow gates.
</process>
Manifest
Installed into a catalogue, chosen by a router
Install gsd-ai-integration-phase 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.