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-forensics - Prompt - OpenSmartRoute
Promptv1.0.0
gsd-forensics
Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
Prompt file imported from protoconf/protoconf (.windsurf/workflows/gsd-forensics.md). Copyright stays with the author.
gsd-forensics
Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
Read and execute the GSD command at @/Users/smintz/go/src/github.com/protoconf/protoconf/.windsurf/gsd-core/commands/gsd/forensics.md end-to-end. Treat the user's message after /gsd-forensics as the command arguments.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# gsd-forensics
Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
Read and execute the GSD command at @/Users/smintz/go/src/github.com/protoconf/protoconf/.windsurf/gsd-core/commands/gsd/forensics.md end-to-end. Treat the user's message after /gsd-forensics as the command arguments.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "# gsd-forensics\n\nPost-mortem investigation for failed GSD workflows — diagnoses what went wrong.\n\nRead and execute the GSD command at @/Users/smintz/go/src/github.com/protoconf/protoconf/.windsurf/gsd-core/commands/gsd/forensics.md end-to-end. Treat the user's message after /gsd-forensics as the command arguments.",
"variables": [],
"notes": "Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.",
"metadata": {
"source": {
"provider": "github-windsurf-workflows",
"repository": "https://github.com/protoconf/protoconf",
"path": ".windsurf/workflows/gsd-forensics.md",
"ref": "a5a7d208f190a5384392b37070eea141f87dc38b",
"url": "https://github.com/protoconf/protoconf/blob/a5a7d208f190a5384392b37070eea141f87dc38b/.windsurf/workflows/gsd-forensics.md",
"key": "protoconf/protoconf/.windsurf/workflows/gsd-forensics.md"
}
}
}
Installed into a catalogue, chosen by a router
Install gsd-forensics 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.