Name: /openspec-proposal
Author: zzxtbeta

Prompt file imported from zzxtbeta/rag_demo (.cursor/commands/openspec-proposal.md). Copyright stays with the author.

Guardrails

Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
Keep changes tightly scoped to the requested outcome.
Refer to openspec/AGENTS.md (located inside the openspec/ directory—run ls openspec or openspec update if you don't see it) if you need additional OpenSpec conventions or clarifications.
Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.

Steps

Review openspec/project.md, run openspec list and openspec list --specs, and inspect related code or docs (e.g., via rg/ls) to ground the proposal in current behaviour; note any gaps that require clarification.
Choose a unique verb-led change-id and scaffold proposal.md, tasks.md, and design.md (when needed) under openspec/changes/<id>/.
Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
Capture architectural reasoning in design.md when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
Draft spec deltas in changes/<id>/specs/<capability>/spec.md (one folder per capability) using ## ADDED|MODIFIED|REMOVED Requirements with at least one #### Scenario: per requirement and cross-reference related capabilities when relevant.
Draft tasks.md as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
Validate with openspec validate <id> --strict and resolve every issue before sharing the proposal.

Reference

Use openspec show <id> --json --deltas-only or openspec show <spec> --type spec to inspect details when validation fails.
Search existing requirements with rg -n "Requirement:|Scenario:" openspec/specs before writing new ones.
Explore the codebase with rg <keyword>, ls, or direct file reads so proposals align with current implementation realities.

Install /openspec-proposal 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.

**Guardrails** - Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required. - Keep changes tightly scoped to the requested outcome. - Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications. - Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files. **Steps** 1. Review `openspec/project.md`, run `openspec list` and `openspec list --specs`, and inspect related code or docs (e.g., via `rg`/`ls`) to ground the proposal in current behaviour; note any gaps that require clarification. 2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, and `design.md` (when needed) under `openspec/changes/<id>/`. 3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing. 4. Capture architectural reasoning in `design.md` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs. 5. Draft spec deltas in `changes/<id>/specs/<capability>/spec.md` (one folder per capability) using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement and cross-reference related capabilities when relevant. 6. Draft `tasks.md` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work. 7. Validate with `openspec validate <id> --strict` and resolve every issue before sharing the proposal. **Reference** - Use `openspec show <id> --json --deltas-only` or `openspec show <spec> --type spec` to inspect details when validation fails. - Search existing requirements with `rg -n "Requirement:|Scenario:" openspec/specs` before writing new ones. - Explore the codebase with `rg <keyword>`, `ls`, or direct file reads so proposals align with current implementation realities.

{ "prompt": "\n**Guardrails**\n- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.\n- Keep changes tightly scoped to the requested outcome.\n- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.\n- Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.\n\n**Steps**\n1. Review `openspec/project.md`, run `openspec list` and `openspec list --specs`, and inspect related code or docs (e.g., via `rg`/`ls`) to ground the proposal in current behaviour; note any gaps that require clarification.\n2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, and `design.md` (when needed) under `openspec/changes/<id>/`.\n3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.\n4. Capture architectural reasoning in `design.md` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.\n5. Draft spec deltas in `changes/<id>/specs/<capability>/spec.md` (one folder per capability) using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement and cross-reference related capabilities when relevant.\n6. Draft `tasks.md` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.\n7. Validate with `openspec validate <id> --strict` and resolve every issue before sharing the proposal.\n\n**Reference**\n- Use `openspec show <id> --json --deltas-only` or `openspec show <spec> --type spec` to inspect details when validation fails.\n- Search existing requirements with `rg -n \"Requirement:|Scenario:\" openspec/specs` before writing new ones.\n- Explore the codebase with `rg <keyword>`, `ls`, or direct file reads so proposals align with current implementation realities.\n", "variables": [], "notes": "Scaffold a new OpenSpec change and validate strictly.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/zzxtbeta/rag_demo", "path": ".cursor/commands/openspec-proposal.md", "ref": "86bad9e1dc451e8e48bb8ae175493bb89840e3d1", "url": "https://github.com/zzxtbeta/rag_demo/blob/86bad9e1dc451e8e48bb8ae175493bb89840e3d1/.cursor/commands/openspec-proposal.md", "key": "zzxtbeta/rag_demo/.cursor/commands/openspec-proposal.md" } } }

/openspec-proposal

About

Install /openspec-proposal and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews