You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -233,7 +234,7 @@ Or run the command yourself in terminal:
233
234
$ openspec archive add-profile-filters --yes # Archive the completed change without prompts
234
235
```
235
236
236
-
**Note:** Tools with native slash commands (Claude Code, CodeBuddy, Cursor, Codex, Qoder) can use the shortcuts shown. All other tools work with natural language requests to "create an OpenSpec proposal", "apply the OpenSpec change", or "archive the change".
237
+
**Note:** Tools with native slash commands (Claude Code, CodeBuddy, Cursor, Codex, Qoder, RooCode) can use the shortcuts shown. All other tools work with natural language requests to "create an OpenSpec proposal", "apply the OpenSpec change", or "archive the change".
Copy file name to clipboardExpand all lines: openspec/specs/cli-init/spec.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -238,6 +238,14 @@ The init command SHALL generate slash command files for supported editors using
238
238
-**AND** wrap the OpenSpec managed markers (`<!-- OPENSPEC:START -->` / `<!-- OPENSPEC:END -->`) inside the `prompt` value so `openspec update` can safely refresh the body between markers without touching the TOML framing
239
239
-**AND** ensure the slash-command copy matches the existing proposal/apply/archive templates used by other tools
240
240
241
+
#### Scenario: Generating slash commands for RooCode
242
+
-**WHEN** the user selects RooCode during initialization
243
+
-**THEN** create `.roo/commands/openspec-proposal.md`, `.roo/commands/openspec-apply.md`, and `.roo/commands/openspec-archive.md`
244
+
-**AND** populate each file from shared templates so command text matches other tools
245
+
-**AND** include simple Markdown headings (e.g., `# OpenSpec: Proposal`) without YAML frontmatter
246
+
-**AND** wrap the generated content in OpenSpec managed markers where applicable so `openspec update` can safely refresh the commands
247
+
-**AND** each template includes instructions for the relevant OpenSpec workflow stage
248
+
241
249
### Requirement: Non-Interactive Mode
242
250
The command SHALL support non-interactive operation through command-line options for automation and CI/CD use cases.
0 commit comments