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
feat(init): add IDE restart instruction after init (Fission-AI#323)
Add prominent restart instruction in success message to inform users
they need to restart their IDE/coding tool for slash commands to appear.
Applies to all tools when slash commands are created or refreshed.
Also updates cli-init spec to document the restart instruction requirement.
Copy file name to clipboardExpand all lines: openspec/specs/cli-init/spec.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,6 +76,12 @@ The command SHALL properly configure selected AI tools with OpenSpec-specific in
76
76
-**THEN** create or update `CLINE.md` in the project root directory (not inside openspec/)
77
77
-**AND** populate the managed block with a short stub that points teammates to `@/openspec/AGENTS.md`
78
78
79
+
#### Scenario: Configuring iFlow CLI
80
+
81
+
-**WHEN** iFlow CLI is selected
82
+
-**THEN** create or update `IFLOW.md` in the project root directory (not inside openspec/)
83
+
-**AND** populate the managed block with a short stub that points teammates to `@/openspec/AGENTS.md`
84
+
79
85
#### Scenario: Creating new CLAUDE.md
80
86
81
87
-**WHEN** CLAUDE.md does not exist
@@ -118,6 +124,12 @@ The command SHALL provide clear, actionable next steps upon successful initializ
118
124
-**WHEN** initialization completes successfully
119
125
-**THEN** include prompt: "Please explain the OpenSpec workflow from openspec/AGENTS.md and how I should work with you on this project"
120
126
127
+
#### Scenario: Displaying restart instruction
128
+
-**WHEN** initialization completes successfully and tools were created or refreshed
129
+
-**THEN** display a prominent restart instruction before the "Next steps" section
130
+
-**AND** inform users that slash commands are loaded at startup
131
+
-**AND** instruct users to restart their coding assistant to ensure /openspec commands appear
132
+
121
133
### Requirement: Exit Codes
122
134
123
135
The command SHALL use consistent exit codes to indicate different failure modes.
@@ -238,6 +250,14 @@ The init command SHALL generate slash command files for supported editors using
238
250
-**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
251
-**AND** ensure the slash-command copy matches the existing proposal/apply/archive templates used by other tools
240
252
253
+
#### Scenario: Generating slash commands for iFlow CLI
254
+
-**WHEN** the user selects iFlow CLI during initialization
255
+
-**THEN** create `.iflow/commands/openspec-proposal.md`, `.iflow/commands/openspec-apply.md`, and `.iflow/commands/openspec-archive.md`
256
+
-**AND** populate each file from shared templates so command text matches other tools
257
+
-**AND** include YAML frontmatter with `name`, `id`, `category`, and `description` fields for each command
258
+
-**AND** wrap the generated content in OpenSpec managed markers so `openspec update` can safely refresh the commands
259
+
-**AND** each template includes instructions for the relevant OpenSpec workflow stage
260
+
241
261
#### Scenario: Generating slash commands for RooCode
242
262
-**WHEN** the user selects RooCode during initialization
243
263
-**THEN** create `.roo/commands/openspec-proposal.md`, `.roo/commands/openspec-apply.md`, and `.roo/commands/openspec-archive.md`
Copy file name to clipboardExpand all lines: openspec/specs/cli-update/spec.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,6 +123,13 @@ The update command SHALL refresh existing slash command files for configured too
123
123
-**AND** replace only the content between `<!-- OPENSPEC:START -->` and `<!-- OPENSPEC:END -->` markers inside the `prompt = """` block so the TOML framing (`description`, `prompt`) stays intact
124
124
-**AND** skip creating any missing `.toml` files during update; only pre-existing Gemini commands are refreshed
125
125
126
+
#### Scenario: Updating slash commands for iFlow CLI
127
+
-**WHEN**`.iflow/commands/` contains `openspec-proposal.md`, `openspec-apply.md`, and `openspec-archive.md`
128
+
-**THEN** refresh each file using shared templates
129
+
-**AND** preserve the YAML frontmatter with `name`, `id`, `category`, and `description` fields
130
+
-**AND** update only the OpenSpec-managed block between markers
131
+
-**AND** ensure templates include instructions for the relevant workflow stage
0 commit comments