iu/ds-galo
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

chore: refresh generated OpenSpec commands and skills

Browse Source
This commit is contained in:
iu
2026-10-11 18:10:34 +03:00
parent c2b0d9c66f
commit 6ccb7764e8
7 changed files with 14 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.opencode/commands/opsx-apply.md
+4 -3
View File
@@ -59,7 +59,7 @@ In both branches, never create the root as a side effect: do not run `openspec i
- If `state: "blocked"`: show the message and pause implementation. - If `state: "blocked"`: show the message and pause implementation.
- If `missingArtifacts` is non-empty: suggest completing the missing artifacts. Run `openspec status --change "<name>" --json`, select the next `ready` artifact (not `skipped` or `blocked`), and use `openspec instructions "<artifact-id>" --change "<name>" --json` for its rules and template. Keep the selected `--store <id>` on both commands. - If `missingArtifacts` is non-empty: suggest completing the missing artifacts. Run `openspec status --change "<name>" --json`, select the next `ready` artifact (not `skipped` or `blocked`), and use `openspec instructions "<artifact-id>" --change "<name>" --json` for its rules and template. Keep the selected `--store <id>` on both commands.
- Otherwise, follow the CLI instruction to create or repair the schema-configured tracking file from existing planning artifacts. Do not assume another artifact is ready or start implementation while blocked. - Otherwise, follow the CLI instruction to create or repair the schema-configured tracking file from existing planning artifacts. Do not assume another artifact is ready or start implementation while blocked.
- If `state: "all_done"`: congratulate, suggest archive - If `state: "all_done"`: report that all tracked tasks are complete and suggest review or verification as appropriate before archiving
- Otherwise: proceed to implementation - Otherwise: proceed to implementation
Treat `context` as a required prompt-level input. Read and consider it, and Treat `context` as a required prompt-level input. Read and consider it, and
@@ -118,7 +118,7 @@ In both branches, never create the root as a side effect: do not run `openspec i
Display: Display:
- Tasks completed this session - Tasks completed this session
- Overall progress: "N/M tasks complete" - Overall progress: "N/M tasks complete"
- If all done: suggest archive - If all done: report that tracked tasks are complete and suggest review or verification as appropriate before archiving
- If paused: explain why and wait for guidance - If paused: explain why and wait for guidance
**Output During Implementation** **Output During Implementation**
@@ -149,7 +149,8 @@ Working on task 4/7: <task description>
- [x] Task 2 - [x] Task 2
... ...
All tasks complete! You can archive this change with `/opsx-archive`. All tracked tasks are complete. Review or verify the change as appropriate
before archiving. You can archive this change with `/opsx-archive`.
``` ```
**Output On Pause (Issue Encountered)** **Output On Pause (Issue Encountered)**
.opencode/skills/openspec-apply-change/SKILL.md
+5 -4
View File
@@ -7,7 +7,7 @@ compatibility: Requires openspec CLI.
metadata: metadata:
author: openspec author: openspec
version: "1.0" version: "1.0"
generatedBy: "1.14.0" generatedBy: "1.14.1"
--- ---
Implement tasks from an OpenSpec change. Implement tasks from an OpenSpec change.
@@ -66,7 +66,7 @@ In both branches, never create the root as a side effect: do not run `openspec i
- If `state: "blocked"`: show the message and pause implementation. - If `state: "blocked"`: show the message and pause implementation.
- If `missingArtifacts` is non-empty: suggest completing the missing artifacts. Run `openspec status --change "<name>" --json`, select the next `ready` artifact (not `skipped` or `blocked`), and use `openspec instructions "<artifact-id>" --change "<name>" --json` for its rules and template. Keep the selected `--store <id>` on both commands. - If `missingArtifacts` is non-empty: suggest completing the missing artifacts. Run `openspec status --change "<name>" --json`, select the next `ready` artifact (not `skipped` or `blocked`), and use `openspec instructions "<artifact-id>" --change "<name>" --json` for its rules and template. Keep the selected `--store <id>` on both commands.
- Otherwise, follow the CLI instruction to create or repair the schema-configured tracking file from existing planning artifacts. Do not assume another artifact is ready or start implementation while blocked. - Otherwise, follow the CLI instruction to create or repair the schema-configured tracking file from existing planning artifacts. Do not assume another artifact is ready or start implementation while blocked.
- If `state: "all_done"`: congratulate, suggest archive - If `state: "all_done"`: report that all tracked tasks are complete and suggest review or verification as appropriate before archiving
- Otherwise: proceed to implementation - Otherwise: proceed to implementation
Treat `context` as a required prompt-level input. Read and consider it, and Treat `context` as a required prompt-level input. Read and consider it, and
@@ -125,7 +125,7 @@ In both branches, never create the root as a side effect: do not run `openspec i
Display: Display:
- Tasks completed this session - Tasks completed this session
- Overall progress: "N/M tasks complete" - Overall progress: "N/M tasks complete"
- If all done: suggest archive - If all done: report that tracked tasks are complete and suggest review or verification as appropriate before archiving
- If paused: explain why and wait for guidance - If paused: explain why and wait for guidance
**Output During Implementation** **Output During Implementation**
@@ -156,7 +156,8 @@ Working on task 4/7: <task description>
- [x] Task 2 - [x] Task 2
... ...
All tasks complete! You can archive this change with `/opsx-archive`. All tracked tasks are complete. Review or verify the change as appropriate
before archiving. You can archive this change with `/opsx-archive`.
``` ```
**Output On Pause (Issue Encountered)** **Output On Pause (Issue Encountered)**
.opencode/skills/openspec-archive-change/SKILL.md
+1 -1
View File
@@ -7,7 +7,7 @@ compatibility: Requires openspec CLI.
metadata: metadata:
author: openspec author: openspec
version: "1.0" version: "1.0"
generatedBy: "1.14.0" generatedBy: "1.14.1"
--- ---
Archive a completed change in the experimental workflow. Archive a completed change in the experimental workflow.
.opencode/skills/openspec-explore/SKILL.md
+1 -1
View File
@@ -7,7 +7,7 @@ compatibility: Requires openspec CLI.
metadata: metadata:
author: openspec author: openspec
version: "1.0" version: "1.0"
generatedBy: "1.14.0" generatedBy: "1.14.1"
--- ---
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes. Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
.opencode/skills/openspec-propose/SKILL.md
+1 -1
View File
@@ -7,7 +7,7 @@ compatibility: Requires openspec CLI.
metadata: metadata:
author: openspec author: openspec
version: "1.0" version: "1.0"
generatedBy: "1.14.0" generatedBy: "1.14.1"
--- ---
Propose a new change - create the change and generate all artifacts in one step. Propose a new change - create the change and generate all artifacts in one step.
.opencode/skills/openspec-sync-specs/SKILL.md
+1 -1
View File
@@ -7,7 +7,7 @@ compatibility: Requires openspec CLI.
metadata: metadata:
author: openspec author: openspec
version: "1.0" version: "1.0"
generatedBy: "1.14.0" generatedBy: "1.14.1"
--- ---
Sync delta specs from a change to main specs. Sync delta specs from a change to main specs.
.opencode/skills/openspec-update-change/SKILL.md
+1 -1
View File
@@ -7,7 +7,7 @@ compatibility: Requires openspec CLI.
metadata: metadata:
author: openspec author: openspec
version: "1.0" version: "1.0"
generatedBy: "1.14.0" generatedBy: "1.14.1"
--- ---
Revise a change's existing planning artifacts and keep them coherent. Never edit code. Revise a change's existing planning artifacts and keep them coherent. Never edit code.