From: Jérôme Benoit Date: Tue, 24 Feb 2026 10:58:10 +0000 (+0100) Subject: chore: update OpenSpec artifacts X-Git-Url: https://git.piment-noir.org/?a=commitdiff_plain;h=c34df1a1ee9fb287f162336a1827754161851f7c;p=freqai-strategies.git chore: update OpenSpec artifacts Signed-off-by: Jérôme Benoit --- diff --git a/.gitignore b/.gitignore index 084f536..8d125ac 100644 --- a/.gitignore +++ b/.gitignore @@ -387,3 +387,5 @@ config.json */.clinerules/** */openspec */openspec/** +*/.sisyphus/ +*/.sisyphus/** diff --git a/.opencode/command/opsx-archive.md b/.opencode/command/opsx-archive.md index 30368fa..81617f2 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 e466515..650d2c1 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 0bc0357..d929e41 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 6704f37..518b7b4 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 6cd4c3e..bdb1338 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 8b13653..090d9e5 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 403a559..9fbd5a4 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 8174e31..7414bee 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 022e11c..4b25f48 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 ef2110d..1c4d939 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 d7edd3d..5dbe8bf 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 a6bdcf8..4e3af60 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 28e6788..a9f71c5 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 6252e62..e1070d7 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 2dee045..89cfb3c 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). diff --git a/.serena/project.yml b/.serena/project.yml index bd765f8..e2897dd 100644 --- a/.serena/project.yml +++ b/.serena/project.yml @@ -1,4 +1,3 @@ - # the encoding used by text files in the project # For a list of possible encodings, see https://docs.python.org/3.11/library/codecs.html#standard-encodings encoding: "utf-8" @@ -88,7 +87,6 @@ included_optional_tools: [] # This cannot be combined with non-empty excluded_tools or included_optional_tools. fixed_tools: [] - # list of languages for which language servers are started; choose from: # al bash clojure cpp csharp # csharp_omnisharp dart elixir elm erlang @@ -113,4 +111,8 @@ fixed_tools: [] # The first language is the default language and the respective language server will be used as a fallback. # Note that when using the JetBrains backend, language servers are not used and this list is correspondingly ignored. languages: -- python + - python + +# override of the corresponding setting in serena_config.yml, see the documentation there. +# If null or missing, the value from the global config is used. +symbol_info_budget: