From 8b44fb0a24abb6d70f069bc11af4f8bbf62e5da9 Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=A9r=C3=B4me=20Benoit?= Date: Tue, 24 Feb 2026 11:25:46 +0100 Subject: [PATCH] chore: update openspec artifacts MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Jérôme Benoit --- .opencode/command/opsx-archive.md | 4 +- .opencode/command/opsx-bulk-archive.md | 2 +- .opencode/command/opsx-explore.md | 7 +-- .opencode/command/opsx-ff.md | 5 +- .opencode/command/opsx-onboard.md | 53 +++++++++++++----- .../skills/openspec-apply-change/SKILL.md | 2 +- .../skills/openspec-archive-change/SKILL.md | 4 +- .../openspec-bulk-archive-change/SKILL.md | 4 +- .../skills/openspec-continue-change/SKILL.md | 2 +- .opencode/skills/openspec-explore/SKILL.md | 12 ++-- .opencode/skills/openspec-ff-change/SKILL.md | 2 +- .opencode/skills/openspec-new-change/SKILL.md | 2 +- .opencode/skills/openspec-onboard/SKILL.md | 55 ++++++++++++++----- .opencode/skills/openspec-sync-specs/SKILL.md | 2 +- .../skills/openspec-verify-change/SKILL.md | 2 +- 15 files changed, 104 insertions(+), 54 deletions(-) diff --git a/.opencode/command/opsx-archive.md b/.opencode/command/opsx-archive.md index 30368fac..81617f2e 100644 --- a/.opencode/command/opsx-archive.md +++ b/.opencode/command/opsx-archive.md @@ -56,7 +56,7 @@ Archive a completed change in the experimental workflow. - If changes needed: "Sync now (recommended)", "Archive without syncing" - If already synced: "Archive now", "Sync anyway", "Cancel" - If user chooses sync, execute `/opsx-sync` logic. Proceed to archive regardless of choice. + If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change ''. Delta spec analysis: "). Proceed to archive regardless of choice. 5. **Perform the archive** @@ -152,5 +152,5 @@ Target archive directory already exists. - Don't block archive on warnings - just inform and confirm - Preserve .openspec.yaml when moving to archive (it moves with the directory) - Show clear summary of what happened -- If sync is requested, use /opsx-sync approach (agent-driven) +- If sync is requested, use the Skill tool to invoke `openspec-sync-specs` (agent-driven) - If delta specs exist, always run the sync assessment and show the combined summary before prompting diff --git a/.opencode/command/opsx-bulk-archive.md b/.opencode/command/opsx-bulk-archive.md index e4665153..650d2c1e 100644 --- a/.opencode/command/opsx-bulk-archive.md +++ b/.opencode/command/opsx-bulk-archive.md @@ -227,7 +227,7 @@ Failed K changes: ``` ## No Changes to Archive -No active changes found. Use `/opsx-new` to create a new change. +No active changes found. Create a new change to get started. ``` **Guardrails** diff --git a/.opencode/command/opsx-explore.md b/.opencode/command/opsx-explore.md index 0bc0357f..d929e41e 100644 --- a/.opencode/command/opsx-explore.md +++ b/.opencode/command/opsx-explore.md @@ -4,7 +4,7 @@ description: Enter explore mode - think through ideas, investigate problems, cla Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes. -**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first (e.g., start a change with `/opsx-new` or `/opsx-ff`). You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing. +**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing. **This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore. @@ -105,8 +105,7 @@ If the user mentioned a specific change name, read its artifacts for context. Think freely. When insights crystallize, you might offer: -- "This feels solid enough to start a change. Want me to create one?" - → Can transition to `/opsx-new` or `/opsx-ff` +- "This feels solid enough to start a change. Want me to create a proposal?" - Or keep exploring - no pressure to formalize ### When a change exists @@ -158,7 +157,7 @@ If the user mentions a change or you detect one is relevant: There's no required ending. Discovery might: -- **Flow into action**: "Ready to start? `/opsx-new` or `/opsx-ff`" +- **Flow into a proposal**: "Ready to start? I can create a change proposal." - **Result in artifact updates**: "Updated design.md with these decisions" - **Just provide clarity**: User has what they need, moves on - **Continue later**: "We can pick this up anytime" diff --git a/.opencode/command/opsx-ff.md b/.opencode/command/opsx-ff.md index 6704f37f..518b7b45 100644 --- a/.opencode/command/opsx-ff.md +++ b/.opencode/command/opsx-ff.md @@ -87,7 +87,10 @@ After completing all artifacts, summarize: - Follow the `instruction` field from `openspec instructions` for each artifact type - The schema defines what each artifact should contain - follow it - Read dependency artifacts for context before creating new ones -- Use the `template` as a starting point, filling in based on context +- Use `template` as the structure for your output file - fill in its sections +- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file + - Do NOT copy ``, ``, `` blocks into the artifact + - These guide what you write, but should never appear in the output **Guardrails** diff --git a/.opencode/command/opsx-onboard.md b/.opencode/command/opsx-onboard.md index 6cd4c3e3..bdb13383 100644 --- a/.opencode/command/opsx-onboard.md +++ b/.opencode/command/opsx-onboard.md @@ -8,17 +8,20 @@ Guide the user through their first complete OpenSpec workflow cycle. This is a t ## Preflight -Before starting, check if OpenSpec is initialized: +Before starting, check if the OpenSpec CLI is installed: ```bash -openspec status --json 2>&1 || echo "NOT_INITIALIZED" +# Unix/macOS +openspec --version 2>&1 || echo "CLI_NOT_INSTALLED" +# Windows (PowerShell) +# if (Get-Command openspec -ErrorAction SilentlyContinue) { openspec --version } else { echo "CLI_NOT_INSTALLED" } ``` -**If not initialized:** +**If CLI not installed:** -> OpenSpec isn't set up in this project yet. Run `openspec init` first, then come back to `/opsx-onboard`. +> OpenSpec CLI is not installed. Install it first, then come back to `/opsx-onboard`. -Stop here if not initialized. +Stop here if not installed. --- @@ -62,7 +65,10 @@ Scan the codebase for small improvement opportunities. Look for: Also check recent git activity: ```bash +# Unix/macOS git log --oneline -10 2>/dev/null || echo "No git history" +# Windows (PowerShell) +# git log --oneline -10 2>$null; if ($LASTEXITCODE -ne 0) { echo "No git history" } ``` ### Present Suggestions @@ -269,7 +275,10 @@ For a small task like this, we might only need one spec file. **DO:** Create the spec file: ```bash +# Unix/macOS mkdir -p openspec/changes//specs/ +# Windows (PowerShell) +# New-Item -ItemType Directory -Force -Path "openspec/changes//specs/" ``` Draft the spec content: @@ -470,21 +479,29 @@ This same rhythm works for any size change—a small fix or a major feature. ## Command Reference +**Core workflow:** + | Command | What it does | |---------|--------------| +| `/opsx-propose` | Create a change and generate all artifacts | | `/opsx-explore` | Think through problems before/during work | -| `/opsx-new` | Start a new change, step through artifacts | -| `/opsx-ff` | Fast-forward: create all artifacts at once | -| `/opsx-continue` | Continue working on an existing change | | `/opsx-apply` | Implement tasks from a change | -| `/opsx-verify` | Verify implementation matches artifacts | | `/opsx-archive` | Archive a completed change | +**Additional commands:** + +| Command | What it does | +|---------|--------------| +| `/opsx-new` | Start a new change, step through artifacts one at a time | +| `/opsx-continue` | Continue working on an existing change | +| `/opsx-ff` | Fast-forward: create all artifacts at once | +| `/opsx-verify` | Verify implementation matches artifacts | + --- ## What's Next? -Try `/opsx-new` or `/opsx-ff` on something you actually want to build. You've got the rhythm now! +Try `/opsx-propose` on something you actually want to build. You've got the rhythm now! ``` --- @@ -514,17 +531,25 @@ If the user says they just want to see the commands or skip the tutorial: ``` ## OpenSpec Quick Reference +**Core workflow:** + | Command | What it does | |---------|--------------| +| `/opsx-propose ` | Create a change and generate all artifacts | | `/opsx-explore` | Think through problems (no code changes) | +| `/opsx-apply ` | Implement tasks | +| `/opsx-archive ` | Archive when done | + +**Additional commands:** + +| Command | What it does | +|---------|--------------| | `/opsx-new ` | Start a new change, step by step | -| `/opsx-ff ` | Fast-forward: all artifacts at once | | `/opsx-continue ` | Continue an existing change | -| `/opsx-apply ` | Implement tasks | +| `/opsx-ff ` | Fast-forward: all artifacts at once | | `/opsx-verify ` | Verify implementation | -| `/opsx-archive ` | Archive when done | -Try `/opsx-new` to start your first change, or `/opsx-ff` if you want to move fast. +Try `/opsx-propose` to start your first change. ``` Exit gracefully. diff --git a/.opencode/skills/openspec-apply-change/SKILL.md b/.opencode/skills/openspec-apply-change/SKILL.md index 05c2e2e8..7c69d4ab 100644 --- a/.opencode/skills/openspec-apply-change/SKILL.md +++ b/.opencode/skills/openspec-apply-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Implement tasks from an OpenSpec change. diff --git a/.opencode/skills/openspec-archive-change/SKILL.md b/.opencode/skills/openspec-archive-change/SKILL.md index a6986f67..4163d134 100644 --- a/.opencode/skills/openspec-archive-change/SKILL.md +++ b/.opencode/skills/openspec-archive-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Archive a completed change in the experimental workflow. @@ -63,7 +63,7 @@ Archive a completed change in the experimental workflow. - If changes needed: "Sync now (recommended)", "Archive without syncing" - If already synced: "Archive now", "Sync anyway", "Cancel" - If user chooses sync, execute /opsx-sync logic (use the openspec-sync-specs skill). Proceed to archive regardless of choice. + If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change ''. Delta spec analysis: "). Proceed to archive regardless of choice. 5. **Perform the archive** diff --git a/.opencode/skills/openspec-bulk-archive-change/SKILL.md b/.opencode/skills/openspec-bulk-archive-change/SKILL.md index cc0c0d7c..db6cf213 100644 --- a/.opencode/skills/openspec-bulk-archive-change/SKILL.md +++ b/.opencode/skills/openspec-bulk-archive-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Archive multiple completed changes in a single operation. @@ -234,7 +234,7 @@ Failed K changes: ``` ## No Changes to Archive -No active changes found. Use `/opsx-new` to create a new change. +No active changes found. Create a new change to get started. ``` **Guardrails** diff --git a/.opencode/skills/openspec-continue-change/SKILL.md b/.opencode/skills/openspec-continue-change/SKILL.md index 08258191..8f7f0ae4 100644 --- a/.opencode/skills/openspec-continue-change/SKILL.md +++ b/.opencode/skills/openspec-continue-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Continue working on a change by creating the next artifact. diff --git a/.opencode/skills/openspec-explore/SKILL.md b/.opencode/skills/openspec-explore/SKILL.md index 3c8c4418..3cb68812 100644 --- a/.opencode/skills/openspec-explore/SKILL.md +++ b/.opencode/skills/openspec-explore/SKILL.md @@ -6,12 +6,12 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes. -**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first (e.g., start a change with `/opsx-new` or `/opsx-ff`). You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing. +**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing. **This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore. @@ -102,8 +102,7 @@ This tells you: Think freely. When insights crystallize, you might offer: -- "This feels solid enough to start a change. Want me to create one?" - → Can transition to `/opsx-new` or `/opsx-ff` +- "This feels solid enough to start a change. Want me to create a proposal?" - Or keep exploring - no pressure to formalize ### When a change exists @@ -263,7 +262,7 @@ You: That changes everything. There's no required ending. Discovery might: -- **Flow into action**: "Ready to start? /opsx-new or /opsx-ff" +- **Flow into a proposal**: "Ready to start? I can create a change proposal." - **Result in artifact updates**: "Updated design.md with these decisions" - **Just provide clarity**: User has what they need, moves on - **Continue later**: "We can pick this up anytime" @@ -280,8 +279,7 @@ When it feels like things are crystallizing, you might summarize: **Open questions**: [if any remain] **Next steps** (if ready): -- Create a change: /opsx-new -- Fast-forward to tasks: /opsx-ff +- Create a change proposal - Keep exploring: just keep talking ``` diff --git a/.opencode/skills/openspec-ff-change/SKILL.md b/.opencode/skills/openspec-ff-change/SKILL.md index 491e2143..111e4fe5 100644 --- a/.opencode/skills/openspec-ff-change/SKILL.md +++ b/.opencode/skills/openspec-ff-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Fast-forward through artifact creation - generate everything needed to start implementation in one go. diff --git a/.opencode/skills/openspec-new-change/SKILL.md b/.opencode/skills/openspec-new-change/SKILL.md index fd3ad14e..179bb03f 100644 --- a/.opencode/skills/openspec-new-change/SKILL.md +++ b/.opencode/skills/openspec-new-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Start a new change using the experimental artifact-driven approach. diff --git a/.opencode/skills/openspec-onboard/SKILL.md b/.opencode/skills/openspec-onboard/SKILL.md index c800a5d6..addace78 100644 --- a/.opencode/skills/openspec-onboard/SKILL.md +++ b/.opencode/skills/openspec-onboard/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step. @@ -15,17 +15,20 @@ Guide the user through their first complete OpenSpec workflow cycle. This is a t ## Preflight -Before starting, check if OpenSpec is initialized: +Before starting, check if the OpenSpec CLI is installed: ```bash -openspec status --json 2>&1 || echo "NOT_INITIALIZED" +# Unix/macOS +openspec --version 2>&1 || echo "CLI_NOT_INSTALLED" +# Windows (PowerShell) +# if (Get-Command openspec -ErrorAction SilentlyContinue) { openspec --version } else { echo "CLI_NOT_INSTALLED" } ``` -**If not initialized:** +**If CLI not installed:** -> OpenSpec isn't set up in this project yet. Run `openspec init` first, then come back to `/opsx-onboard`. +> OpenSpec CLI is not installed. Install it first, then come back to `/opsx-onboard`. -Stop here if not initialized. +Stop here if not installed. --- @@ -69,7 +72,10 @@ Scan the codebase for small improvement opportunities. Look for: Also check recent git activity: ```bash +# Unix/macOS git log --oneline -10 2>/dev/null || echo "No git history" +# Windows (PowerShell) +# git log --oneline -10 2>$null; if ($LASTEXITCODE -ne 0) { echo "No git history" } ``` ### Present Suggestions @@ -276,7 +282,10 @@ For a small task like this, we might only need one spec file. **DO:** Create the spec file: ```bash +# Unix/macOS mkdir -p openspec/changes//specs/ +# Windows (PowerShell) +# New-Item -ItemType Directory -Force -Path "openspec/changes//specs/" ``` Draft the spec content: @@ -477,21 +486,29 @@ This same rhythm works for any size change—a small fix or a major feature. ## Command Reference +**Core workflow:** + | Command | What it does | |---------|--------------| +| `/opsx-propose` | Create a change and generate all artifacts | | `/opsx-explore` | Think through problems before/during work | -| `/opsx-new` | Start a new change, step through artifacts | -| `/opsx-ff` | Fast-forward: create all artifacts at once | -| `/opsx-continue` | Continue working on an existing change | | `/opsx-apply` | Implement tasks from a change | -| `/opsx-verify` | Verify implementation matches artifacts | | `/opsx-archive` | Archive a completed change | +**Additional commands:** + +| Command | What it does | +|---------|--------------| +| `/opsx-new` | Start a new change, step through artifacts one at a time | +| `/opsx-continue` | Continue working on an existing change | +| `/opsx-ff` | Fast-forward: create all artifacts at once | +| `/opsx-verify` | Verify implementation matches artifacts | + --- ## What's Next? -Try `/opsx-new` or `/opsx-ff` on something you actually want to build. You've got the rhythm now! +Try `/opsx-propose` on something you actually want to build. You've got the rhythm now! ``` --- @@ -521,17 +538,25 @@ If the user says they just want to see the commands or skip the tutorial: ``` ## OpenSpec Quick Reference +**Core workflow:** + | Command | What it does | |---------|--------------| +| `/opsx-propose ` | Create a change and generate all artifacts | | `/opsx-explore` | Think through problems (no code changes) | +| `/opsx-apply ` | Implement tasks | +| `/opsx-archive ` | Archive when done | + +**Additional commands:** + +| Command | What it does | +|---------|--------------| | `/opsx-new ` | Start a new change, step by step | -| `/opsx-ff ` | Fast-forward: all artifacts at once | | `/opsx-continue ` | Continue an existing change | -| `/opsx-apply ` | Implement tasks | +| `/opsx-ff ` | Fast-forward: all artifacts at once | | `/opsx-verify ` | Verify implementation | -| `/opsx-archive ` | Archive when done | -Try `/opsx-new` to start your first change, or `/opsx-ff` if you want to move fast. +Try `/opsx-propose` to start your first change. ``` Exit gracefully. diff --git a/.opencode/skills/openspec-sync-specs/SKILL.md b/.opencode/skills/openspec-sync-specs/SKILL.md index 5154438a..a14f27dc 100644 --- a/.opencode/skills/openspec-sync-specs/SKILL.md +++ b/.opencode/skills/openspec-sync-specs/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Sync delta specs from a change to main specs. diff --git a/.opencode/skills/openspec-verify-change/SKILL.md b/.opencode/skills/openspec-verify-change/SKILL.md index 90fc30ff..051f4b12 100644 --- a/.opencode/skills/openspec-verify-change/SKILL.md +++ b/.opencode/skills/openspec-verify-change/SKILL.md @@ -6,7 +6,7 @@ compatibility: Requires openspec CLI. metadata: author: openspec version: '1.0' - generatedBy: '1.1.1' + generatedBy: '1.2.0' --- Verify that an implementation matches the change artifacts (specs, tasks, design). -- 2.43.0