feat(skill): improving openspec and tested it

Author: jabrena

.cursor/rules/042-planning-openspec.md

@@ -87,6 +87,7 @@ openspec list
 
 - **MUST** run commands from the project directory context expected by OpenSpec
 - **MUST** distinguish between creating a fresh OpenSpec project vs updating an existing one
+- **MUST** use plain `openspec init` (without any `--tools ...` options) when initializing a new OpenSpec project
 
 ### Step 4: Create or Update a Change
 

skills-generator/src/main/resources/skills/042-skill.xml

@@ -32,6 +32,7 @@ Guide the process of turning an implementation plan (`*.plan.md`) into an OpenSp
       <constraint>**MUST**: Check CLI availability with `openspec --version` before any OpenSpec operation</constraint>
       <constraint>**MUST**: If OpenSpec is missing, provide macOS, Linux, and Windows install guidance via npm command</constraint>
       <constraint>**MUST**: Offer `openspec init` when no OpenSpec project exists</constraint>
+      <constraint>**MUST**: When creating a new OpenSpec project, run plain `openspec init` only (do not use `--tools ...` options)</constraint>
       <constraint>**MUST**: Use a stable change-id (for example: `add-dark-mode`) for status/show/archive commands</constraint>
       <constraint>**MUST**: Run `openspec validate --all` before archiving</constraint>
       <constraint>**MUST**: Explain whether the workflow creates a new change or updates an existing one</constraint>

skills/042-planning-openspec/SKILL.md

@@ -28,6 +28,7 @@ Always execute OpenSpec commands from the parent directory that contains the `op
 - **MUST**: Check CLI availability with `openspec --version` before any OpenSpec operation
 - **MUST**: If OpenSpec is missing, provide macOS, Linux, and Windows install guidance via npm command
 - **MUST**: Offer `openspec init` when no OpenSpec project exists
+- **MUST**: When creating a new OpenSpec project, run plain `openspec init` only (do not use `--tools ...` options)
 - **MUST**: Use a stable change-id (for example: `add-dark-mode`) for status/show/archive commands
 - **MUST**: Run `openspec validate --all` before archiving
 - **MUST**: Explain whether the workflow creates a new change or updates an existing one

skills/042-planning-openspec/references/042-planning-openspec.md

@@ -87,6 +87,7 @@ openspec list
 
 - **MUST** run commands from the project directory context expected by OpenSpec
 - **MUST** distinguish between creating a fresh OpenSpec project vs updating an existing one
+- **MUST** use plain `openspec init` (without any `--tools ...` options) when initializing a new OpenSpec project
 
 ### Step 4: Create or Update a Change
 

system-prompts-generator/src/main/resources/system-prompts/042-planning-openspec.xml

@@ -90,6 +90,7 @@ openspec list
                 <step-constraint-list>
                     <step-constraint>**MUST** run commands from the project directory context expected by OpenSpec</step-constraint>
                     <step-constraint>**MUST** distinguish between creating a fresh OpenSpec project vs updating an existing one</step-constraint>
+                    <step-constraint>**MUST** use plain `openspec init` (without any `--tools ...` options) when initializing a new OpenSpec project</step-constraint>
                 </step-constraint-list>
             </step-constraints>
         </step>