+++ /dev/null
----
-agent: build
-description: Implement an approved OpenSpec change and keep tasks in sync.
----
-
-<!-- OPENSPEC:START -->
-
-**Guardrails**
-
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-Track these steps as TODOs and complete them one by one.
-
-1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria.
-2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
-3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished.
-4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality.
-5. Reference `openspec list` or `openspec show <item>` when additional context is required.
-
-**Reference**
-
-- Use `openspec show <id> --json --deltas-only` if you need additional context from the proposal while implementing.
-<!-- OPENSPEC:END -->
+++ /dev/null
----
-description: Archive a deployed OpenSpec change and update specs.
----
-
-<ChangeId>
- $ARGUMENTS
-</ChangeId>
-<!-- OPENSPEC:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-
-**Steps**
-
-1. Determine the change ID to archive:
- - If this prompt already includes a specific change ID (for example inside a `<ChangeId>` block populated by slash-command arguments), use that value after trimming whitespace.
- - If the conversation references a change loosely (for example by title or summary), run `openspec list` to surface likely IDs, share the relevant candidates, and confirm which one the user intends.
- - Otherwise, review the conversation, run `openspec list`, and ask the user which change to archive; wait for a confirmed change ID before proceeding.
- - If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
-2. Validate the change ID by running `openspec list` (or `openspec show <id>`) and stop if the change is missing, already archived, or otherwise not ready to archive.
-3. Run `openspec archive <id> --yes` so the CLI moves the change and applies spec updates without prompts (use `--skip-specs` only for tooling-only work).
-4. Review the command output to confirm the target specs were updated and the change landed in `changes/archive/`.
-5. Validate with `openspec validate --strict --no-interactive` and inspect with `openspec show <id>` if anything looks off.
-
-**Reference**
-
-- Use `openspec list` to confirm change IDs before archiving.
-- Inspect refreshed specs with `openspec list --specs` and address any validation issues before handing off.
-<!-- OPENSPEC:END -->
+++ /dev/null
----
-agent: build
-description: Scaffold a new OpenSpec change and validate strictly.
----
-
-The user has requested the following change proposal. Use the openspec instructions to create their change proposal.
-<UserRequest>
-$ARGUMENTS
-</UserRequest>
-
-<!-- OPENSPEC:START -->
-
-**Guardrails**
-
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
-- Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
-- Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.
-
-**Steps**
-
-1. Review `openspec/project.md`, run `openspec list` and `openspec list --specs`, and inspect related code or docs (e.g., via `rg`/`ls`) to ground the proposal in current behaviour; note any gaps that require clarification.
-2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, and `design.md` (when needed) under `openspec/changes/<id>/`.
-3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
-4. Capture architectural reasoning in `design.md` when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
-5. Draft spec deltas in `changes/<id>/specs/<capability>/spec.md` (one folder per capability) using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement and cross-reference related capabilities when relevant.
-6. Draft `tasks.md` as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
-7. Validate with `openspec validate <id> --strict --no-interactive` and resolve every issue before sharing the proposal.
-
-**Reference**
-
-- Use `openspec show <id> --json --deltas-only` or `openspec show <spec> --type spec` to inspect details when validation fails.
-- Search existing requirements with `rg -n "Requirement:|Scenario:" openspec/specs` before writing new ones.
-- Explore the codebase with `rg <keyword>`, `ls`, or direct file reads so proposals align with current implementation realities.
-<!-- OPENSPEC:END -->
--- /dev/null
+---
+description: Implement tasks from an OpenSpec change (Experimental)
+---
+
+Implement tasks from an OpenSpec change.
+
+**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.
+
+**Steps**
+
+1. **Select the change**
+
+ If a name is provided, use it. Otherwise:
+ - Infer from conversation context if the user mentioned a change
+ - Auto-select if only one active change exists
+ - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+ Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
+
+2. **Check status to understand the schema**
+
+ ```bash
+ openspec status --change "<name>" --json
+ ```
+
+ Parse the JSON to understand:
+ - `schemaName`: The workflow being used (e.g., "spec-driven")
+ - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+ ```bash
+ openspec instructions apply --change "<name>" --json
+ ```
+
+ This returns:
+ - Context file paths (varies by schema)
+ - Progress (total, complete, remaining)
+ - Task list with status
+ - Dynamic instruction based on current state
+
+ **Handle states:**
+ - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx:continue`
+ - If `state: "all_done"`: congratulate, suggest archive
+ - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+ Read the files listed in `contextFiles` from the apply instructions output.
+ The files depend on the schema being used:
+ - **spec-driven**: proposal, specs, design, tasks
+ - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+ Display:
+ - Schema being used
+ - Progress: "N/M tasks complete"
+ - Remaining tasks overview
+ - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+ For each pending task:
+ - Show which task is being worked on
+ - Make the code changes required
+ - Keep changes minimal and focused
+ - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+ - Continue to next task
+
+ **Pause if:**
+ - Task is unclear → ask for clarification
+ - Implementation reveals a design issue → suggest updating artifacts
+ - Error or blocker encountered → report and wait for guidance
+ - User interrupts
+
+7. **On completion or pause, show status**
+
+ Display:
+ - Tasks completed this session
+ - Overall progress: "N/M tasks complete"
+ - If all done: suggest archive
+ - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! Ready to archive this change.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
--- /dev/null
+---
+description: Archive a completed change in the experimental workflow
+---
+
+Archive a completed change in the experimental workflow.
+
+**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.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+ Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+ Show only active changes (not already archived).
+ Include the schema used for each change if available.
+
+ **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+ Run `openspec status --change "<name>" --json` to check artifact completion.
+
+ Parse the JSON to understand:
+ - `schemaName`: The workflow being used
+ - `artifacts`: List of artifacts with their status (`done` or other)
+
+ **If any artifacts are not `done`:**
+ - Display warning listing incomplete artifacts
+ - Prompt user for confirmation to continue
+ - Proceed if user confirms
+
+3. **Check task completion status**
+
+ Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+ Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+ **If incomplete tasks found:**
+ - Display warning showing count of incomplete tasks
+ - Prompt user for confirmation to continue
+ - Proceed if user confirms
+
+ **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+ Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
+
+ **If delta specs exist:**
+ - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+ - Determine what changes would be applied (adds, modifications, removals, renames)
+ - Show a combined summary before prompting
+
+ **Prompt options:**
+ - 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.
+
+5. **Perform the archive**
+
+ Create the archive directory if it doesn't exist:
+
+ ```bash
+ mkdir -p openspec/changes/archive
+ ```
+
+ Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+ **Check if target already exists:**
+ - If yes: Fail with error, suggest renaming existing archive or using different date
+ - If no: Move the change directory to archive
+
+ ```bash
+ mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+ ```
+
+6. **Display summary**
+
+ Show archive completion summary including:
+ - Change name
+ - Schema that was used
+ - Archive location
+ - Spec sync status (synced / sync skipped / no delta specs)
+ - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success (No Delta Specs)**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** No delta specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success With Warnings**
+
+```
+## Archive Complete (with warnings)
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** Sync skipped (user chose to skip)
+
+**Warnings:**
+- Archived with 2 incomplete artifacts
+- Archived with 3 incomplete tasks
+- Delta spec sync was skipped (user chose to skip)
+
+Review the archive if this was not intentional.
+```
+
+**Output On Error (Archive Exists)**
+
+```
+## Archive Failed
+
+**Change:** <change-name>
+**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/
+
+Target archive directory already exists.
+
+**Options:**
+1. Rename the existing archive
+2. Delete the existing archive if it's a duplicate
+3. Wait until a different date to archive
+```
+
+**Guardrails**
+
+- Always prompt for change selection if not provided
+- Use artifact graph (openspec status --json) for completion checking
+- 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 delta specs exist, always run the sync assessment and show the combined summary before prompting
--- /dev/null
+---
+description: Archive multiple completed changes at once
+---
+
+Archive multiple completed changes in a single operation.
+
+This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented.
+
+**Input**: None required (prompts for selection)
+
+**Steps**
+
+1. **Get active changes**
+
+ Run `openspec list --json` to get all active changes.
+
+ If no active changes exist, inform user and stop.
+
+2. **Prompt for change selection**
+
+ Use **AskUserQuestion tool** with multi-select to let user choose changes:
+ - Show each change with its schema
+ - Include an option for "All changes"
+ - Allow any number of selections (1+ works, 2+ is the typical use case)
+
+ **IMPORTANT**: Do NOT auto-select. Always let the user choose.
+
+3. **Batch validation - gather status for all selected changes**
+
+ For each selected change, collect:
+
+ a. **Artifact status** - Run `openspec status --change "<name>" --json`
+ - Parse `schemaName` and `artifacts` list
+ - Note which artifacts are `done` vs other states
+
+ b. **Task completion** - Read `openspec/changes/<name>/tasks.md`
+ - Count `- [ ]` (incomplete) vs `- [x]` (complete)
+ - If no tasks file exists, note as "No tasks"
+
+ c. **Delta specs** - Check `openspec/changes/<name>/specs/` directory
+ - List which capability specs exist
+ - For each, extract requirement names (lines matching `### Requirement: <name>`)
+
+4. **Detect spec conflicts**
+
+ Build a map of `capability -> [changes that touch it]`:
+
+ ```
+ auth -> [change-a, change-b] <- CONFLICT (2+ changes)
+ api -> [change-c] <- OK (only 1 change)
+ ```
+
+ A conflict exists when 2+ selected changes have delta specs for the same capability.
+
+5. **Resolve conflicts agentically**
+
+ **For each conflict**, investigate the codebase:
+
+ a. **Read the delta specs** from each conflicting change to understand what each claims to add/modify
+
+ b. **Search the codebase** for implementation evidence:
+ - Look for code implementing requirements from each delta spec
+ - Check for related files, functions, or tests
+
+ c. **Determine resolution**:
+ - If only one change is actually implemented -> sync that one's specs
+ - If both implemented -> apply in chronological order (older first, newer overwrites)
+ - If neither implemented -> skip spec sync, warn user
+
+ d. **Record resolution** for each conflict:
+ - Which change's specs to apply
+ - In what order (if both)
+ - Rationale (what was found in codebase)
+
+6. **Show consolidated status table**
+
+ Display a table summarizing all changes:
+
+ ```
+ | Change | Artifacts | Tasks | Specs | Conflicts | Status |
+ |---------------------|-----------|-------|---------|-----------|--------|
+ | schema-management | Done | 5/5 | 2 delta | None | Ready |
+ | project-config | Done | 3/3 | 1 delta | None | Ready |
+ | add-oauth | Done | 4/4 | 1 delta | auth (!) | Ready* |
+ | add-verify-skill | 1 left | 2/5 | None | None | Warn |
+ ```
+
+ For conflicts, show the resolution:
+
+ ```
+ * Conflict resolution:
+ - auth spec: Will apply add-oauth then add-jwt (both implemented, chronological order)
+ ```
+
+ For incomplete changes, show warnings:
+
+ ```
+ Warnings:
+ - add-verify-skill: 1 incomplete artifact, 3 incomplete tasks
+ ```
+
+7. **Confirm batch operation**
+
+ Use **AskUserQuestion tool** with a single confirmation:
+ - "Archive N changes?" with options based on status
+ - Options might include:
+ - "Archive all N changes"
+ - "Archive only N ready changes (skip incomplete)"
+ - "Cancel"
+
+ If there are incomplete changes, make clear they'll be archived with warnings.
+
+8. **Execute archive for each confirmed change**
+
+ Process changes in the determined order (respecting conflict resolution):
+
+ a. **Sync specs** if delta specs exist:
+ - Use the openspec-sync-specs approach (agent-driven intelligent merge)
+ - For conflicts, apply in resolved order
+ - Track if sync was done
+
+ b. **Perform the archive**:
+
+ ```bash
+ mkdir -p openspec/changes/archive
+ mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+ ```
+
+ c. **Track outcome** for each change:
+ - Success: archived successfully
+ - Failed: error during archive (record error)
+ - Skipped: user chose not to archive (if applicable)
+
+9. **Display summary**
+
+ Show final results:
+
+ ```
+ ## Bulk Archive Complete
+
+ Archived 3 changes:
+ - schema-management-cli -> archive/2026-01-19-schema-management-cli/
+ - project-config -> archive/2026-01-19-project-config/
+ - add-oauth -> archive/2026-01-19-add-oauth/
+
+ Skipped 1 change:
+ - add-verify-skill (user chose not to archive incomplete)
+
+ Spec sync summary:
+ - 4 delta specs synced to main specs
+ - 1 conflict resolved (auth: applied both in chronological order)
+ ```
+
+ If any failures:
+
+ ```
+ Failed 1 change:
+ - some-change: Archive directory already exists
+ ```
+
+**Conflict Resolution Examples**
+
+Example 1: Only one implemented
+
+```
+Conflict: specs/auth/spec.md touched by [add-oauth, add-jwt]
+
+Checking add-oauth:
+- Delta adds "OAuth Provider Integration" requirement
+- Searching codebase... found src/auth/oauth.ts implementing OAuth flow
+
+Checking add-jwt:
+- Delta adds "JWT Token Handling" requirement
+- Searching codebase... no JWT implementation found
+
+Resolution: Only add-oauth is implemented. Will sync add-oauth specs only.
+```
+
+Example 2: Both implemented
+
+```
+Conflict: specs/api/spec.md touched by [add-rest-api, add-graphql]
+
+Checking add-rest-api (created 2026-01-10):
+- Delta adds "REST Endpoints" requirement
+- Searching codebase... found src/api/rest.ts
+
+Checking add-graphql (created 2026-01-15):
+- Delta adds "GraphQL Schema" requirement
+- Searching codebase... found src/api/graphql.ts
+
+Resolution: Both implemented. Will apply add-rest-api specs first,
+then add-graphql specs (chronological order, newer takes precedence).
+```
+
+**Output On Success**
+
+```
+## Bulk Archive Complete
+
+Archived N changes:
+- <change-1> -> archive/YYYY-MM-DD-<change-1>/
+- <change-2> -> archive/YYYY-MM-DD-<change-2>/
+
+Spec sync summary:
+- N delta specs synced to main specs
+- No conflicts (or: M conflicts resolved)
+```
+
+**Output On Partial Success**
+
+```
+## Bulk Archive Complete (partial)
+
+Archived N changes:
+- <change-1> -> archive/YYYY-MM-DD-<change-1>/
+
+Skipped M changes:
+- <change-2> (user chose not to archive incomplete)
+
+Failed K changes:
+- <change-3>: Archive directory already exists
+```
+
+**Output When No Changes**
+
+```
+## No Changes to Archive
+
+No active changes found. Use `/opsx:new` to create a new change.
+```
+
+**Guardrails**
+
+- Allow any number of changes (1+ is fine, 2+ is the typical use case)
+- Always prompt for selection, never auto-select
+- Detect spec conflicts early and resolve by checking codebase
+- When both changes are implemented, apply specs in chronological order
+- Skip spec sync only when implementation is missing (warn user)
+- Show clear per-change status before confirming
+- Use single confirmation for entire batch
+- Track and report all outcomes (success/skip/fail)
+- Preserve .openspec.yaml when moving to archive
+- Archive directory target uses current date: YYYY-MM-DD-<name>
+- If archive target exists, fail that change but continue with others
--- /dev/null
+---
+description: Continue working on a change - create the next artifact (Experimental)
+---
+
+Continue working on a change by creating the next artifact.
+
+**Input**: Optionally specify a change name after `/opsx:continue` (e.g., `/opsx:continue add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+ Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.
+
+ Present the top 3-4 most recently modified changes as options, showing:
+ - Change name
+ - Schema (from `schema` field if present, otherwise "spec-driven")
+ - Status (e.g., "0/5 tasks", "complete", "no tasks")
+ - How recently it was modified (from `lastModified` field)
+
+ Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to continue.
+
+ **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check current status**
+
+ ```bash
+ openspec status --change "<name>" --json
+ ```
+
+ Parse the JSON to understand current state. The response includes:
+ - `schemaName`: The workflow schema being used (e.g., "spec-driven")
+ - `artifacts`: Array of artifacts with their status ("done", "ready", "blocked")
+ - `isComplete`: Boolean indicating if all artifacts are complete
+
+3. **Act based on status**:
+
+ ***
+
+ **If all artifacts are complete (`isComplete: true`)**:
+ - Congratulate the user
+ - Show final status including the schema used
+ - Suggest: "All artifacts created! You can now implement this change or archive it."
+ - STOP
+
+ ***
+
+ **If artifacts are ready to create** (status shows artifacts with `status: "ready"`):
+ - Pick the FIRST artifact with `status: "ready"` from the status output
+ - Get its instructions:
+ ```bash
+ openspec instructions <artifact-id> --change "<name>" --json
+ ```
+ - Parse the JSON. The key fields are:
+ - `context`: Project background (constraints for you - do NOT include in output)
+ - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+ - `template`: The structure to use for your output file
+ - `instruction`: Schema-specific guidance
+ - `outputPath`: Where to write the artifact
+ - `dependencies`: Completed artifacts to read for context
+ - **Create the artifact file**:
+ - Read any completed dependency files for context
+ - Use `template` as the structure - fill in its sections
+ - Apply `context` and `rules` as constraints when writing - but do NOT copy them into the file
+ - Write to the output path specified in instructions
+ - Show what was created and what's now unlocked
+ - STOP after creating ONE artifact
+
+ ***
+
+ **If no artifacts are ready (all blocked)**:
+ - This shouldn't happen with a valid schema
+ - Show status and suggest checking for issues
+
+4. **After creating an artifact, show progress**
+ ```bash
+ openspec status --change "<name>"
+ ```
+
+**Output**
+
+After each invocation, show:
+
+- Which artifact was created
+- Schema workflow being used
+- Current progress (N/M complete)
+- What artifacts are now unlocked
+- Prompt: "Run `/opsx:continue` to create the next artifact"
+
+**Artifact Creation Guidelines**
+
+The artifact types and their purpose depend on the schema. Use the `instruction` field from the instructions output to understand what to create.
+
+Common artifact patterns:
+
+**spec-driven schema** (proposal → specs → design → tasks):
+
+- **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.
+ - The Capabilities section is critical - each capability listed will need a spec file.
+- **specs/<capability>/spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).
+- **design.md**: Document technical decisions, architecture, and implementation approach.
+- **tasks.md**: Break down implementation into checkboxed tasks.
+
+For other schemas, follow the `instruction` field from the CLI output.
+
+**Guardrails**
+
+- Create ONE artifact per invocation
+- Always read dependency artifacts before creating a new one
+- Never skip artifacts or create out of order
+- If context is unclear, ask the user before creating
+- Verify the artifact file exists after writing before marking progress
+- Use the schema's artifact sequence, don't assume specific artifact names
+- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
+ - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
+ - These guide what you write, but should never appear in the output
--- /dev/null
+---
+description: Enter explore mode - think through ideas, investigate problems, clarify requirements
+---
+
+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.
+
+**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.
+
+**Input**: The argument after `/opsx:explore` is whatever the user wants to think about. Could be:
+
+- A vague idea: "real-time collaboration"
+- A specific problem: "the auth system is getting unwieldy"
+- A change name: "add-dark-mode" (to explore in context of that change)
+- A comparison: "postgres vs sqlite for this"
+- Nothing (just enter explore mode)
+
+---
+
+## The Stance
+
+- **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script
+- **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
+- **Visual** - Use ASCII diagrams liberally when they'd help clarify thinking
+- **Adaptive** - Follow interesting threads, pivot when new information emerges
+- **Patient** - Don't rush to conclusions, let the shape of the problem emerge
+- **Grounded** - Explore the actual codebase when relevant, don't just theorize
+
+---
+
+## What You Might Do
+
+Depending on what the user brings, you might:
+
+**Explore the problem space**
+
+- Ask clarifying questions that emerge from what they said
+- Challenge assumptions
+- Reframe the problem
+- Find analogies
+
+**Investigate the codebase**
+
+- Map existing architecture relevant to the discussion
+- Find integration points
+- Identify patterns already in use
+- Surface hidden complexity
+
+**Compare options**
+
+- Brainstorm multiple approaches
+- Build comparison tables
+- Sketch tradeoffs
+- Recommend a path (if asked)
+
+**Visualize**
+
+```
+┌─────────────────────────────────────────┐
+│ Use ASCII diagrams liberally │
+├─────────────────────────────────────────┤
+│ │
+│ ┌────────┐ ┌────────┐ │
+│ │ State │────────▶│ State │ │
+│ │ A │ │ B │ │
+│ └────────┘ └────────┘ │
+│ │
+│ System diagrams, state machines, │
+│ data flows, architecture sketches, │
+│ dependency graphs, comparison tables │
+│ │
+└─────────────────────────────────────────┘
+```
+
+**Surface risks and unknowns**
+
+- Identify what could go wrong
+- Find gaps in understanding
+- Suggest spikes or investigations
+
+---
+
+## OpenSpec Awareness
+
+You have full context of the OpenSpec system. Use it naturally, don't force it.
+
+### Check for context
+
+At the start, quickly check what exists:
+
+```bash
+openspec list --json
+```
+
+This tells you:
+
+- If there are active changes
+- Their names, schemas, and status
+- What the user might be working on
+
+If the user mentioned a specific change name, read its artifacts for context.
+
+### When no change exists
+
+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`
+- Or keep exploring - no pressure to formalize
+
+### When a change exists
+
+If the user mentions a change or you detect one is relevant:
+
+1. **Read existing artifacts for context**
+ - `openspec/changes/<name>/proposal.md`
+ - `openspec/changes/<name>/design.md`
+ - `openspec/changes/<name>/tasks.md`
+ - etc.
+
+2. **Reference them naturally in conversation**
+ - "Your design mentions using Redis, but we just realized SQLite fits better..."
+ - "The proposal scopes this to premium users, but we're now thinking everyone..."
+
+3. **Offer to capture when decisions are made**
+
+ | Insight Type | Where to Capture |
+ | -------------------------- | ---------------------------- |
+ | New requirement discovered | `specs/<capability>/spec.md` |
+ | Requirement changed | `specs/<capability>/spec.md` |
+ | Design decision made | `design.md` |
+ | Scope changed | `proposal.md` |
+ | New work identified | `tasks.md` |
+ | Assumption invalidated | Relevant artifact |
+
+ Example offers:
+ - "That's a design decision. Capture it in design.md?"
+ - "This is a new requirement. Add it to specs?"
+ - "This changes scope. Update the proposal?"
+
+4. **The user decides** - Offer and move on. Don't pressure. Don't auto-capture.
+
+---
+
+## What You Don't Have To Do
+
+- Follow a script
+- Ask the same questions every time
+- Produce a specific artifact
+- Reach a conclusion
+- Stay on topic if a tangent is valuable
+- Be brief (this is thinking time)
+
+---
+
+## Ending Discovery
+
+There's no required ending. Discovery might:
+
+- **Flow into action**: "Ready to start? `/opsx:new` or `/opsx:ff`"
+- **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"
+
+When things crystallize, you might offer a summary - but it's optional. Sometimes the thinking IS the value.
+
+---
+
+## Guardrails
+
+- **Don't implement** - Never write code or implement features. Creating OpenSpec artifacts is fine, writing application code is not.
+- **Don't fake understanding** - If something is unclear, dig deeper
+- **Don't rush** - Discovery is thinking time, not task time
+- **Don't force structure** - Let patterns emerge naturally
+- **Don't auto-capture** - Offer to save insights, don't just do it
+- **Do visualize** - A good diagram is worth many paragraphs
+- **Do explore the codebase** - Ground discussions in reality
+- **Do question assumptions** - Including the user's and your own
--- /dev/null
+---
+description: Create a change and generate all artifacts needed for implementation in one go
+---
+
+Fast-forward through artifact creation - generate everything needed to start implementation.
+
+**Input**: The argument after `/opsx:ff` is the change name (kebab-case), OR a description of what the user wants to build.
+
+**Steps**
+
+1. **If no input provided, ask what they want to build**
+
+ Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+
+ > "What change do you want to work on? Describe what you want to build or fix."
+
+ From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+ **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Create the change directory**
+
+ ```bash
+ openspec new change "<name>"
+ ```
+
+ This creates a scaffolded change at `openspec/changes/<name>/`.
+
+3. **Get the artifact build order**
+
+ ```bash
+ openspec status --change "<name>" --json
+ ```
+
+ Parse the JSON to get:
+ - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`)
+ - `artifacts`: list of all artifacts with their status and dependencies
+
+4. **Create artifacts in sequence until apply-ready**
+
+ Use the **TodoWrite tool** to track progress through the artifacts.
+
+ Loop through artifacts in dependency order (artifacts with no pending dependencies first):
+
+ a. **For each artifact that is `ready` (dependencies satisfied)**:
+ - Get instructions:
+ ```bash
+ openspec instructions <artifact-id> --change "<name>" --json
+ ```
+ - The instructions JSON includes:
+ - `context`: Project background (constraints for you - do NOT include in output)
+ - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+ - `template`: The structure to use for your output file
+ - `instruction`: Schema-specific guidance for this artifact type
+ - `outputPath`: Where to write the artifact
+ - `dependencies`: Completed artifacts to read for context
+ - Read any completed dependency files for context
+ - Create the artifact file using `template` as the structure
+ - Apply `context` and `rules` as constraints - but do NOT copy them into the file
+ - Show brief progress: "✓ Created <artifact-id>"
+
+ b. **Continue until all `applyRequires` artifacts are complete**
+ - After creating each artifact, re-run `openspec status --change "<name>" --json`
+ - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array
+ - Stop when all `applyRequires` artifacts are done
+
+ c. **If an artifact requires user input** (unclear context):
+ - Use **AskUserQuestion tool** to clarify
+ - Then continue with creation
+
+5. **Show final status**
+ ```bash
+ openspec status --change "<name>"
+ ```
+
+**Output**
+
+After completing all artifacts, summarize:
+
+- Change name and location
+- List of artifacts created with brief descriptions
+- What's ready: "All artifacts created! Ready for implementation."
+- Prompt: "Run `/opsx:apply` to start implementing."
+
+**Artifact Creation Guidelines**
+
+- 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
+
+**Guardrails**
+
+- Create ALL artifacts needed for implementation (as defined by schema's `apply.requires`)
+- Always read dependency artifacts before creating a new one
+- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
+- If a change with that name already exists, ask if user wants to continue it or create a new one
+- Verify each artifact file exists after writing before proceeding to next
--- /dev/null
+---
+description: Start a new change using the experimental artifact workflow (OPSX)
+---
+
+Start a new change using the experimental artifact-driven approach.
+
+**Input**: The argument after `/opsx:new` is the change name (kebab-case), OR a description of what the user wants to build.
+
+**Steps**
+
+1. **If no input provided, ask what they want to build**
+
+ Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+
+ > "What change do you want to work on? Describe what you want to build or fix."
+
+ From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+ **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Determine the workflow schema**
+
+ Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.
+
+ **Use a different schema only if the user mentions:**
+ - A specific schema name → use `--schema <name>`
+ - "show workflows" or "what workflows" → run `openspec schemas --json` and let them choose
+
+ **Otherwise**: Omit `--schema` to use the default.
+
+3. **Create the change directory**
+
+ ```bash
+ openspec new change "<name>"
+ ```
+
+ Add `--schema <name>` only if the user requested a specific workflow.
+ This creates a scaffolded change at `openspec/changes/<name>/` with the selected schema.
+
+4. **Show the artifact status**
+
+ ```bash
+ openspec status --change "<name>"
+ ```
+
+ This shows which artifacts need to be created and which are ready (dependencies satisfied).
+
+5. **Get instructions for the first artifact**
+ The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
+
+ ```bash
+ openspec instructions <first-artifact-id> --change "<name>"
+ ```
+
+ This outputs the template and context for creating the first artifact.
+
+6. **STOP and wait for user direction**
+
+**Output**
+
+After completing the steps, summarize:
+
+- Change name and location
+- Schema/workflow being used and its artifact sequence
+- Current status (0/N artifacts complete)
+- The template for the first artifact
+- Prompt: "Ready to create the first artifact? Run `/opsx:continue` or just describe what this change is about and I'll draft it."
+
+**Guardrails**
+
+- Do NOT create any artifacts yet - just show the instructions
+- Do NOT advance beyond showing the first artifact template
+- If the name is invalid (not kebab-case), ask for a valid name
+- If a change with that name already exists, suggest using `/opsx:continue` instead
+- Pass --schema if using a non-default workflow
--- /dev/null
+---
+description: Guided onboarding - walk through a complete OpenSpec workflow cycle with narration
+---
+
+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.
+
+---
+
+## Preflight
+
+Before starting, check if OpenSpec is initialized:
+
+```bash
+openspec status --json 2>&1 || echo "NOT_INITIALIZED"
+```
+
+**If not initialized:**
+
+> OpenSpec isn't set up in this project yet. Run `openspec init` first, then come back to `/opsx:onboard`.
+
+Stop here if not initialized.
+
+---
+
+## Phase 1: Welcome
+
+Display:
+
+```
+## Welcome to OpenSpec!
+
+I'll walk you through a complete change cycle—from idea to implementation—using a real task in your codebase. Along the way, you'll learn the workflow by doing it.
+
+**What we'll do:**
+1. Pick a small, real task in your codebase
+2. Explore the problem briefly
+3. Create a change (the container for our work)
+4. Build the artifacts: proposal → specs → design → tasks
+5. Implement the tasks
+6. Archive the completed change
+
+**Time:** ~15-20 minutes
+
+Let's start by finding something to work on.
+```
+
+---
+
+## Phase 2: Task Selection
+
+### Codebase Analysis
+
+Scan the codebase for small improvement opportunities. Look for:
+
+1. **TODO/FIXME comments** - Search for `TODO`, `FIXME`, `HACK`, `XXX` in code files
+2. **Missing error handling** - `catch` blocks that swallow errors, risky operations without try-catch
+3. **Functions without tests** - Cross-reference `src/` with test directories
+4. **Type issues** - `any` types in TypeScript files (`: any`, `as any`)
+5. **Debug artifacts** - `console.log`, `console.debug`, `debugger` statements in non-debug code
+6. **Missing validation** - User input handlers without validation
+
+Also check recent git activity:
+
+```bash
+git log --oneline -10 2>/dev/null || echo "No git history"
+```
+
+### Present Suggestions
+
+From your analysis, present 3-4 specific suggestions:
+
+```
+## Task Suggestions
+
+Based on scanning your codebase, here are some good starter tasks:
+
+**1. [Most promising task]**
+ Location: `src/path/to/file.ts:42`
+ Scope: ~1-2 files, ~20-30 lines
+ Why it's good: [brief reason]
+
+**2. [Second task]**
+ Location: `src/another/file.ts`
+ Scope: ~1 file, ~15 lines
+ Why it's good: [brief reason]
+
+**3. [Third task]**
+ Location: [location]
+ Scope: [estimate]
+ Why it's good: [brief reason]
+
+**4. Something else?**
+ Tell me what you'd like to work on.
+
+Which task interests you? (Pick a number or describe your own)
+```
+
+**If nothing found:** Fall back to asking what the user wants to build:
+
+> I didn't find obvious quick wins in your codebase. What's something small you've been meaning to add or fix?
+
+### Scope Guardrail
+
+If the user picks or describes something too large (major feature, multi-day work):
+
+```
+That's a valuable task, but it's probably larger than ideal for your first OpenSpec run-through.
+
+For learning the workflow, smaller is better—it lets you see the full cycle without getting stuck in implementation details.
+
+**Options:**
+1. **Slice it smaller** - What's the smallest useful piece of [their task]? Maybe just [specific slice]?
+2. **Pick something else** - One of the other suggestions, or a different small task?
+3. **Do it anyway** - If you really want to tackle this, we can. Just know it'll take longer.
+
+What would you prefer?
+```
+
+Let the user override if they insist—this is a soft guardrail.
+
+---
+
+## Phase 3: Explore Demo
+
+Once a task is selected, briefly demonstrate explore mode:
+
+```
+Before we create a change, let me quickly show you **explore mode**—it's how you think through problems before committing to a direction.
+```
+
+Spend 1-2 minutes investigating the relevant code:
+
+- Read the file(s) involved
+- Draw a quick ASCII diagram if it helps
+- Note any considerations
+
+```
+## Quick Exploration
+
+[Your brief analysis—what you found, any considerations]
+
+┌─────────────────────────────────────────┐
+│ [Optional: ASCII diagram if helpful] │
+└─────────────────────────────────────────┘
+
+Explore mode (`/opsx:explore`) is for this kind of thinking—investigating before implementing. You can use it anytime you need to think through a problem.
+
+Now let's create a change to hold our work.
+```
+
+**PAUSE** - Wait for user acknowledgment before proceeding.
+
+---
+
+## Phase 4: Create the Change
+
+**EXPLAIN:**
+
+```
+## Creating a Change
+
+A "change" in OpenSpec is a container for all the thinking and planning around a piece of work. It lives in `openspec/changes/<name>/` and holds your artifacts—proposal, specs, design, tasks.
+
+Let me create one for our task.
+```
+
+**DO:** Create the change with a derived kebab-case name:
+
+```bash
+openspec new change "<derived-name>"
+```
+
+**SHOW:**
+
+```
+Created: `openspec/changes/<name>/`
+
+The folder structure:
+```
+
+openspec/changes/<name>/
+├── proposal.md ← Why we're doing this (empty, we'll fill it)
+├── design.md ← How we'll build it (empty)
+├── specs/ ← Detailed requirements (empty)
+└── tasks.md ← Implementation checklist (empty)
+
+```
+
+Now let's fill in the first artifact—the proposal.
+```
+
+---
+
+## Phase 5: Proposal
+
+**EXPLAIN:**
+
+```
+## The Proposal
+
+The proposal captures **why** we're making this change and **what** it involves at a high level. It's the "elevator pitch" for the work.
+
+I'll draft one based on our task.
+```
+
+**DO:** Draft the proposal content (don't save yet):
+
+```
+Here's a draft proposal:
+
+---
+
+## Why
+
+[1-2 sentences explaining the problem/opportunity]
+
+## What Changes
+
+[Bullet points of what will be different]
+
+## Capabilities
+
+### New Capabilities
+- `<capability-name>`: [brief description]
+
+### Modified Capabilities
+<!-- If modifying existing behavior -->
+
+## Impact
+
+- `src/path/to/file.ts`: [what changes]
+- [other files if applicable]
+
+---
+
+Does this capture the intent? I can adjust before we save it.
+```
+
+**PAUSE** - Wait for user approval/feedback.
+
+After approval, save the proposal:
+
+```bash
+openspec instructions proposal --change "<name>" --json
+```
+
+Then write the content to `openspec/changes/<name>/proposal.md`.
+
+```
+Proposal saved. This is your "why" document—you can always come back and refine it as understanding evolves.
+
+Next up: specs.
+```
+
+---
+
+## Phase 6: Specs
+
+**EXPLAIN:**
+
+```
+## Specs
+
+Specs define **what** we're building in precise, testable terms. They use a requirement/scenario format that makes expected behavior crystal clear.
+
+For a small task like this, we might only need one spec file.
+```
+
+**DO:** Create the spec file:
+
+```bash
+mkdir -p openspec/changes/<name>/specs/<capability-name>
+```
+
+Draft the spec content:
+
+```
+Here's the spec:
+
+---
+
+## ADDED Requirements
+
+### Requirement: <Name>
+
+<Description of what the system should do>
+
+#### Scenario: <Scenario name>
+
+- **WHEN** <trigger condition>
+- **THEN** <expected outcome>
+- **AND** <additional outcome if needed>
+
+---
+
+This format—WHEN/THEN/AND—makes requirements testable. You can literally read them as test cases.
+```
+
+Save to `openspec/changes/<name>/specs/<capability>/spec.md`.
+
+---
+
+## Phase 7: Design
+
+**EXPLAIN:**
+
+```
+## Design
+
+The design captures **how** we'll build it—technical decisions, tradeoffs, approach.
+
+For small changes, this might be brief. That's fine—not every change needs deep design discussion.
+```
+
+**DO:** Draft design.md:
+
+```
+Here's the design:
+
+---
+
+## Context
+
+[Brief context about the current state]
+
+## Goals / Non-Goals
+
+**Goals:**
+- [What we're trying to achieve]
+
+**Non-Goals:**
+- [What's explicitly out of scope]
+
+## Decisions
+
+### Decision 1: [Key decision]
+
+[Explanation of approach and rationale]
+
+---
+
+For a small task, this captures the key decisions without over-engineering.
+```
+
+Save to `openspec/changes/<name>/design.md`.
+
+---
+
+## Phase 8: Tasks
+
+**EXPLAIN:**
+
+```
+## Tasks
+
+Finally, we break the work into implementation tasks—checkboxes that drive the apply phase.
+
+These should be small, clear, and in logical order.
+```
+
+**DO:** Generate tasks based on specs and design:
+
+```
+Here are the implementation tasks:
+
+---
+
+## 1. [Category or file]
+
+- [ ] 1.1 [Specific task]
+- [ ] 1.2 [Specific task]
+
+## 2. Verify
+
+- [ ] 2.1 [Verification step]
+
+---
+
+Each checkbox becomes a unit of work in the apply phase. Ready to implement?
+```
+
+**PAUSE** - Wait for user to confirm they're ready to implement.
+
+Save to `openspec/changes/<name>/tasks.md`.
+
+---
+
+## Phase 9: Apply (Implementation)
+
+**EXPLAIN:**
+
+```
+## Implementation
+
+Now we implement each task, checking them off as we go. I'll announce each one and occasionally note how the specs/design informed the approach.
+```
+
+**DO:** For each task:
+
+1. Announce: "Working on task N: [description]"
+2. Implement the change in the codebase
+3. Reference specs/design naturally: "The spec says X, so I'm doing Y"
+4. Mark complete in tasks.md: `- [ ]` → `- [x]`
+5. Brief status: "✓ Task N complete"
+
+Keep narration light—don't over-explain every line of code.
+
+After all tasks:
+
+```
+## Implementation Complete
+
+All tasks done:
+- [x] Task 1
+- [x] Task 2
+- [x] ...
+
+The change is implemented! One more step—let's archive it.
+```
+
+---
+
+## Phase 10: Archive
+
+**EXPLAIN:**
+
+```
+## Archiving
+
+When a change is complete, we archive it. This moves it from `openspec/changes/` to `openspec/changes/archive/YYYY-MM-DD-<name>/`.
+
+Archived changes become your project's decision history—you can always find them later to understand why something was built a certain way.
+```
+
+**DO:**
+
+```bash
+openspec archive "<name>"
+```
+
+**SHOW:**
+
+```
+Archived to: `openspec/changes/archive/YYYY-MM-DD-<name>/`
+
+The change is now part of your project's history. The code is in your codebase, the decision record is preserved.
+```
+
+---
+
+## Phase 11: Recap & Next Steps
+
+```
+## Congratulations!
+
+You just completed a full OpenSpec cycle:
+
+1. **Explore** - Thought through the problem
+2. **New** - Created a change container
+3. **Proposal** - Captured WHY
+4. **Specs** - Defined WHAT in detail
+5. **Design** - Decided HOW
+6. **Tasks** - Broke it into steps
+7. **Apply** - Implemented the work
+8. **Archive** - Preserved the record
+
+This same rhythm works for any size change—a small fix or a major feature.
+
+---
+
+## Command Reference
+
+| Command | What it does |
+|---------|--------------|
+| `/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 |
+
+---
+
+## What's Next?
+
+Try `/opsx:new` or `/opsx:ff` on something you actually want to build. You've got the rhythm now!
+```
+
+---
+
+## Graceful Exit Handling
+
+### User wants to stop mid-way
+
+If the user says they need to stop, want to pause, or seem disengaged:
+
+```
+No problem! Your change is saved at `openspec/changes/<name>/`.
+
+To pick up where we left off later:
+- `/opsx:continue <name>` - Resume artifact creation
+- `/opsx:apply <name>` - Jump to implementation (if tasks exist)
+
+The work won't be lost. Come back whenever you're ready.
+```
+
+Exit gracefully without pressure.
+
+### User just wants command reference
+
+If the user says they just want to see the commands or skip the tutorial:
+
+```
+## OpenSpec Quick Reference
+
+| Command | What it does |
+|---------|--------------|
+| `/opsx:explore` | Think through problems (no code changes) |
+| `/opsx:new <name>` | Start a new change, step by step |
+| `/opsx:ff <name>` | Fast-forward: all artifacts at once |
+| `/opsx:continue <name>` | Continue an existing change |
+| `/opsx:apply <name>` | Implement tasks |
+| `/opsx:verify <name>` | Verify implementation |
+| `/opsx:archive <name>` | Archive when done |
+
+Try `/opsx:new` to start your first change, or `/opsx:ff` if you want to move fast.
+```
+
+Exit gracefully.
+
+---
+
+## Guardrails
+
+- **Follow the EXPLAIN → DO → SHOW → PAUSE pattern** at key transitions (after explore, after proposal draft, after tasks, after archive)
+- **Keep narration light** during implementation—teach without lecturing
+- **Don't skip phases** even if the change is small—the goal is teaching the workflow
+- **Pause for acknowledgment** at marked points, but don't over-pause
+- **Handle exits gracefully**—never pressure the user to continue
+- **Use real codebase tasks**—don't simulate or use fake examples
+- **Adjust scope gently**—guide toward smaller tasks but respect user choice
--- /dev/null
+---
+description: Sync delta specs from a change to main specs
+---
+
+Sync delta specs from a change to main specs.
+
+This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
+
+**Input**: Optionally specify a change name after `/opsx:sync` (e.g., `/opsx:sync add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+ Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+ Show changes that have delta specs (under `specs/` directory).
+
+ **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Find delta specs**
+
+ Look for delta spec files in `openspec/changes/<name>/specs/*/spec.md`.
+
+ Each delta spec file contains sections like:
+ - `## ADDED Requirements` - New requirements to add
+ - `## MODIFIED Requirements` - Changes to existing requirements
+ - `## REMOVED Requirements` - Requirements to remove
+ - `## RENAMED Requirements` - Requirements to rename (FROM:/TO: format)
+
+ If no delta specs found, inform user and stop.
+
+3. **For each delta spec, apply changes to main specs**
+
+ For each capability with a delta spec at `openspec/changes/<name>/specs/<capability>/spec.md`:
+
+ a. **Read the delta spec** to understand the intended changes
+
+ b. **Read the main spec** at `openspec/specs/<capability>/spec.md` (may not exist yet)
+
+ c. **Apply changes intelligently**:
+
+ **ADDED Requirements:**
+ - If requirement doesn't exist in main spec → add it
+ - If requirement already exists → update it to match (treat as implicit MODIFIED)
+
+ **MODIFIED Requirements:**
+ - Find the requirement in main spec
+ - Apply the changes - this can be:
+ - Adding new scenarios (don't need to copy existing ones)
+ - Modifying existing scenarios
+ - Changing the requirement description
+ - Preserve scenarios/content not mentioned in the delta
+
+ **REMOVED Requirements:**
+ - Remove the entire requirement block from main spec
+
+ **RENAMED Requirements:**
+ - Find the FROM requirement, rename to TO
+
+ d. **Create new main spec** if capability doesn't exist yet:
+ - Create `openspec/specs/<capability>/spec.md`
+ - Add Purpose section (can be brief, mark as TBD)
+ - Add Requirements section with the ADDED requirements
+
+4. **Show summary**
+
+ After applying all changes, summarize:
+ - Which capabilities were updated
+ - What changes were made (requirements added/modified/removed/renamed)
+
+**Delta Spec Format Reference**
+
+```markdown
+## ADDED Requirements
+
+### Requirement: New Feature
+
+The system SHALL do something new.
+
+#### Scenario: Basic case
+
+- **WHEN** user does X
+- **THEN** system does Y
+
+## MODIFIED Requirements
+
+### Requirement: Existing Feature
+
+#### Scenario: New scenario to add
+
+- **WHEN** user does A
+- **THEN** system does B
+
+## REMOVED Requirements
+
+### Requirement: Deprecated Feature
+
+## RENAMED Requirements
+
+- FROM: `### Requirement: Old Name`
+- TO: `### Requirement: New Name`
+```
+
+**Key Principle: Intelligent Merging**
+
+Unlike programmatic merging, you can apply **partial updates**:
+
+- To add a scenario, just include that scenario under MODIFIED - don't copy existing scenarios
+- The delta represents _intent_, not a wholesale replacement
+- Use your judgment to merge changes sensibly
+
+**Output On Success**
+
+```
+## Specs Synced: <change-name>
+
+Updated main specs:
+
+**<capability-1>**:
+- Added requirement: "New Feature"
+- Modified requirement: "Existing Feature" (added 1 scenario)
+
+**<capability-2>**:
+- Created new spec file
+- Added requirement: "Another Feature"
+
+Main specs are now updated. The change remains active - archive when implementation is complete.
+```
+
+**Guardrails**
+
+- Read both delta and main specs before making changes
+- Preserve existing content not mentioned in delta
+- If something is unclear, ask for clarification
+- Show what you're changing as you go
+- The operation should be idempotent - running twice should give same result
--- /dev/null
+---
+description: Verify implementation matches change artifacts before archiving
+---
+
+Verify that an implementation matches the change artifacts (specs, tasks, design).
+
+**Input**: Optionally specify a change name after `/opsx:verify` (e.g., `/opsx:verify add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+ Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+ Show changes that have implementation tasks (tasks artifact exists).
+ Include the schema used for each change if available.
+ Mark changes with incomplete tasks as "(In Progress)".
+
+ **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check status to understand the schema**
+
+ ```bash
+ openspec status --change "<name>" --json
+ ```
+
+ Parse the JSON to understand:
+ - `schemaName`: The workflow being used (e.g., "spec-driven")
+ - Which artifacts exist for this change
+
+3. **Get the change directory and load artifacts**
+
+ ```bash
+ openspec instructions apply --change "<name>" --json
+ ```
+
+ This returns the change directory and context files. Read all available artifacts from `contextFiles`.
+
+4. **Initialize verification report structure**
+
+ Create a report structure with three dimensions:
+ - **Completeness**: Track tasks and spec coverage
+ - **Correctness**: Track requirement implementation and scenario coverage
+ - **Coherence**: Track design adherence and pattern consistency
+
+ Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
+
+5. **Verify Completeness**
+
+ **Task Completion**:
+ - If tasks.md exists in contextFiles, read it
+ - Parse checkboxes: `- [ ]` (incomplete) vs `- [x]` (complete)
+ - Count complete vs total tasks
+ - If incomplete tasks exist:
+ - Add CRITICAL issue for each incomplete task
+ - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
+
+ **Spec Coverage**:
+ - If delta specs exist in `openspec/changes/<name>/specs/`:
+ - Extract all requirements (marked with "### Requirement:")
+ - For each requirement:
+ - Search codebase for keywords related to the requirement
+ - Assess if implementation likely exists
+ - If requirements appear unimplemented:
+ - Add CRITICAL issue: "Requirement not found: <requirement name>"
+ - Recommendation: "Implement requirement X: <description>"
+
+6. **Verify Correctness**
+
+ **Requirement Implementation Mapping**:
+ - For each requirement from delta specs:
+ - Search codebase for implementation evidence
+ - If found, note file paths and line ranges
+ - Assess if implementation matches requirement intent
+ - If divergence detected:
+ - Add WARNING: "Implementation may diverge from spec: <details>"
+ - Recommendation: "Review <file>:<lines> against requirement X"
+
+ **Scenario Coverage**:
+ - For each scenario in delta specs (marked with "#### Scenario:"):
+ - Check if conditions are handled in code
+ - Check if tests exist covering the scenario
+ - If scenario appears uncovered:
+ - Add WARNING: "Scenario not covered: <scenario name>"
+ - Recommendation: "Add test or implementation for scenario: <description>"
+
+7. **Verify Coherence**
+
+ **Design Adherence**:
+ - If design.md exists in contextFiles:
+ - Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
+ - Verify implementation follows those decisions
+ - If contradiction detected:
+ - Add WARNING: "Design decision not followed: <decision>"
+ - Recommendation: "Update implementation or revise design.md to match reality"
+ - If no design.md: Skip design adherence check, note "No design.md to verify against"
+
+ **Code Pattern Consistency**:
+ - Review new code for consistency with project patterns
+ - Check file naming, directory structure, coding style
+ - If significant deviations found:
+ - Add SUGGESTION: "Code pattern deviation: <details>"
+ - Recommendation: "Consider following project pattern: <example>"
+
+8. **Generate Verification Report**
+
+ **Summary Scorecard**:
+
+ ```
+ ## Verification Report: <change-name>
+
+ ### Summary
+ | Dimension | Status |
+ |--------------|------------------|
+ | Completeness | X/Y tasks, N reqs|
+ | Correctness | M/N reqs covered |
+ | Coherence | Followed/Issues |
+ ```
+
+ **Issues by Priority**:
+ 1. **CRITICAL** (Must fix before archive):
+ - Incomplete tasks
+ - Missing requirement implementations
+ - Each with specific, actionable recommendation
+
+ 2. **WARNING** (Should fix):
+ - Spec/design divergences
+ - Missing scenario coverage
+ - Each with specific recommendation
+
+ 3. **SUGGESTION** (Nice to fix):
+ - Pattern inconsistencies
+ - Minor improvements
+ - Each with specific recommendation
+
+ **Final Assessment**:
+ - If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
+ - If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
+ - If all clear: "All checks passed. Ready for archive."
+
+**Verification Heuristics**
+
+- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)
+- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
+- **Coherence**: Look for glaring inconsistencies, don't nitpick style
+- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
+- **Actionability**: Every issue must have a specific recommendation with file/line references where applicable
+
+**Graceful Degradation**
+
+- If only tasks.md exists: verify task completion only, skip spec/design checks
+- If tasks + specs exist: verify completeness and correctness, skip design
+- If full artifacts: verify all three dimensions
+- Always note which checks were skipped and why
+
+**Output Format**
+
+Use clear markdown with:
+
+- Table for summary scorecard
+- Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
+- Code references in format: `file.ts:123`
+- Specific, actionable recommendations
+- No vague suggestions like "consider reviewing"
--- /dev/null
+---
+name: openspec-apply-change
+description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+Implement tasks from an OpenSpec change.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+ If a name is provided, use it. Otherwise:
+ - Infer from conversation context if the user mentioned a change
+ - Auto-select if only one active change exists
+ - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+ Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
+
+2. **Check status to understand the schema**
+
+ ```bash
+ openspec status --change "<name>" --json
+ ```
+
+ Parse the JSON to understand:
+ - `schemaName`: The workflow being used (e.g., "spec-driven")
+ - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+ ```bash
+ openspec instructions apply --change "<name>" --json
+ ```
+
+ This returns:
+ - Context file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
+ - Progress (total, complete, remaining)
+ - Task list with status
+ - Dynamic instruction based on current state
+
+ **Handle states:**
+ - If `state: "blocked"` (missing artifacts): show message, suggest using openspec-continue-change
+ - If `state: "all_done"`: congratulate, suggest archive
+ - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+ Read the files listed in `contextFiles` from the apply instructions output.
+ The files depend on the schema being used:
+ - **spec-driven**: proposal, specs, design, tasks
+ - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+ Display:
+ - Schema being used
+ - Progress: "N/M tasks complete"
+ - Remaining tasks overview
+ - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+ For each pending task:
+ - Show which task is being worked on
+ - Make the code changes required
+ - Keep changes minimal and focused
+ - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+ - Continue to next task
+
+ **Pause if:**
+ - Task is unclear → ask for clarification
+ - Implementation reveals a design issue → suggest updating artifacts
+ - Error or blocker encountered → report and wait for guidance
+ - User interrupts
+
+7. **On completion or pause, show status**
+
+ Display:
+ - Tasks completed this session
+ - Overall progress: "N/M tasks complete"
+ - If all done: suggest archive
+ - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! Ready to archive this change.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
--- /dev/null
+---
+name: openspec-archive-change
+description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+Archive a completed change in the experimental workflow.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+ Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+ Show only active changes (not already archived).
+ Include the schema used for each change if available.
+
+ **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+ Run `openspec status --change "<name>" --json` to check artifact completion.
+
+ Parse the JSON to understand:
+ - `schemaName`: The workflow being used
+ - `artifacts`: List of artifacts with their status (`done` or other)
+
+ **If any artifacts are not `done`:**
+ - Display warning listing incomplete artifacts
+ - Use **AskUserQuestion tool** to confirm user wants to proceed
+ - Proceed if user confirms
+
+3. **Check task completion status**
+
+ Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+ Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+ **If incomplete tasks found:**
+ - Display warning showing count of incomplete tasks
+ - Use **AskUserQuestion tool** to confirm user wants to proceed
+ - Proceed if user confirms
+
+ **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+ Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
+
+ **If delta specs exist:**
+ - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+ - Determine what changes would be applied (adds, modifications, removals, renames)
+ - Show a combined summary before prompting
+
+ **Prompt options:**
+ - 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.
+
+5. **Perform the archive**
+
+ Create the archive directory if it doesn't exist:
+
+ ```bash
+ mkdir -p openspec/changes/archive
+ ```
+
+ Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+ **Check if target already exists:**
+ - If yes: Fail with error, suggest renaming existing archive or using different date
+ - If no: Move the change directory to archive
+
+ ```bash
+ mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+ ```
+
+6. **Display summary**
+
+ Show archive completion summary including:
+ - Change name
+ - Schema that was used
+ - Archive location
+ - Whether specs were synced (if applicable)
+ - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs (or "No delta specs" or "Sync skipped")
+
+All artifacts complete. All tasks complete.
+```
+
+**Guardrails**
+
+- Always prompt for change selection if not provided
+- Use artifact graph (openspec status --json) for completion checking
+- 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 openspec-sync-specs approach (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting
--- /dev/null
+---
+name: openspec-bulk-archive-change
+description: Archive multiple completed changes at once. Use when archiving several parallel changes.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+Archive multiple completed changes in a single operation.
+
+This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented.
+
+**Input**: None required (prompts for selection)
+
+**Steps**
+
+1. **Get active changes**
+
+ Run `openspec list --json` to get all active changes.
+
+ If no active changes exist, inform user and stop.
+
+2. **Prompt for change selection**
+
+ Use **AskUserQuestion tool** with multi-select to let user choose changes:
+ - Show each change with its schema
+ - Include an option for "All changes"
+ - Allow any number of selections (1+ works, 2+ is the typical use case)
+
+ **IMPORTANT**: Do NOT auto-select. Always let the user choose.
+
+3. **Batch validation - gather status for all selected changes**
+
+ For each selected change, collect:
+
+ a. **Artifact status** - Run `openspec status --change "<name>" --json`
+ - Parse `schemaName` and `artifacts` list
+ - Note which artifacts are `done` vs other states
+
+ b. **Task completion** - Read `openspec/changes/<name>/tasks.md`
+ - Count `- [ ]` (incomplete) vs `- [x]` (complete)
+ - If no tasks file exists, note as "No tasks"
+
+ c. **Delta specs** - Check `openspec/changes/<name>/specs/` directory
+ - List which capability specs exist
+ - For each, extract requirement names (lines matching `### Requirement: <name>`)
+
+4. **Detect spec conflicts**
+
+ Build a map of `capability -> [changes that touch it]`:
+
+ ```
+ auth -> [change-a, change-b] <- CONFLICT (2+ changes)
+ api -> [change-c] <- OK (only 1 change)
+ ```
+
+ A conflict exists when 2+ selected changes have delta specs for the same capability.
+
+5. **Resolve conflicts agentically**
+
+ **For each conflict**, investigate the codebase:
+
+ a. **Read the delta specs** from each conflicting change to understand what each claims to add/modify
+
+ b. **Search the codebase** for implementation evidence:
+ - Look for code implementing requirements from each delta spec
+ - Check for related files, functions, or tests
+
+ c. **Determine resolution**:
+ - If only one change is actually implemented -> sync that one's specs
+ - If both implemented -> apply in chronological order (older first, newer overwrites)
+ - If neither implemented -> skip spec sync, warn user
+
+ d. **Record resolution** for each conflict:
+ - Which change's specs to apply
+ - In what order (if both)
+ - Rationale (what was found in codebase)
+
+6. **Show consolidated status table**
+
+ Display a table summarizing all changes:
+
+ ```
+ | Change | Artifacts | Tasks | Specs | Conflicts | Status |
+ |---------------------|-----------|-------|---------|-----------|--------|
+ | schema-management | Done | 5/5 | 2 delta | None | Ready |
+ | project-config | Done | 3/3 | 1 delta | None | Ready |
+ | add-oauth | Done | 4/4 | 1 delta | auth (!) | Ready* |
+ | add-verify-skill | 1 left | 2/5 | None | None | Warn |
+ ```
+
+ For conflicts, show the resolution:
+
+ ```
+ * Conflict resolution:
+ - auth spec: Will apply add-oauth then add-jwt (both implemented, chronological order)
+ ```
+
+ For incomplete changes, show warnings:
+
+ ```
+ Warnings:
+ - add-verify-skill: 1 incomplete artifact, 3 incomplete tasks
+ ```
+
+7. **Confirm batch operation**
+
+ Use **AskUserQuestion tool** with a single confirmation:
+ - "Archive N changes?" with options based on status
+ - Options might include:
+ - "Archive all N changes"
+ - "Archive only N ready changes (skip incomplete)"
+ - "Cancel"
+
+ If there are incomplete changes, make clear they'll be archived with warnings.
+
+8. **Execute archive for each confirmed change**
+
+ Process changes in the determined order (respecting conflict resolution):
+
+ a. **Sync specs** if delta specs exist:
+ - Use the openspec-sync-specs approach (agent-driven intelligent merge)
+ - For conflicts, apply in resolved order
+ - Track if sync was done
+
+ b. **Perform the archive**:
+
+ ```bash
+ mkdir -p openspec/changes/archive
+ mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+ ```
+
+ c. **Track outcome** for each change:
+ - Success: archived successfully
+ - Failed: error during archive (record error)
+ - Skipped: user chose not to archive (if applicable)
+
+9. **Display summary**
+
+ Show final results:
+
+ ```
+ ## Bulk Archive Complete
+
+ Archived 3 changes:
+ - schema-management-cli -> archive/2026-01-19-schema-management-cli/
+ - project-config -> archive/2026-01-19-project-config/
+ - add-oauth -> archive/2026-01-19-add-oauth/
+
+ Skipped 1 change:
+ - add-verify-skill (user chose not to archive incomplete)
+
+ Spec sync summary:
+ - 4 delta specs synced to main specs
+ - 1 conflict resolved (auth: applied both in chronological order)
+ ```
+
+ If any failures:
+
+ ```
+ Failed 1 change:
+ - some-change: Archive directory already exists
+ ```
+
+**Conflict Resolution Examples**
+
+Example 1: Only one implemented
+
+```
+Conflict: specs/auth/spec.md touched by [add-oauth, add-jwt]
+
+Checking add-oauth:
+- Delta adds "OAuth Provider Integration" requirement
+- Searching codebase... found src/auth/oauth.ts implementing OAuth flow
+
+Checking add-jwt:
+- Delta adds "JWT Token Handling" requirement
+- Searching codebase... no JWT implementation found
+
+Resolution: Only add-oauth is implemented. Will sync add-oauth specs only.
+```
+
+Example 2: Both implemented
+
+```
+Conflict: specs/api/spec.md touched by [add-rest-api, add-graphql]
+
+Checking add-rest-api (created 2026-01-10):
+- Delta adds "REST Endpoints" requirement
+- Searching codebase... found src/api/rest.ts
+
+Checking add-graphql (created 2026-01-15):
+- Delta adds "GraphQL Schema" requirement
+- Searching codebase... found src/api/graphql.ts
+
+Resolution: Both implemented. Will apply add-rest-api specs first,
+then add-graphql specs (chronological order, newer takes precedence).
+```
+
+**Output On Success**
+
+```
+## Bulk Archive Complete
+
+Archived N changes:
+- <change-1> -> archive/YYYY-MM-DD-<change-1>/
+- <change-2> -> archive/YYYY-MM-DD-<change-2>/
+
+Spec sync summary:
+- N delta specs synced to main specs
+- No conflicts (or: M conflicts resolved)
+```
+
+**Output On Partial Success**
+
+```
+## Bulk Archive Complete (partial)
+
+Archived N changes:
+- <change-1> -> archive/YYYY-MM-DD-<change-1>/
+
+Skipped M changes:
+- <change-2> (user chose not to archive incomplete)
+
+Failed K changes:
+- <change-3>: Archive directory already exists
+```
+
+**Output When No Changes**
+
+```
+## No Changes to Archive
+
+No active changes found. Use `/opsx:new` to create a new change.
+```
+
+**Guardrails**
+
+- Allow any number of changes (1+ is fine, 2+ is the typical use case)
+- Always prompt for selection, never auto-select
+- Detect spec conflicts early and resolve by checking codebase
+- When both changes are implemented, apply specs in chronological order
+- Skip spec sync only when implementation is missing (warn user)
+- Show clear per-change status before confirming
+- Use single confirmation for entire batch
+- Track and report all outcomes (success/skip/fail)
+- Preserve .openspec.yaml when moving to archive
+- Archive directory target uses current date: YYYY-MM-DD-<name>
+- If archive target exists, fail that change but continue with others
--- /dev/null
+---
+name: openspec-continue-change
+description: Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+Continue working on a change by creating the next artifact.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+ Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.
+
+ Present the top 3-4 most recently modified changes as options, showing:
+ - Change name
+ - Schema (from `schema` field if present, otherwise "spec-driven")
+ - Status (e.g., "0/5 tasks", "complete", "no tasks")
+ - How recently it was modified (from `lastModified` field)
+
+ Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to continue.
+
+ **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check current status**
+
+ ```bash
+ openspec status --change "<name>" --json
+ ```
+
+ Parse the JSON to understand current state. The response includes:
+ - `schemaName`: The workflow schema being used (e.g., "spec-driven")
+ - `artifacts`: Array of artifacts with their status ("done", "ready", "blocked")
+ - `isComplete`: Boolean indicating if all artifacts are complete
+
+3. **Act based on status**:
+
+ ***
+
+ **If all artifacts are complete (`isComplete: true`)**:
+ - Congratulate the user
+ - Show final status including the schema used
+ - Suggest: "All artifacts created! You can now implement this change or archive it."
+ - STOP
+
+ ***
+
+ **If artifacts are ready to create** (status shows artifacts with `status: "ready"`):
+ - Pick the FIRST artifact with `status: "ready"` from the status output
+ - Get its instructions:
+ ```bash
+ openspec instructions <artifact-id> --change "<name>" --json
+ ```
+ - Parse the JSON. The key fields are:
+ - `context`: Project background (constraints for you - do NOT include in output)
+ - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+ - `template`: The structure to use for your output file
+ - `instruction`: Schema-specific guidance
+ - `outputPath`: Where to write the artifact
+ - `dependencies`: Completed artifacts to read for context
+ - **Create the artifact file**:
+ - Read any completed dependency files for context
+ - Use `template` as the structure - fill in its sections
+ - Apply `context` and `rules` as constraints when writing - but do NOT copy them into the file
+ - Write to the output path specified in instructions
+ - Show what was created and what's now unlocked
+ - STOP after creating ONE artifact
+
+ ***
+
+ **If no artifacts are ready (all blocked)**:
+ - This shouldn't happen with a valid schema
+ - Show status and suggest checking for issues
+
+4. **After creating an artifact, show progress**
+ ```bash
+ openspec status --change "<name>"
+ ```
+
+**Output**
+
+After each invocation, show:
+
+- Which artifact was created
+- Schema workflow being used
+- Current progress (N/M complete)
+- What artifacts are now unlocked
+- Prompt: "Want to continue? Just ask me to continue or tell me what to do next."
+
+**Artifact Creation Guidelines**
+
+The artifact types and their purpose depend on the schema. Use the `instruction` field from the instructions output to understand what to create.
+
+Common artifact patterns:
+
+**spec-driven schema** (proposal → specs → design → tasks):
+
+- **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.
+ - The Capabilities section is critical - each capability listed will need a spec file.
+- **specs/<capability>/spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).
+- **design.md**: Document technical decisions, architecture, and implementation approach.
+- **tasks.md**: Break down implementation into checkboxed tasks.
+
+For other schemas, follow the `instruction` field from the CLI output.
+
+**Guardrails**
+
+- Create ONE artifact per invocation
+- Always read dependency artifacts before creating a new one
+- Never skip artifacts or create out of order
+- If context is unclear, ask the user before creating
+- Verify the artifact file exists after writing before marking progress
+- Use the schema's artifact sequence, don't assume specific artifact names
+- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
+ - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
+ - These guide what you write, but should never appear in the output
--- /dev/null
+---
+name: openspec-explore
+description: Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+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.
+
+**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.
+
+---
+
+## The Stance
+
+- **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script
+- **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
+- **Visual** - Use ASCII diagrams liberally when they'd help clarify thinking
+- **Adaptive** - Follow interesting threads, pivot when new information emerges
+- **Patient** - Don't rush to conclusions, let the shape of the problem emerge
+- **Grounded** - Explore the actual codebase when relevant, don't just theorize
+
+---
+
+## What You Might Do
+
+Depending on what the user brings, you might:
+
+**Explore the problem space**
+
+- Ask clarifying questions that emerge from what they said
+- Challenge assumptions
+- Reframe the problem
+- Find analogies
+
+**Investigate the codebase**
+
+- Map existing architecture relevant to the discussion
+- Find integration points
+- Identify patterns already in use
+- Surface hidden complexity
+
+**Compare options**
+
+- Brainstorm multiple approaches
+- Build comparison tables
+- Sketch tradeoffs
+- Recommend a path (if asked)
+
+**Visualize**
+
+```
+┌─────────────────────────────────────────┐
+│ Use ASCII diagrams liberally │
+├─────────────────────────────────────────┤
+│ │
+│ ┌────────┐ ┌────────┐ │
+│ │ State │────────▶│ State │ │
+│ │ A │ │ B │ │
+│ └────────┘ └────────┘ │
+│ │
+│ System diagrams, state machines, │
+│ data flows, architecture sketches, │
+│ dependency graphs, comparison tables │
+│ │
+└─────────────────────────────────────────┘
+```
+
+**Surface risks and unknowns**
+
+- Identify what could go wrong
+- Find gaps in understanding
+- Suggest spikes or investigations
+
+---
+
+## OpenSpec Awareness
+
+You have full context of the OpenSpec system. Use it naturally, don't force it.
+
+### Check for context
+
+At the start, quickly check what exists:
+
+```bash
+openspec list --json
+```
+
+This tells you:
+
+- If there are active changes
+- Their names, schemas, and status
+- What the user might be working on
+
+### When no change exists
+
+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`
+- Or keep exploring - no pressure to formalize
+
+### When a change exists
+
+If the user mentions a change or you detect one is relevant:
+
+1. **Read existing artifacts for context**
+ - `openspec/changes/<name>/proposal.md`
+ - `openspec/changes/<name>/design.md`
+ - `openspec/changes/<name>/tasks.md`
+ - etc.
+
+2. **Reference them naturally in conversation**
+ - "Your design mentions using Redis, but we just realized SQLite fits better..."
+ - "The proposal scopes this to premium users, but we're now thinking everyone..."
+
+3. **Offer to capture when decisions are made**
+
+ | Insight Type | Where to Capture |
+ | -------------------------- | ---------------------------- |
+ | New requirement discovered | `specs/<capability>/spec.md` |
+ | Requirement changed | `specs/<capability>/spec.md` |
+ | Design decision made | `design.md` |
+ | Scope changed | `proposal.md` |
+ | New work identified | `tasks.md` |
+ | Assumption invalidated | Relevant artifact |
+
+ Example offers:
+ - "That's a design decision. Capture it in design.md?"
+ - "This is a new requirement. Add it to specs?"
+ - "This changes scope. Update the proposal?"
+
+4. **The user decides** - Offer and move on. Don't pressure. Don't auto-capture.
+
+---
+
+## What You Don't Have To Do
+
+- Follow a script
+- Ask the same questions every time
+- Produce a specific artifact
+- Reach a conclusion
+- Stay on topic if a tangent is valuable
+- Be brief (this is thinking time)
+
+---
+
+## Handling Different Entry Points
+
+**User brings a vague idea:**
+
+```
+User: I'm thinking about adding real-time collaboration
+
+You: Real-time collab is a big space. Let me think about this...
+
+ COLLABORATION SPECTRUM
+ ════════════════════════════════════════════
+
+ Awareness Coordination Sync
+ │ │ │
+ ▼ ▼ ▼
+ ┌────────┐ ┌────────┐ ┌────────┐
+ │Presence│ │Cursors │ │ CRDT │
+ │ "3 │ │ Multi │ │Conflict│
+ │online" │ │ select │ │ free │
+ └────────┘ └────────┘ └────────┘
+ │ │ │
+ trivial moderate complex
+
+ Where's your head at?
+```
+
+**User brings a specific problem:**
+
+```
+User: The auth system is a mess
+
+You: [reads codebase]
+
+ ┌─────────────────────────────────────────────┐
+ │ CURRENT AUTH FLOW │
+ └─────────────────────────────────────────────┘
+ │
+ ┌─────────────┼─────────────┐
+ ▼ ▼ ▼
+ ┌─────────┐ ┌─────────┐ ┌─────────┐
+ │ Google │ │ GitHub │ │ Email │
+ │ OAuth │ │ OAuth │ │ Magic │
+ └────┬────┘ └────┬────┘ └────┬────┘
+ │ │ │
+ └─────────────┼─────────────┘
+ ▼
+ ┌───────────┐
+ │ Session │
+ └─────┬─────┘
+ │
+ ▼
+ ┌───────────┐
+ │ Perms │
+ └───────────┘
+
+ I see three tangles. Which one's burning?
+```
+
+**User is stuck mid-implementation:**
+
+```
+User: /opsx:explore add-auth-system
+ The OAuth integration is more complex than expected
+
+You: [reads change artifacts]
+
+ You're on task 4: "Implement OAuth flow"
+
+ Let me trace what's involved...
+
+ [draws diagram, explores options, suggests paths]
+
+ Want to update the design to reflect this?
+ Or add a spike task to investigate?
+```
+
+**User wants to compare options:**
+
+```
+User: Should we use Postgres or SQLite?
+
+You: Generic answer is boring. What's the context?
+
+User: A CLI tool that tracks local dev environments
+
+You: That changes everything.
+
+ ┌─────────────────────────────────────────────────┐
+ │ CLI TOOL DATA STORAGE │
+ └─────────────────────────────────────────────────┘
+
+ Key constraints:
+ • No daemon running
+ • Must work offline
+ • Single user
+
+ SQLite Postgres
+ Deployment embedded ✓ needs server ✗
+ Offline yes ✓ no ✗
+ Single file yes ✓ no ✗
+
+ SQLite. Not even close.
+
+ Unless... is there a sync component?
+```
+
+---
+
+## Ending Discovery
+
+There's no required ending. Discovery might:
+
+- **Flow into action**: "Ready to start? /opsx:new or /opsx:ff"
+- **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"
+
+When it feels like things are crystallizing, you might summarize:
+
+```
+## What We Figured Out
+
+**The problem**: [crystallized understanding]
+
+**The approach**: [if one emerged]
+
+**Open questions**: [if any remain]
+
+**Next steps** (if ready):
+- Create a change: /opsx:new <name>
+- Fast-forward to tasks: /opsx:ff <name>
+- Keep exploring: just keep talking
+```
+
+But this summary is optional. Sometimes the thinking IS the value.
+
+---
+
+## Guardrails
+
+- **Don't implement** - Never write code or implement features. Creating OpenSpec artifacts is fine, writing application code is not.
+- **Don't fake understanding** - If something is unclear, dig deeper
+- **Don't rush** - Discovery is thinking time, not task time
+- **Don't force structure** - Let patterns emerge naturally
+- **Don't auto-capture** - Offer to save insights, don't just do it
+- **Do visualize** - A good diagram is worth many paragraphs
+- **Do explore the codebase** - Ground discussions in reality
+- **Do question assumptions** - Including the user's and your own
--- /dev/null
+---
+name: openspec-ff-change
+description: Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+Fast-forward through artifact creation - generate everything needed to start implementation in one go.
+
+**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.
+
+**Steps**
+
+1. **If no clear input provided, ask what they want to build**
+
+ Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+
+ > "What change do you want to work on? Describe what you want to build or fix."
+
+ From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+ **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Create the change directory**
+
+ ```bash
+ openspec new change "<name>"
+ ```
+
+ This creates a scaffolded change at `openspec/changes/<name>/`.
+
+3. **Get the artifact build order**
+
+ ```bash
+ openspec status --change "<name>" --json
+ ```
+
+ Parse the JSON to get:
+ - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`)
+ - `artifacts`: list of all artifacts with their status and dependencies
+
+4. **Create artifacts in sequence until apply-ready**
+
+ Use the **TodoWrite tool** to track progress through the artifacts.
+
+ Loop through artifacts in dependency order (artifacts with no pending dependencies first):
+
+ a. **For each artifact that is `ready` (dependencies satisfied)**:
+ - Get instructions:
+ ```bash
+ openspec instructions <artifact-id> --change "<name>" --json
+ ```
+ - The instructions JSON includes:
+ - `context`: Project background (constraints for you - do NOT include in output)
+ - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+ - `template`: The structure to use for your output file
+ - `instruction`: Schema-specific guidance for this artifact type
+ - `outputPath`: Where to write the artifact
+ - `dependencies`: Completed artifacts to read for context
+ - Read any completed dependency files for context
+ - Create the artifact file using `template` as the structure
+ - Apply `context` and `rules` as constraints - but do NOT copy them into the file
+ - Show brief progress: "✓ Created <artifact-id>"
+
+ b. **Continue until all `applyRequires` artifacts are complete**
+ - After creating each artifact, re-run `openspec status --change "<name>" --json`
+ - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array
+ - Stop when all `applyRequires` artifacts are done
+
+ c. **If an artifact requires user input** (unclear context):
+ - Use **AskUserQuestion tool** to clarify
+ - Then continue with creation
+
+5. **Show final status**
+ ```bash
+ openspec status --change "<name>"
+ ```
+
+**Output**
+
+After completing all artifacts, summarize:
+
+- Change name and location
+- List of artifacts created with brief descriptions
+- What's ready: "All artifacts created! Ready for implementation."
+- Prompt: "Run `/opsx:apply` or ask me to implement to start working on the tasks."
+
+**Artifact Creation Guidelines**
+
+- 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 `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 `<context>`, `<rules>`, `<project_context>` blocks into the artifact
+ - These guide what you write, but should never appear in the output
+
+**Guardrails**
+
+- Create ALL artifacts needed for implementation (as defined by schema's `apply.requires`)
+- Always read dependency artifacts before creating a new one
+- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
+- If a change with that name already exists, suggest continuing that change instead
+- Verify each artifact file exists after writing before proceeding to next
--- /dev/null
+---
+name: openspec-new-change
+description: Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+Start a new change using the experimental artifact-driven approach.
+
+**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.
+
+**Steps**
+
+1. **If no clear input provided, ask what they want to build**
+
+ Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+
+ > "What change do you want to work on? Describe what you want to build or fix."
+
+ From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+ **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Determine the workflow schema**
+
+ Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.
+
+ **Use a different schema only if the user mentions:**
+ - A specific schema name → use `--schema <name>`
+ - "show workflows" or "what workflows" → run `openspec schemas --json` and let them choose
+
+ **Otherwise**: Omit `--schema` to use the default.
+
+3. **Create the change directory**
+
+ ```bash
+ openspec new change "<name>"
+ ```
+
+ Add `--schema <name>` only if the user requested a specific workflow.
+ This creates a scaffolded change at `openspec/changes/<name>/` with the selected schema.
+
+4. **Show the artifact status**
+
+ ```bash
+ openspec status --change "<name>"
+ ```
+
+ This shows which artifacts need to be created and which are ready (dependencies satisfied).
+
+5. **Get instructions for the first artifact**
+ The first artifact depends on the schema (e.g., `proposal` for spec-driven).
+ Check the status output to find the first artifact with status "ready".
+
+ ```bash
+ openspec instructions <first-artifact-id> --change "<name>"
+ ```
+
+ This outputs the template and context for creating the first artifact.
+
+6. **STOP and wait for user direction**
+
+**Output**
+
+After completing the steps, summarize:
+
+- Change name and location
+- Schema/workflow being used and its artifact sequence
+- Current status (0/N artifacts complete)
+- The template for the first artifact
+- Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."
+
+**Guardrails**
+
+- Do NOT create any artifacts yet - just show the instructions
+- Do NOT advance beyond showing the first artifact template
+- If the name is invalid (not kebab-case), ask for a valid name
+- If a change with that name already exists, suggest continuing that change instead
+- Pass --schema if using a non-default workflow
--- /dev/null
+---
+name: openspec-onboard
+description: Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+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.
+
+---
+
+## Preflight
+
+Before starting, check if OpenSpec is initialized:
+
+```bash
+openspec status --json 2>&1 || echo "NOT_INITIALIZED"
+```
+
+**If not initialized:**
+
+> OpenSpec isn't set up in this project yet. Run `openspec init` first, then come back to `/opsx:onboard`.
+
+Stop here if not initialized.
+
+---
+
+## Phase 1: Welcome
+
+Display:
+
+```
+## Welcome to OpenSpec!
+
+I'll walk you through a complete change cycle—from idea to implementation—using a real task in your codebase. Along the way, you'll learn the workflow by doing it.
+
+**What we'll do:**
+1. Pick a small, real task in your codebase
+2. Explore the problem briefly
+3. Create a change (the container for our work)
+4. Build the artifacts: proposal → specs → design → tasks
+5. Implement the tasks
+6. Archive the completed change
+
+**Time:** ~15-20 minutes
+
+Let's start by finding something to work on.
+```
+
+---
+
+## Phase 2: Task Selection
+
+### Codebase Analysis
+
+Scan the codebase for small improvement opportunities. Look for:
+
+1. **TODO/FIXME comments** - Search for `TODO`, `FIXME`, `HACK`, `XXX` in code files
+2. **Missing error handling** - `catch` blocks that swallow errors, risky operations without try-catch
+3. **Functions without tests** - Cross-reference `src/` with test directories
+4. **Type issues** - `any` types in TypeScript files (`: any`, `as any`)
+5. **Debug artifacts** - `console.log`, `console.debug`, `debugger` statements in non-debug code
+6. **Missing validation** - User input handlers without validation
+
+Also check recent git activity:
+
+```bash
+git log --oneline -10 2>/dev/null || echo "No git history"
+```
+
+### Present Suggestions
+
+From your analysis, present 3-4 specific suggestions:
+
+```
+## Task Suggestions
+
+Based on scanning your codebase, here are some good starter tasks:
+
+**1. [Most promising task]**
+ Location: `src/path/to/file.ts:42`
+ Scope: ~1-2 files, ~20-30 lines
+ Why it's good: [brief reason]
+
+**2. [Second task]**
+ Location: `src/another/file.ts`
+ Scope: ~1 file, ~15 lines
+ Why it's good: [brief reason]
+
+**3. [Third task]**
+ Location: [location]
+ Scope: [estimate]
+ Why it's good: [brief reason]
+
+**4. Something else?**
+ Tell me what you'd like to work on.
+
+Which task interests you? (Pick a number or describe your own)
+```
+
+**If nothing found:** Fall back to asking what the user wants to build:
+
+> I didn't find obvious quick wins in your codebase. What's something small you've been meaning to add or fix?
+
+### Scope Guardrail
+
+If the user picks or describes something too large (major feature, multi-day work):
+
+```
+That's a valuable task, but it's probably larger than ideal for your first OpenSpec run-through.
+
+For learning the workflow, smaller is better—it lets you see the full cycle without getting stuck in implementation details.
+
+**Options:**
+1. **Slice it smaller** - What's the smallest useful piece of [their task]? Maybe just [specific slice]?
+2. **Pick something else** - One of the other suggestions, or a different small task?
+3. **Do it anyway** - If you really want to tackle this, we can. Just know it'll take longer.
+
+What would you prefer?
+```
+
+Let the user override if they insist—this is a soft guardrail.
+
+---
+
+## Phase 3: Explore Demo
+
+Once a task is selected, briefly demonstrate explore mode:
+
+```
+Before we create a change, let me quickly show you **explore mode**—it's how you think through problems before committing to a direction.
+```
+
+Spend 1-2 minutes investigating the relevant code:
+
+- Read the file(s) involved
+- Draw a quick ASCII diagram if it helps
+- Note any considerations
+
+```
+## Quick Exploration
+
+[Your brief analysis—what you found, any considerations]
+
+┌─────────────────────────────────────────┐
+│ [Optional: ASCII diagram if helpful] │
+└─────────────────────────────────────────┘
+
+Explore mode (`/opsx:explore`) is for this kind of thinking—investigating before implementing. You can use it anytime you need to think through a problem.
+
+Now let's create a change to hold our work.
+```
+
+**PAUSE** - Wait for user acknowledgment before proceeding.
+
+---
+
+## Phase 4: Create the Change
+
+**EXPLAIN:**
+
+```
+## Creating a Change
+
+A "change" in OpenSpec is a container for all the thinking and planning around a piece of work. It lives in `openspec/changes/<name>/` and holds your artifacts—proposal, specs, design, tasks.
+
+Let me create one for our task.
+```
+
+**DO:** Create the change with a derived kebab-case name:
+
+```bash
+openspec new change "<derived-name>"
+```
+
+**SHOW:**
+
+```
+Created: `openspec/changes/<name>/`
+
+The folder structure:
+```
+
+openspec/changes/<name>/
+├── proposal.md ← Why we're doing this (empty, we'll fill it)
+├── design.md ← How we'll build it (empty)
+├── specs/ ← Detailed requirements (empty)
+└── tasks.md ← Implementation checklist (empty)
+
+```
+
+Now let's fill in the first artifact—the proposal.
+```
+
+---
+
+## Phase 5: Proposal
+
+**EXPLAIN:**
+
+```
+## The Proposal
+
+The proposal captures **why** we're making this change and **what** it involves at a high level. It's the "elevator pitch" for the work.
+
+I'll draft one based on our task.
+```
+
+**DO:** Draft the proposal content (don't save yet):
+
+```
+Here's a draft proposal:
+
+---
+
+## Why
+
+[1-2 sentences explaining the problem/opportunity]
+
+## What Changes
+
+[Bullet points of what will be different]
+
+## Capabilities
+
+### New Capabilities
+- `<capability-name>`: [brief description]
+
+### Modified Capabilities
+<!-- If modifying existing behavior -->
+
+## Impact
+
+- `src/path/to/file.ts`: [what changes]
+- [other files if applicable]
+
+---
+
+Does this capture the intent? I can adjust before we save it.
+```
+
+**PAUSE** - Wait for user approval/feedback.
+
+After approval, save the proposal:
+
+```bash
+openspec instructions proposal --change "<name>" --json
+```
+
+Then write the content to `openspec/changes/<name>/proposal.md`.
+
+```
+Proposal saved. This is your "why" document—you can always come back and refine it as understanding evolves.
+
+Next up: specs.
+```
+
+---
+
+## Phase 6: Specs
+
+**EXPLAIN:**
+
+```
+## Specs
+
+Specs define **what** we're building in precise, testable terms. They use a requirement/scenario format that makes expected behavior crystal clear.
+
+For a small task like this, we might only need one spec file.
+```
+
+**DO:** Create the spec file:
+
+```bash
+mkdir -p openspec/changes/<name>/specs/<capability-name>
+```
+
+Draft the spec content:
+
+```
+Here's the spec:
+
+---
+
+## ADDED Requirements
+
+### Requirement: <Name>
+
+<Description of what the system should do>
+
+#### Scenario: <Scenario name>
+
+- **WHEN** <trigger condition>
+- **THEN** <expected outcome>
+- **AND** <additional outcome if needed>
+
+---
+
+This format—WHEN/THEN/AND—makes requirements testable. You can literally read them as test cases.
+```
+
+Save to `openspec/changes/<name>/specs/<capability>/spec.md`.
+
+---
+
+## Phase 7: Design
+
+**EXPLAIN:**
+
+```
+## Design
+
+The design captures **how** we'll build it—technical decisions, tradeoffs, approach.
+
+For small changes, this might be brief. That's fine—not every change needs deep design discussion.
+```
+
+**DO:** Draft design.md:
+
+```
+Here's the design:
+
+---
+
+## Context
+
+[Brief context about the current state]
+
+## Goals / Non-Goals
+
+**Goals:**
+- [What we're trying to achieve]
+
+**Non-Goals:**
+- [What's explicitly out of scope]
+
+## Decisions
+
+### Decision 1: [Key decision]
+
+[Explanation of approach and rationale]
+
+---
+
+For a small task, this captures the key decisions without over-engineering.
+```
+
+Save to `openspec/changes/<name>/design.md`.
+
+---
+
+## Phase 8: Tasks
+
+**EXPLAIN:**
+
+```
+## Tasks
+
+Finally, we break the work into implementation tasks—checkboxes that drive the apply phase.
+
+These should be small, clear, and in logical order.
+```
+
+**DO:** Generate tasks based on specs and design:
+
+```
+Here are the implementation tasks:
+
+---
+
+## 1. [Category or file]
+
+- [ ] 1.1 [Specific task]
+- [ ] 1.2 [Specific task]
+
+## 2. Verify
+
+- [ ] 2.1 [Verification step]
+
+---
+
+Each checkbox becomes a unit of work in the apply phase. Ready to implement?
+```
+
+**PAUSE** - Wait for user to confirm they're ready to implement.
+
+Save to `openspec/changes/<name>/tasks.md`.
+
+---
+
+## Phase 9: Apply (Implementation)
+
+**EXPLAIN:**
+
+```
+## Implementation
+
+Now we implement each task, checking them off as we go. I'll announce each one and occasionally note how the specs/design informed the approach.
+```
+
+**DO:** For each task:
+
+1. Announce: "Working on task N: [description]"
+2. Implement the change in the codebase
+3. Reference specs/design naturally: "The spec says X, so I'm doing Y"
+4. Mark complete in tasks.md: `- [ ]` → `- [x]`
+5. Brief status: "✓ Task N complete"
+
+Keep narration light—don't over-explain every line of code.
+
+After all tasks:
+
+```
+## Implementation Complete
+
+All tasks done:
+- [x] Task 1
+- [x] Task 2
+- [x] ...
+
+The change is implemented! One more step—let's archive it.
+```
+
+---
+
+## Phase 10: Archive
+
+**EXPLAIN:**
+
+```
+## Archiving
+
+When a change is complete, we archive it. This moves it from `openspec/changes/` to `openspec/changes/archive/YYYY-MM-DD-<name>/`.
+
+Archived changes become your project's decision history—you can always find them later to understand why something was built a certain way.
+```
+
+**DO:**
+
+```bash
+openspec archive "<name>"
+```
+
+**SHOW:**
+
+```
+Archived to: `openspec/changes/archive/YYYY-MM-DD-<name>/`
+
+The change is now part of your project's history. The code is in your codebase, the decision record is preserved.
+```
+
+---
+
+## Phase 11: Recap & Next Steps
+
+```
+## Congratulations!
+
+You just completed a full OpenSpec cycle:
+
+1. **Explore** - Thought through the problem
+2. **New** - Created a change container
+3. **Proposal** - Captured WHY
+4. **Specs** - Defined WHAT in detail
+5. **Design** - Decided HOW
+6. **Tasks** - Broke it into steps
+7. **Apply** - Implemented the work
+8. **Archive** - Preserved the record
+
+This same rhythm works for any size change—a small fix or a major feature.
+
+---
+
+## Command Reference
+
+| Command | What it does |
+|---------|--------------|
+| `/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 |
+
+---
+
+## What's Next?
+
+Try `/opsx:new` or `/opsx:ff` on something you actually want to build. You've got the rhythm now!
+```
+
+---
+
+## Graceful Exit Handling
+
+### User wants to stop mid-way
+
+If the user says they need to stop, want to pause, or seem disengaged:
+
+```
+No problem! Your change is saved at `openspec/changes/<name>/`.
+
+To pick up where we left off later:
+- `/opsx:continue <name>` - Resume artifact creation
+- `/opsx:apply <name>` - Jump to implementation (if tasks exist)
+
+The work won't be lost. Come back whenever you're ready.
+```
+
+Exit gracefully without pressure.
+
+### User just wants command reference
+
+If the user says they just want to see the commands or skip the tutorial:
+
+```
+## OpenSpec Quick Reference
+
+| Command | What it does |
+|---------|--------------|
+| `/opsx:explore` | Think through problems (no code changes) |
+| `/opsx:new <name>` | Start a new change, step by step |
+| `/opsx:ff <name>` | Fast-forward: all artifacts at once |
+| `/opsx:continue <name>` | Continue an existing change |
+| `/opsx:apply <name>` | Implement tasks |
+| `/opsx:verify <name>` | Verify implementation |
+| `/opsx:archive <name>` | Archive when done |
+
+Try `/opsx:new` to start your first change, or `/opsx:ff` if you want to move fast.
+```
+
+Exit gracefully.
+
+---
+
+## Guardrails
+
+- **Follow the EXPLAIN → DO → SHOW → PAUSE pattern** at key transitions (after explore, after proposal draft, after tasks, after archive)
+- **Keep narration light** during implementation—teach without lecturing
+- **Don't skip phases** even if the change is small—the goal is teaching the workflow
+- **Pause for acknowledgment** at marked points, but don't over-pause
+- **Handle exits gracefully**—never pressure the user to continue
+- **Use real codebase tasks**—don't simulate or use fake examples
+- **Adjust scope gently**—guide toward smaller tasks but respect user choice
--- /dev/null
+---
+name: openspec-sync-specs
+description: Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+Sync delta specs from a change to main specs.
+
+This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+ Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+ Show changes that have delta specs (under `specs/` directory).
+
+ **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Find delta specs**
+
+ Look for delta spec files in `openspec/changes/<name>/specs/*/spec.md`.
+
+ Each delta spec file contains sections like:
+ - `## ADDED Requirements` - New requirements to add
+ - `## MODIFIED Requirements` - Changes to existing requirements
+ - `## REMOVED Requirements` - Requirements to remove
+ - `## RENAMED Requirements` - Requirements to rename (FROM:/TO: format)
+
+ If no delta specs found, inform user and stop.
+
+3. **For each delta spec, apply changes to main specs**
+
+ For each capability with a delta spec at `openspec/changes/<name>/specs/<capability>/spec.md`:
+
+ a. **Read the delta spec** to understand the intended changes
+
+ b. **Read the main spec** at `openspec/specs/<capability>/spec.md` (may not exist yet)
+
+ c. **Apply changes intelligently**:
+
+ **ADDED Requirements:**
+ - If requirement doesn't exist in main spec → add it
+ - If requirement already exists → update it to match (treat as implicit MODIFIED)
+
+ **MODIFIED Requirements:**
+ - Find the requirement in main spec
+ - Apply the changes - this can be:
+ - Adding new scenarios (don't need to copy existing ones)
+ - Modifying existing scenarios
+ - Changing the requirement description
+ - Preserve scenarios/content not mentioned in the delta
+
+ **REMOVED Requirements:**
+ - Remove the entire requirement block from main spec
+
+ **RENAMED Requirements:**
+ - Find the FROM requirement, rename to TO
+
+ d. **Create new main spec** if capability doesn't exist yet:
+ - Create `openspec/specs/<capability>/spec.md`
+ - Add Purpose section (can be brief, mark as TBD)
+ - Add Requirements section with the ADDED requirements
+
+4. **Show summary**
+
+ After applying all changes, summarize:
+ - Which capabilities were updated
+ - What changes were made (requirements added/modified/removed/renamed)
+
+**Delta Spec Format Reference**
+
+```markdown
+## ADDED Requirements
+
+### Requirement: New Feature
+
+The system SHALL do something new.
+
+#### Scenario: Basic case
+
+- **WHEN** user does X
+- **THEN** system does Y
+
+## MODIFIED Requirements
+
+### Requirement: Existing Feature
+
+#### Scenario: New scenario to add
+
+- **WHEN** user does A
+- **THEN** system does B
+
+## REMOVED Requirements
+
+### Requirement: Deprecated Feature
+
+## RENAMED Requirements
+
+- FROM: `### Requirement: Old Name`
+- TO: `### Requirement: New Name`
+```
+
+**Key Principle: Intelligent Merging**
+
+Unlike programmatic merging, you can apply **partial updates**:
+
+- To add a scenario, just include that scenario under MODIFIED - don't copy existing scenarios
+- The delta represents _intent_, not a wholesale replacement
+- Use your judgment to merge changes sensibly
+
+**Output On Success**
+
+```
+## Specs Synced: <change-name>
+
+Updated main specs:
+
+**<capability-1>**:
+- Added requirement: "New Feature"
+- Modified requirement: "Existing Feature" (added 1 scenario)
+
+**<capability-2>**:
+- Created new spec file
+- Added requirement: "Another Feature"
+
+Main specs are now updated. The change remains active - archive when implementation is complete.
+```
+
+**Guardrails**
+
+- Read both delta and main specs before making changes
+- Preserve existing content not mentioned in delta
+- If something is unclear, ask for clarification
+- Show what you're changing as you go
+- The operation should be idempotent - running twice should give same result
--- /dev/null
+---
+name: openspec-verify-change
+description: Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+ author: openspec
+ version: '1.0'
+ generatedBy: '1.0.2'
+---
+
+Verify that an implementation matches the change artifacts (specs, tasks, design).
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+ Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+ Show changes that have implementation tasks (tasks artifact exists).
+ Include the schema used for each change if available.
+ Mark changes with incomplete tasks as "(In Progress)".
+
+ **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check status to understand the schema**
+
+ ```bash
+ openspec status --change "<name>" --json
+ ```
+
+ Parse the JSON to understand:
+ - `schemaName`: The workflow being used (e.g., "spec-driven")
+ - Which artifacts exist for this change
+
+3. **Get the change directory and load artifacts**
+
+ ```bash
+ openspec instructions apply --change "<name>" --json
+ ```
+
+ This returns the change directory and context files. Read all available artifacts from `contextFiles`.
+
+4. **Initialize verification report structure**
+
+ Create a report structure with three dimensions:
+ - **Completeness**: Track tasks and spec coverage
+ - **Correctness**: Track requirement implementation and scenario coverage
+ - **Coherence**: Track design adherence and pattern consistency
+
+ Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
+
+5. **Verify Completeness**
+
+ **Task Completion**:
+ - If tasks.md exists in contextFiles, read it
+ - Parse checkboxes: `- [ ]` (incomplete) vs `- [x]` (complete)
+ - Count complete vs total tasks
+ - If incomplete tasks exist:
+ - Add CRITICAL issue for each incomplete task
+ - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
+
+ **Spec Coverage**:
+ - If delta specs exist in `openspec/changes/<name>/specs/`:
+ - Extract all requirements (marked with "### Requirement:")
+ - For each requirement:
+ - Search codebase for keywords related to the requirement
+ - Assess if implementation likely exists
+ - If requirements appear unimplemented:
+ - Add CRITICAL issue: "Requirement not found: <requirement name>"
+ - Recommendation: "Implement requirement X: <description>"
+
+6. **Verify Correctness**
+
+ **Requirement Implementation Mapping**:
+ - For each requirement from delta specs:
+ - Search codebase for implementation evidence
+ - If found, note file paths and line ranges
+ - Assess if implementation matches requirement intent
+ - If divergence detected:
+ - Add WARNING: "Implementation may diverge from spec: <details>"
+ - Recommendation: "Review <file>:<lines> against requirement X"
+
+ **Scenario Coverage**:
+ - For each scenario in delta specs (marked with "#### Scenario:"):
+ - Check if conditions are handled in code
+ - Check if tests exist covering the scenario
+ - If scenario appears uncovered:
+ - Add WARNING: "Scenario not covered: <scenario name>"
+ - Recommendation: "Add test or implementation for scenario: <description>"
+
+7. **Verify Coherence**
+
+ **Design Adherence**:
+ - If design.md exists in contextFiles:
+ - Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
+ - Verify implementation follows those decisions
+ - If contradiction detected:
+ - Add WARNING: "Design decision not followed: <decision>"
+ - Recommendation: "Update implementation or revise design.md to match reality"
+ - If no design.md: Skip design adherence check, note "No design.md to verify against"
+
+ **Code Pattern Consistency**:
+ - Review new code for consistency with project patterns
+ - Check file naming, directory structure, coding style
+ - If significant deviations found:
+ - Add SUGGESTION: "Code pattern deviation: <details>"
+ - Recommendation: "Consider following project pattern: <example>"
+
+8. **Generate Verification Report**
+
+ **Summary Scorecard**:
+
+ ```
+ ## Verification Report: <change-name>
+
+ ### Summary
+ | Dimension | Status |
+ |--------------|------------------|
+ | Completeness | X/Y tasks, N reqs|
+ | Correctness | M/N reqs covered |
+ | Coherence | Followed/Issues |
+ ```
+
+ **Issues by Priority**:
+ 1. **CRITICAL** (Must fix before archive):
+ - Incomplete tasks
+ - Missing requirement implementations
+ - Each with specific, actionable recommendation
+
+ 2. **WARNING** (Should fix):
+ - Spec/design divergences
+ - Missing scenario coverage
+ - Each with specific recommendation
+
+ 3. **SUGGESTION** (Nice to fix):
+ - Pattern inconsistencies
+ - Minor improvements
+ - Each with specific recommendation
+
+ **Final Assessment**:
+ - If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
+ - If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
+ - If all clear: "All checks passed. Ready for archive."
+
+**Verification Heuristics**
+
+- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)
+- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
+- **Coherence**: Look for glaring inconsistencies, don't nitpick style
+- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
+- **Actionability**: Every issue must have a specific recommendation with file/line references where applicable
+
+**Graceful Degradation**
+
+- If only tasks.md exists: verify task completion only, skip spec/design checks
+- If tasks + specs exist: verify completeness and correctness, skip design
+- If full artifacts: verify all three dimensions
+- Always note which checks were skipped and why
+
+**Output Format**
+
+Use clear markdown with:
+
+- Table for summary scorecard
+- Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
+- Code references in format: `file.ts:123`
+- Specific, actionable recommendations
+- No vague suggestions like "consider reviewing"
-<!-- OPENSPEC:START -->
-
-# OpenSpec Instructions
-
-These instructions are for AI assistants working in this project.
-
-Always open `@/openspec/AGENTS.md` when the request:
-
-- Mentions planning or proposals (words like proposal, spec, change, plan)
-- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
-- Sounds ambiguous and you need the authoritative spec before coding
-
-Use `@/openspec/AGENTS.md` to learn:
-
-- How to create and apply change proposals
-- Spec format and conventions
-- Project structure and guidelines
-
-Keep this managed block so 'openspec update' can refresh the instructions.
-
-<!-- OPENSPEC:END -->
-
Open `@/.github/copilot-instructions.md`, read it and strictly follow the instructions.
+++ /dev/null
-# OpenSpec Instructions
-
-Instructions for AI coding assistants using OpenSpec for spec-driven development.
-
-## TL;DR Quick Checklist
-
-- Search existing work: `openspec spec list --long`, `openspec list` (use `rg` only for full-text search)
-- Decide scope: new capability vs modify existing capability
-- Pick a unique `change-id`: kebab-case, verb-led (`add-`, `update-`, `remove-`, `refactor-`)
-- Scaffold: `proposal.md`, `tasks.md`, `design.md` (only if needed), and delta specs per affected capability
-- Write deltas: use `## ADDED|MODIFIED|REMOVED|RENAMED Requirements`; include at least one `#### Scenario:` per requirement
-- Validate: `openspec validate [change-id] --strict --no-interactive` and fix issues
-- Request approval: Do not start implementation until proposal is approved
-
-## Three-Stage Workflow
-
-### Stage 1: Creating Changes
-
-Create proposal when you need to:
-
-- Add features or functionality
-- Make breaking changes (API, schema)
-- Change architecture or patterns
-- Optimize performance (changes behavior)
-- Update security patterns
-
-Triggers (examples):
-
-- "Help me create a change proposal"
-- "Help me plan a change"
-- "Help me create a proposal"
-- "I want to create a spec proposal"
-- "I want to create a spec"
-
-Loose matching guidance:
-
-- Contains one of: `proposal`, `change`, `spec`
-- With one of: `create`, `plan`, `make`, `start`, `help`
-
-Skip proposal for:
-
-- Bug fixes (restore intended behavior)
-- Typos, formatting, comments
-- Dependency updates (non-breaking)
-- Configuration changes
-- Tests for existing behavior
-
-**Workflow**
-
-1. Review `openspec/project.md`, `openspec list`, and `openspec list --specs` to understand current context.
-2. Choose a unique verb-led `change-id` and scaffold `proposal.md`, `tasks.md`, optional `design.md`, and spec deltas under `openspec/changes/<id>/`.
-3. Draft spec deltas using `## ADDED|MODIFIED|REMOVED Requirements` with at least one `#### Scenario:` per requirement.
-4. Run `openspec validate <id> --strict --no-interactive` and resolve any issues before sharing the proposal.
-
-### Stage 2: Implementing Changes
-
-Track these steps as TODOs and complete them one by one.
-
-1. **Read proposal.md** - Understand what's being built
-2. **Read design.md** (if exists) - Review technical decisions
-3. **Read tasks.md** - Get implementation checklist
-4. **Implement tasks sequentially** - Complete in order
-5. **Confirm completion** - Ensure every item in `tasks.md` is finished before updating statuses
-6. **Update checklist** - After all work is done, set every task to `- [x]` so the list reflects reality
-7. **Approval gate** - Do not start implementation until the proposal is reviewed and approved
-
-### Stage 3: Archiving Changes
-
-After deployment, create separate PR to:
-
-- Move `changes/[name]/` → `changes/archive/YYYY-MM-DD-[name]/`
-- Update `specs/` if capabilities changed
-- Use `openspec archive <change-id> --skip-specs --yes` for tooling-only changes (always pass the change ID explicitly)
-- Run `openspec validate --strict --no-interactive` to confirm the archived change passes checks
-
-## Before Any Task
-
-**Context Checklist:**
-
-- [ ] Read relevant specs in `specs/[capability]/spec.md`
-- [ ] Check pending changes in `changes/` for conflicts
-- [ ] Read `openspec/project.md` for conventions
-- [ ] Run `openspec list` to see active changes
-- [ ] Run `openspec list --specs` to see existing capabilities
-
-**Before Creating Specs:**
-
-- Always check if capability already exists
-- Prefer modifying existing specs over creating duplicates
-- Use `openspec show [spec]` to review current state
-- If request is ambiguous, ask 1–2 clarifying questions before scaffolding
-
-### Search Guidance
-
-- Enumerate specs: `openspec spec list --long` (or `--json` for scripts)
-- Enumerate changes: `openspec list` (or `openspec change list --json` - deprecated but available)
-- Show details:
- - Spec: `openspec show <spec-id> --type spec` (use `--json` for filters)
- - Change: `openspec show <change-id> --json --deltas-only`
-- Full-text search (use ripgrep): `rg -n "Requirement:|Scenario:" openspec/specs`
-
-## Quick Start
-
-### CLI Commands
-
-```bash
-# Essential commands
-openspec list # List active changes
-openspec list --specs # List specifications
-openspec show [item] # Display change or spec
-openspec validate [item] # Validate changes or specs
-openspec archive <change-id> [--yes|-y] # Archive after deployment (add --yes for non-interactive runs)
-
-# Project management
-openspec init [path] # Initialize OpenSpec
-openspec update [path] # Update instruction files
-
-# Interactive mode
-openspec show # Prompts for selection
-openspec validate # Bulk validation mode
-
-# Debugging
-openspec show [change] --json --deltas-only
-openspec validate [change] --strict --no-interactive
-```
-
-### Command Flags
-
-- `--json` - Machine-readable output
-- `--type change|spec` - Disambiguate items
-- `--strict` - Comprehensive validation
-- `--no-interactive` - Disable prompts
-- `--skip-specs` - Archive without spec updates
-- `--yes`/`-y` - Skip confirmation prompts (non-interactive archive)
-
-## Directory Structure
-
-```
-openspec/
-├── project.md # Project conventions
-├── specs/ # Current truth - what IS built
-│ └── [capability]/ # Single focused capability
-│ ├── spec.md # Requirements and scenarios
-│ └── design.md # Technical patterns
-├── changes/ # Proposals - what SHOULD change
-│ ├── [change-name]/
-│ │ ├── proposal.md # Why, what, impact
-│ │ ├── tasks.md # Implementation checklist
-│ │ ├── design.md # Technical decisions (optional; see criteria)
-│ │ └── specs/ # Delta changes
-│ │ └── [capability]/
-│ │ └── spec.md # ADDED/MODIFIED/REMOVED
-│ └── archive/ # Completed changes
-```
-
-## Creating Change Proposals
-
-### Decision Tree
-
-```
-New request?
-├─ Bug fix restoring spec behavior? → Fix directly
-├─ Typo/format/comment? → Fix directly
-├─ New feature/capability? → Create proposal
-├─ Breaking change? → Create proposal
-├─ Architecture change? → Create proposal
-└─ Unclear? → Create proposal (safer)
-```
-
-### Proposal Structure
-
-1. **Create directory:** `changes/[change-id]/` (kebab-case, verb-led, unique)
-
-2. **Write proposal.md:**
-
-```markdown
-# Change: [Brief description of change]
-
-## Why
-
-[1-2 sentences on problem/opportunity]
-
-## What Changes
-
-- [Bullet list of changes]
-- [Mark breaking changes with **BREAKING**]
-
-## Impact
-
-- Affected specs: [list capabilities]
-- Affected code: [key files/systems]
-```
-
-3. **Create spec deltas:** `specs/[capability]/spec.md`
-
-```markdown
-## ADDED Requirements
-
-### Requirement: New Feature
-
-The system SHALL provide...
-
-#### Scenario: Success case
-
-- **WHEN** user performs action
-- **THEN** expected result
-
-## MODIFIED Requirements
-
-### Requirement: Existing Feature
-
-[Complete modified requirement]
-
-## REMOVED Requirements
-
-### Requirement: Old Feature
-
-**Reason**: [Why removing]
-**Migration**: [How to handle]
-```
-
-If multiple capabilities are affected, create multiple delta files under `changes/[change-id]/specs/<capability>/spec.md`—one per capability.
-
-4. **Create tasks.md:**
-
-```markdown
-## 1. Implementation
-
-- [ ] 1.1 Create database schema
-- [ ] 1.2 Implement API endpoint
-- [ ] 1.3 Add frontend component
-- [ ] 1.4 Write tests
-```
-
-5. **Create design.md when needed:**
- Create `design.md` if any of the following apply; otherwise omit it:
-
-- Cross-cutting change (multiple services/modules) or a new architectural pattern
-- New external dependency or significant data model changes
-- Security, performance, or migration complexity
-- Ambiguity that benefits from technical decisions before coding
-
-Minimal `design.md` skeleton:
-
-```markdown
-## Context
-
-[Background, constraints, stakeholders]
-
-## Goals / Non-Goals
-
-- Goals: [...]
-- Non-Goals: [...]
-
-## Decisions
-
-- Decision: [What and why]
-- Alternatives considered: [Options + rationale]
-
-## Risks / Trade-offs
-
-- [Risk] → Mitigation
-
-## Migration Plan
-
-[Steps, rollback]
-
-## Open Questions
-
-- [...]
-```
-
-## Spec File Format
-
-### Critical: Scenario Formatting
-
-**CORRECT** (use #### headers):
-
-```markdown
-#### Scenario: User login success
-
-- **WHEN** valid credentials provided
-- **THEN** return JWT token
-```
-
-**WRONG** (don't use bullets or bold):
-
-```markdown
-- **Scenario: User login** ❌
- **Scenario**: User login ❌
-
-### Scenario: User login ❌
-```
-
-Every requirement MUST have at least one scenario.
-
-### Requirement Wording
-
-- Use SHALL/MUST for normative requirements (avoid should/may unless intentionally non-normative)
-
-### Delta Operations
-
-- `## ADDED Requirements` - New capabilities
-- `## MODIFIED Requirements` - Changed behavior
-- `## REMOVED Requirements` - Deprecated features
-- `## RENAMED Requirements` - Name changes
-
-Headers matched with `trim(header)` - whitespace ignored.
-
-#### When to use ADDED vs MODIFIED
-
-- ADDED: Introduces a new capability or sub-capability that can stand alone as a requirement. Prefer ADDED when the change is orthogonal (e.g., adding "Slash Command Configuration") rather than altering the semantics of an existing requirement.
-- MODIFIED: Changes the behavior, scope, or acceptance criteria of an existing requirement. Always paste the full, updated requirement content (header + all scenarios). The archiver will replace the entire requirement with what you provide here; partial deltas will drop previous details.
-- RENAMED: Use when only the name changes. If you also change behavior, use RENAMED (name) plus MODIFIED (content) referencing the new name.
-
-Common pitfall: Using MODIFIED to add a new concern without including the previous text. This causes loss of detail at archive time. If you aren’t explicitly changing the existing requirement, add a new requirement under ADDED instead.
-
-Authoring a MODIFIED requirement correctly:
-
-1. Locate the existing requirement in `openspec/specs/<capability>/spec.md`.
-2. Copy the entire requirement block (from `### Requirement: ...` through its scenarios).
-3. Paste it under `## MODIFIED Requirements` and edit to reflect the new behavior.
-4. Ensure the header text matches exactly (whitespace-insensitive) and keep at least one `#### Scenario:`.
-
-Example for RENAMED:
-
-```markdown
-## RENAMED Requirements
-
-- FROM: `### Requirement: Login`
-- TO: `### Requirement: User Authentication`
-```
-
-## Troubleshooting
-
-### Common Errors
-
-**"Change must have at least one delta"**
-
-- Check `changes/[name]/specs/` exists with .md files
-- Verify files have operation prefixes (## ADDED Requirements)
-
-**"Requirement must have at least one scenario"**
-
-- Check scenarios use `#### Scenario:` format (4 hashtags)
-- Don't use bullet points or bold for scenario headers
-
-**Silent scenario parsing failures**
-
-- Exact format required: `#### Scenario: Name`
-- Debug with: `openspec show [change] --json --deltas-only`
-
-### Validation Tips
-
-```bash
-# Always use strict mode for comprehensive checks
-openspec validate [change] --strict --no-interactive
-
-# Debug delta parsing
-openspec show [change] --json | jq '.deltas'
-
-# Check specific requirement
-openspec show [spec] --json -r 1
-```
-
-## Happy Path Script
-
-```bash
-# 1) Explore current state
-openspec spec list --long
-openspec list
-# Optional full-text search:
-# rg -n "Requirement:|Scenario:" openspec/specs
-# rg -n "^#|Requirement:" openspec/changes
-
-# 2) Choose change id and scaffold
-CHANGE=add-two-factor-auth
-mkdir -p openspec/changes/$CHANGE/{specs/auth}
-printf "## Why\n...\n\n## What Changes\n- ...\n\n## Impact\n- ...\n" > openspec/changes/$CHANGE/proposal.md
-printf "## 1. Implementation\n- [ ] 1.1 ...\n" > openspec/changes/$CHANGE/tasks.md
-
-# 3) Add deltas (example)
-cat > openspec/changes/$CHANGE/specs/auth/spec.md << 'EOF'
-## ADDED Requirements
-### Requirement: Two-Factor Authentication
-Users MUST provide a second factor during login.
-
-#### Scenario: OTP required
-- **WHEN** valid credentials are provided
-- **THEN** an OTP challenge is required
-EOF
-
-# 4) Validate
-openspec validate $CHANGE --strict --no-interactive
-```
-
-## Multi-Capability Example
-
-```
-openspec/changes/add-2fa-notify/
-├── proposal.md
-├── tasks.md
-└── specs/
- ├── auth/
- │ └── spec.md # ADDED: Two-Factor Authentication
- └── notifications/
- └── spec.md # ADDED: OTP email notification
-```
-
-auth/spec.md
-
-```markdown
-## ADDED Requirements
-
-### Requirement: Two-Factor Authentication
-
-...
-```
-
-notifications/spec.md
-
-```markdown
-## ADDED Requirements
-
-### Requirement: OTP Email Notification
-
-...
-```
-
-## Best Practices
-
-### Simplicity First
-
-- Default to <100 lines of new code
-- Single-file implementations until proven insufficient
-- Avoid frameworks without clear justification
-- Choose boring, proven patterns
-
-### Complexity Triggers
-
-Only add complexity with:
-
-- Performance data showing current solution too slow
-- Concrete scale requirements (>1000 users, >100MB data)
-- Multiple proven use cases requiring abstraction
-
-### Clear References
-
-- Use `file.ts:42` format for code locations
-- Reference specs as `specs/auth/spec.md`
-- Link related changes and PRs
-
-### Capability Naming
-
-- Use verb-noun: `user-auth`, `payment-capture`
-- Single purpose per capability
-- 10-minute understandability rule
-- Split if description needs "AND"
-
-### Change ID Naming
-
-- Use kebab-case, short and descriptive: `add-two-factor-auth`
-- Prefer verb-led prefixes: `add-`, `update-`, `remove-`, `refactor-`
-- Ensure uniqueness; if taken, append `-2`, `-3`, etc.
-
-## Tool Selection Guide
-
-| Task | Tool | Why |
-| --------------------- | ---- | ------------------------ |
-| Find files by pattern | Glob | Fast pattern matching |
-| Search code content | Grep | Optimized regex search |
-| Read specific files | Read | Direct file access |
-| Explore unknown scope | Task | Multi-step investigation |
-
-## Error Recovery
-
-### Change Conflicts
-
-1. Run `openspec list` to see active changes
-2. Check for overlapping specs
-3. Coordinate with change owners
-4. Consider combining proposals
-
-### Validation Failures
-
-1. Run with `--strict` flag
-2. Check JSON output for details
-3. Verify spec file format
-4. Ensure scenarios properly formatted
-
-### Missing Context
-
-1. Read project.md first
-2. Check related specs
-3. Review recent archives
-4. Ask for clarification
-
-## Quick Reference
-
-### Stage Indicators
-
-- `changes/` - Proposed, not yet built
-- `specs/` - Built and deployed
-- `archive/` - Completed changes
-
-### File Purposes
-
-- `proposal.md` - Why and what
-- `tasks.md` - Implementation steps
-- `design.md` - Technical decisions
-- `spec.md` - Requirements and behavior
-
-### CLI Essentials
-
-```bash
-openspec list # What's in progress?
-openspec show [item] # View details
-openspec validate --strict --no-interactive # Is it correct?
-openspec archive <change-id> [--yes|-y] # Mark complete (add --yes for automation)
-```
-
-Remember: Specs are truth. Changes are proposals. Keep them in sync.
+++ /dev/null
-# Project Context
-
-## Purpose
-
-The e-Mobility Charging Stations Simulator provides a scalable, configurable load and behavior simulator for sets of EV charging stations speaking the OCPP-J protocol (1.6 and partially 2.0.x). It is used for functional testing, performance/load testing, integration validation, and experimentation within SAP e-Mobility and for community contributors. It emulates station lifecycle, transactions, firmware flows, metering, statistics and supervision URL dynamics.
-
-## Tech Stack
-
-- Runtime: Node.js (>=22.0.0) + Worker Threads
-- Language: TypeScript (~5.9) (ESM modules; `type: module`)
-- Build: esbuild bundling (custom scripts) + PNPM workspaces
-- Package Manager: pnpm (>=9)
-- Testing: Native Node test runner (`node --test`) + `@std/expect` assertions + c8 coverage
-- Linting: ESLint flat config with TypeScript strict type checking, jsdoc, perfectionist, vue, cspell, neostandard style
-- Formatting: Prettier (printWidth 100, singleQuote, no semicolons, trailingComma es5)
-- UI: Vue-based Web UI (under `ui/web`) communicating via HTTP or WebSocket SRPC protocol
-- Protocol Simulation: OCPP-J 1.6 (core + profiles) and partial 2.0.x; JSON Schema validation (ajv + ajv-formats)
-- Mock OCPP 2.0.x server: Python (>=3.11), Poetry (>=2) (under `tests/ocpp-server`)
-- Concurrency & Pools: Worker Threads + `poolifier` for dynamic/fixed/workerSet strategies
-- Persistence / Storage: Optional performance storage (JSON file / MongoDB) + Mikro-ORM (MariaDB / SQLite drivers available) for entity modeling if enabled
-- Logging: winston + winston-daily-rotate-file (structured, rotating logs)
-- Utilities: date-fns, chalk, mnemonist, ws, tar
-- CI/CD & Releases: GitHub Actions (lint/test/build/codeql/release-please) + release-please automation
-
-## Project Conventions
-
-### Code Style
-
-- Source: TypeScript with strict type checking (typescript-eslint strictTypeChecked + stylisticTypeChecked).
-- Naming: camelCase for variables/functions; PascalCase for classes/interfaces/enums/types; UPPER_SNAKE_CASE for constants where applicable; exact OCPP enumeration names.
-- Imports: ESM `import` syntax, relative paths kept short; avoid default exports except where single primary module.
-- Formatting: Prettier enforced (printWidth 100, singleQuote=true, semi=false, trailingComma=es5, arrowParens=avoid). Auto-run via lint-staged on committed files.
-- Lint: ESLint flat config; no lint errors permitted in CI. Spellchecking via cspell plugin for domain-specific terms.
-- Avoid `any`; prefer explicit types, discriminated unions, and type guards. Optional chaining (`?.`) + nullish coalescing (`??`) for safety.
-- Errors: Use `BaseError` and `OCPPError` in OCPP stack for structured error handling; include contextual properties.
-- Logging: Use `Logger` utility wrapping winston; correct severity (error>warn>info>debug). No console.log in committed code.
-- Immutability: Avoid shared mutable state; configuration objects cloned before modification.
-- No non-English terms in code, docs, comments, logs.
-
-### Architecture Patterns
-
-- Modular layering around `ChargingStation`, `ChargingStationWorker`, and OCPP services (`src/charging-station/ocpp/<version>/`).
-- Worker abstraction: Strategy-based selection (`workerSet`, `fixedPool`, `dynamicPool`) leveraging `poolifier` + custom worker management in `worker/` directory.
-- Configuration hierarchy (template → generated station config → runtime overrides) with automatic reload watchers.
-- Protocol handling: Separation of request/response services per OCPP version; strict validation via ajv when `ocppStrictCompliance` enabled.
-- SRPC UI protocol over WebSocket/HTTP with procedure dispatch and correlation using UUID.
-- Broadcasting & async coordination: Broadcast channels / message maps for pending requests resolution.
-- Performance statistics subsystem pluggable storage backend (`none|jsonfile|mongodb`).
-- Persistence model optionally via Mikro-ORM (entities compiled with dedicated tsconfig).
-- Single source of truth for tunables: canonical defaults defined in config templates; merging precedence defaults < template < station config < runtime options.
-- Separation of domain (charging stations simulation) from infrastructure (logging, storage, worker pools, UI server).
-
-### Testing Strategy
-
-- Test framework: Native Node test runner (`node --test`) invoked through glob; assertions via `@std/expect`.
-- Coverage: c8 with lcov & html reports; thresholds enforced indirectly through CI review (no explicit thresholds currently documented).
-- Test scope: Unit tests for utilities, configuration handling, errors, OCPP services behaviors, worker utilities, performance statistics calculations.
-- Determinism: Randomness minimized or parameterized; probability-based features (ATG) tested with controlled inputs.
-- No flaky tests accepted; asynchronous tests await promises explicitly.
-- New behavior: Add minimal tests before or alongside implementation; refactoring requires test stability.
-
-### Git Workflow
-
-- Branching model: `main` for active development; maintenance branches `vX` (major) and `vX.Y` (minor) for released lines; feature / experiment branches should be: `feat/<concise-topic>`, `exp/<strategy-or-reward-param>`; fix branches should be: `fix/<bug>`..
-- Commits follow Conventional Commits and validated by commitlint (`@commitlint/config-conventional`).
-- Pre-commit hooks (husky): Lint & formatting (lint-staged) + commit message validation.
-- PR process: CI (lint, type-check, tests, build) + CodeQL security analysis; release-please manages automated versioning/changelogs.
-- Merge strategy: Squash or regular merges allowed (follow repository settings); maintain clear atomic changes.
-
-## Domain Context
-
-- Focus: Simulating large fleets of EV charging stations speaking OCPP-J for integration and load testing of CSMS (Charge Station Management Systems) and related services.
-- Dual OCPP stack for OCPP-J 1.6 and 2.0.1.
-- Automatic Transaction Generator (ATG): Probabilistic simulation of charging sessions with configurable durations, delays, authorization flows, connector affinity.
-- Configuration templates define station capabilities (power, connectors, firmware version patterns, metering, etc.).
-- UI protocol: Procedural control (start/stop simulator/stations, add/delete, trigger OCPP commands, manage ATG) via HTTP or WebSocket SRPC.
-- Performance metrics: Collect & optionally persist statistics to analyze throughput, latencies, resource usage.
-
-## Important Constraints
-
-- Node.js >=22.0.0 runtime features (Worker Threads, ESM) required.
-- Strict OCPP JSON schema validation when `ocppStrictCompliance` is true; deviations require explicit config relaxation (e.g., out-of-order meter values).
-- Simulator must avoid blocking operations in worker threads; heavy tasks delegated or streamed.
-- Memory footprint scalability: workerSet auto sizing formula ensures balanced distribution.
-- Security: No real credentials beyond optional supervision basic auth; avoid storing sensitive PII; logs sanitized (RFID tags considered test data only).
-- Licensing: Apache-2.0; contributions must respect REUSE compliance (license headers / metadata).
-- Configuration reload only for designated file sets; persisted station-specific states preserved where specified.
-
-## External Dependencies
-
-- OCPP Server(s): Supervision URLs provided (external CSMS endpoints) for protocol interactions.
-- Performance Storage: Optional MongoDB instance (via URI) or JSON file storage; may require external service.
-- Databases: MariaDB / SQLite (via Mikro-ORM) if enabled for extended persistence (currently optional paths).
-- Logging: File system (rotating log files) + optional console; no external log aggregator baked in.
-- Release Automation: GitHub Release Please (GitHub API).
-
-## Glossary / Key Concepts
-
-- Supervision URL: Target URL(s) for station-server OCPP communications.
-- Station Template: Parameterized JSON blueprint for generating multiple station instances.
-- HashId: Unique identifier per simulated station (derived/persistent across restarts).
-- ATG: Automatic Transaction Generator component that drives simulated charging sessions.
-- SRPC: Simple Remote Procedure Call used for UI control over WebSocket/HTTP.
-
-## Configuration Precedence & Mutation
-
-1. Template (`src/assets/station-templates/*.json`)
-2. Generated station config (`dist/assets/configurations/<hashId>.json`)
-3. Runtime procedure overrides (UI protocol commands)
-
-Persisted sections (e.g., configurationKey subset, ATG statuses) are retained across template changes unless explicitly regenerated.
-
-## Quality Gates
-
-- Lint (ESLint) passes with no errors; warnings minimized (spellchecker may auto-fix).
-- Type checking (tsc / typescript-eslint project service) succeeds.
-- Tests pass with stable coverage; new code paths covered.
-- Prettier formatting enforced.
-- Conventional Commit messages validated.
-- Release automation validation (release-please) on version bumps.
-
-## Spec Authoring Guidance (OpenSpec Alignment)
-
-- New behavior or capabilities require change proposal prior to implementation (see `openspec/AGENTS.md`).
-- Bug fixes do not require proposals if restoring documented behavior.
-- Requirements wording uses SHALL/MUST for normative statements; include at least one Scenario per Requirement.
-- Keep architecture changes minimal (<100 LOC) unless justified by scaling/performance data.
-
-## Maintenance & Evolution
-
-- Incremental expansion of OCPP 2.0.x coverage guided by real integration needs.
-- Performance tuning informed by collected statistics; complexity added only if baseline insufficient.
-- Backward compatibility for public procedure names and configuration keys unless marked BREAKING in a proposal.
-
-## Non-Goals
-
-- Real hardware control or physical charging operations.
-- Proprietary protocol extensions beyond generic vendor key handling.
-
-## Observability & Metrics
-
-- Log-based statistics at configurable intervals (`log.statisticsInterval`).
-- Optional persisted performance storage for offline analysis.
-
-## Security Considerations
-
-- Basic Auth credentials if provided stored only in config JSON; avoid committing secrets.
-- WebSocket/HTTP UI server authentication optional; disabled by default—enable for controlled environments.
-- No dynamic code execution from untrusted input; JSON schemas guard payload structure.
-
-## Extensibility Points
-
-- Add new OCPP commands by extending versioned service modules and updating template command support maps.
-- Introduce new worker strategies via `worker/` abstractions (proposal if architectural change).
-- Add new performance storage backends by extending storage interface (ensure configuration validation).
-- UI procedures: Add procedure name + handler; document in README and project spec.
-
-## External Integration Scenarios
-
-- Load testing against a CSMS: Generate N stations with variable power/connectors; start ATG to create transactions.
-- Firmware upgrade simulation: Use `firmwareUpgrade` template section to emulate version step and reset behavior.
-- Dynamic supervision URL switching: Use procedure to set new URL across station fleet.
-
-## Risks & Mitigations
-
-- Risk: Overloading system resources with too many stations → Mitigation: auto sizing & configurable pool limits.
-- Risk: Schema drift in OCPP support → Mitigation: JSON schema validation toggled via strict compliance flag.
-- Risk: Incomplete OCPP 2.0.x stack leading to false assumptions → Mitigation: Explicit README note and spec separation per version.
-- Risk: Log volume & rotation issues → Mitigation: Daily rotation + configurable maxFiles/maxSize.
-
-## Change Process Summary
-
-- Use verb-led change IDs (add-/update-/refactor-/remove-) for proposals.
-- Validate proposals with `openspec validate --strict` before implementation.
-- Archive after deployment; keep specs authoritative.
repositories / e-mobility-charging-stations-simulator.git / commitdiff
