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 leopoldlacroix/Cognyx_case (.cursor/commands/gsd/list-phase-assumptions.md). Fill in {{arguments}} before use. Copyright stays with the author.
Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong.
Output: Conversational output only (no file creation) - ends with "What do you think?" prompt
User knows next steps (discuss context, plan phase, or correct assumptions)
</success_criteria>
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
<objective>
Analyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.
Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong.
Output: Conversational output only (no file creation) - ends with"What do you think?" prompt
</objective>
<execution_context>
@./.cursor/get-shit-done/workflows/list-phase-assumptions.md
</execution_context>
<context>
Phase number: {{arguments}} (required)
**Load project state first:**
@.planning/STATE.md
**Load roadmap:**
@.planning/ROADMAP.md
</context>
<process>
1. Validate phase number argument (error if missing or invalid)
2. Check if phase exists in roadmap
3. Follow list-phase-assumptions.md workflow:
- Analyze roadmap description
- Surface assumptions about: technical approach, implementation order, scope, risks, dependencies
- Present assumptions clearly
- Prompt "What do you think?"4. Gather feedback and offer next steps
</process>
<success_criteria>
- Phase validated against roadmap
- Assumptions surfaced across five areas
- User prompted for feedback
- User knows next steps (discuss context, plan phase, or correct assumptions)
</success_criteria>
Installed into a catalogue, chosen by a router
Install gsd/list-phase-assumptions 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.
{
"prompt": "<objective>\r\nAnalyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.\r\n\r\nPurpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong.\r\nOutput: Conversational output only (no file creation) - ends with \"What do you think?\" prompt\r\n</objective>\r\n\r\n<execution_context>\r\n@./.cursor/get-shit-done/workflows/list-phase-assumptions.md\r\n</execution_context>\r\n\r\n<context>\r\nPhase number: {{arguments}} (required)\r\n\r\n**Load project state first:**\r\n@.planning/STATE.md\r\n\r\n**Load roadmap:**\r\n@.planning/ROADMAP.md\r\n</context>\r\n\r\n<process>\r\n1. Validate phase number argument (error if missing or invalid)\r\n2. Check if phase exists in roadmap\r\n3. Follow list-phase-assumptions.md workflow:\r\n - Analyze roadmap description\r\n - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies\r\n - Present assumptions clearly\r\n - Prompt \"What do you think?\"\r\n4. Gather feedback and offer next steps\r\n</process>\r\n\r\n<success_criteria>\r\n\r\n- Phase validated against roadmap\r\n- Assumptions surfaced across five areas\r\n- User prompted for feedback\r\n- User knows next steps (discuss context, plan phase, or correct assumptions)\r\n </success_criteria>",
"variables": [
"arguments"
],
"notes": "Surface Claude's assumptions about a phase approach before planning Tools: Read, Bash, Grep, Glob. Arguments: [phase].",
"metadata": {
"source": {
"provider": "github-cursor-commands",
"repository": "https://github.com/leopoldlacroix/Cognyx_case",
"path": ".cursor/commands/gsd/list-phase-assumptions.md",
"ref": "aa57ce7c360a57db6f22751eb65b71a8b327ef9a",
"url": "https://github.com/leopoldlacroix/Cognyx_case/blob/aa57ce7c360a57db6f22751eb65b71a8b327ef9a/.cursor/commands/gsd/list-phase-assumptions.md",
"key": "leopoldlacroix/Cognyx_case/.cursor/commands/gsd/list-phase-assumptions.md"
}
}
}
Fetch it by URL: GET /api/v1/registry/leopoldlacroix-cognyx-case-list-phase-assumptions-cursor-7909ea/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
