Skip to content

Commit cda37bc

Browse files
ruibabyruibaby
committed
Add OPSX commands, OpenSpec skills and prompts
Add experimental OPSX workflow tooling and OpenSpec skill definitions. This commit introduces command docs for /opsx (apply, archive, explore, propose) under .claude, skill manifests for openspec apply/archive/explore/propose across .claude, .codex and .github, and related GitHub prompt files. Also adds openspec/config.yaml to configure the OpenSpec integration. These files provide the workflow guidance, CLI instruction handling, and agent skill metadata for proposing, exploring, implementing, and archiving changes.
1 parent 625d177 commit cda37bc

21 files changed

Lines changed: 3188 additions & 0 deletions

File tree

‎.claude/commands/opsx/apply.md‎

Lines changed: 152 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,152 @@
1+
---
2+
name: "OPSX: Apply"
3+
description: Implement tasks from an OpenSpec change (Experimental)
4+
category: Workflow
5+
tags: [workflow, artifacts, experimental]
6+
---
7+
8+
Implement tasks from an OpenSpec change.
9+
10+
**Input**: Optionally specify a change name (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
11+
12+
**Steps**
13+
14+
1. **Select the change**
15+
16+
If a name is provided, use it. Otherwise:
17+
- Infer from conversation context if the user mentioned a change
18+
- Auto-select if only one active change exists
19+
- If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
20+
21+
Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
22+
23+
2. **Check status to understand the schema**
24+
```bash
25+
openspec status --change "<name>" --json
26+
```
27+
Parse the JSON to understand:
28+
- `schemaName`: The workflow being used (e.g., "spec-driven")
29+
- Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
30+
31+
3. **Get apply instructions**
32+
33+
```bash
34+
openspec instructions apply --change "<name>" --json
35+
```
36+
37+
This returns:
38+
- `contextFiles`: artifact ID -> array of concrete file paths (varies by schema)
39+
- Progress (total, complete, remaining)
40+
- Task list with status
41+
- Dynamic instruction based on current state
42+
43+
**Handle states:**
44+
- If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx:continue`
45+
- If `state: "all_done"`: congratulate, suggest archive
46+
- Otherwise: proceed to implementation
47+
48+
4. **Read context files**
49+
50+
Read every file path listed under `contextFiles` from the apply instructions output.
51+
The files depend on the schema being used:
52+
- **spec-driven**: proposal, specs, design, tasks
53+
- Other schemas: follow the contextFiles from CLI output
54+
55+
5. **Show current progress**
56+
57+
Display:
58+
- Schema being used
59+
- Progress: "N/M tasks complete"
60+
- Remaining tasks overview
61+
- Dynamic instruction from CLI
62+
63+
6. **Implement tasks (loop until done or blocked)**
64+
65+
For each pending task:
66+
- Show which task is being worked on
67+
- Make the code changes required
68+
- Keep changes minimal and focused
69+
- Mark task complete in the tasks file: `- [ ]` → `- [x]`
70+
- Continue to next task
71+
72+
**Pause if:**
73+
- Task is unclear → ask for clarification
74+
- Implementation reveals a design issue → suggest updating artifacts
75+
- Error or blocker encountered → report and wait for guidance
76+
- User interrupts
77+
78+
7. **On completion or pause, show status**
79+
80+
Display:
81+
- Tasks completed this session
82+
- Overall progress: "N/M tasks complete"
83+
- If all done: suggest archive
84+
- If paused: explain why and wait for guidance
85+
86+
**Output During Implementation**
87+
88+
```
89+
## Implementing: <change-name> (schema: <schema-name>)
90+
91+
Working on task 3/7: <task description>
92+
[...implementation happening...]
93+
✓ Task complete
94+
95+
Working on task 4/7: <task description>
96+
[...implementation happening...]
97+
✓ Task complete
98+
```
99+
100+
**Output On Completion**
101+
102+
```
103+
## Implementation Complete
104+
105+
**Change:** <change-name>
106+
**Schema:** <schema-name>
107+
**Progress:** 7/7 tasks complete ✓
108+
109+
### Completed This Session
110+
- [x] Task 1
111+
- [x] Task 2
112+
...
113+
114+
All tasks complete! You can archive this change with `/opsx:archive`.
115+
```
116+
117+
**Output On Pause (Issue Encountered)**
118+
119+
```
120+
## Implementation Paused
121+
122+
**Change:** <change-name>
123+
**Schema:** <schema-name>
124+
**Progress:** 4/7 tasks complete
125+
126+
### Issue Encountered
127+
<description of the issue>
128+
129+
**Options:**
130+
1. <option 1>
131+
2. <option 2>
132+
3. Other approach
133+
134+
What would you like to do?
135+
```
136+
137+
**Guardrails**
138+
- Keep going through tasks until done or blocked
139+
- Always read context files before starting (from the apply instructions output)
140+
- If task is ambiguous, pause and ask before implementing
141+
- If implementation reveals issues, pause and suggest artifact updates
142+
- Keep code changes minimal and scoped to each task
143+
- Update task checkbox immediately after completing each task
144+
- Pause on errors, blockers, or unclear requirements - don't guess
145+
- Use contextFiles from CLI output, don't assume specific file names
146+
147+
**Fluid Workflow Integration**
148+
149+
This skill supports the "actions on a change" model:
150+
151+
- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
152+
- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly

‎.claude/commands/opsx/archive.md‎

Lines changed: 157 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,157 @@
1+
---
2+
name: "OPSX: Archive"
3+
description: Archive a completed change in the experimental workflow
4+
category: Workflow
5+
tags: [workflow, archive, experimental]
6+
---
7+
8+
Archive a completed change in the experimental workflow.
9+
10+
**Input**: Optionally specify a change name after `/opsx:archive` (e.g., `/opsx:archive add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
11+
12+
**Steps**
13+
14+
1. **If no change name provided, prompt for selection**
15+
16+
Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
17+
18+
Show only active changes (not already archived).
19+
Include the schema used for each change if available.
20+
21+
**IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
22+
23+
2. **Check artifact completion status**
24+
25+
Run `openspec status --change "<name>" --json` to check artifact completion.
26+
27+
Parse the JSON to understand:
28+
- `schemaName`: The workflow being used
29+
- `artifacts`: List of artifacts with their status (`done` or other)
30+
31+
**If any artifacts are not `done`:**
32+
- Display warning listing incomplete artifacts
33+
- Prompt user for confirmation to continue
34+
- Proceed if user confirms
35+
36+
3. **Check task completion status**
37+
38+
Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
39+
40+
Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
41+
42+
**If incomplete tasks found:**
43+
- Display warning showing count of incomplete tasks
44+
- Prompt user for confirmation to continue
45+
- Proceed if user confirms
46+
47+
**If no tasks file exists:** Proceed without task-related warning.
48+
49+
4. **Assess delta spec sync state**
50+
51+
Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
52+
53+
**If delta specs exist:**
54+
- Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
55+
- Determine what changes would be applied (adds, modifications, removals, renames)
56+
- Show a combined summary before prompting
57+
58+
**Prompt options:**
59+
- If changes needed: "Sync now (recommended)", "Archive without syncing"
60+
- If already synced: "Archive now", "Sync anyway", "Cancel"
61+
62+
If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
63+
64+
5. **Perform the archive**
65+
66+
Create the archive directory if it doesn't exist:
67+
```bash
68+
mkdir -p openspec/changes/archive
69+
```
70+
71+
Generate target name using current date: `YYYY-MM-DD-<change-name>`
72+
73+
**Check if target already exists:**
74+
- If yes: Fail with error, suggest renaming existing archive or using different date
75+
- If no: Move the change directory to archive
76+
77+
```bash
78+
mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
79+
```
80+
81+
6. **Display summary**
82+
83+
Show archive completion summary including:
84+
- Change name
85+
- Schema that was used
86+
- Archive location
87+
- Spec sync status (synced / sync skipped / no delta specs)
88+
- Note about any warnings (incomplete artifacts/tasks)
89+
90+
**Output On Success**
91+
92+
```
93+
## Archive Complete
94+
95+
**Change:** <change-name>
96+
**Schema:** <schema-name>
97+
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
98+
**Specs:** ✓ Synced to main specs
99+
100+
All artifacts complete. All tasks complete.
101+
```
102+
103+
**Output On Success (No Delta Specs)**
104+
105+
```
106+
## Archive Complete
107+
108+
**Change:** <change-name>
109+
**Schema:** <schema-name>
110+
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
111+
**Specs:** No delta specs
112+
113+
All artifacts complete. All tasks complete.
114+
```
115+
116+
**Output On Success With Warnings**
117+
118+
```
119+
## Archive Complete (with warnings)
120+
121+
**Change:** <change-name>
122+
**Schema:** <schema-name>
123+
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
124+
**Specs:** Sync skipped (user chose to skip)
125+
126+
**Warnings:**
127+
- Archived with 2 incomplete artifacts
128+
- Archived with 3 incomplete tasks
129+
- Delta spec sync was skipped (user chose to skip)
130+
131+
Review the archive if this was not intentional.
132+
```
133+
134+
**Output On Error (Archive Exists)**
135+
136+
```
137+
## Archive Failed
138+
139+
**Change:** <change-name>
140+
**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/
141+
142+
Target archive directory already exists.
143+
144+
**Options:**
145+
1. Rename the existing archive
146+
2. Delete the existing archive if it's a duplicate
147+
3. Wait until a different date to archive
148+
```
149+
150+
**Guardrails**
151+
- Always prompt for change selection if not provided
152+
- Use artifact graph (openspec status --json) for completion checking
153+
- Don't block archive on warnings - just inform and confirm
154+
- Preserve .openspec.yaml when moving to archive (it moves with the directory)
155+
- Show clear summary of what happened
156+
- If sync is requested, use the Skill tool to invoke `openspec-sync-specs` (agent-driven)
157+
- If delta specs exist, always run the sync assessment and show the combined summary before prompting

0 commit comments

Comments
 (0)