6aspec 2.0.0-dev.2 → 2.0.0-dev.22

package/.claude/commands/opsx/verify.md

@@ -0,0 +1,164 @@
+---
+name: "OPSX: Verify"
+description: Verify implementation matches change artifacts before archiving
+category: Workflow
+tags: [workflow, verify, experimental]
+---
+
+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"

package/.claude/settings.local.json

@@ -2,7 +2,27 @@
   "permissions": {
     "allow": [
       "Bash(ls -la .claude/commands/6aspec/green/*.md)",
-      "Bash(xargs -I {} basename {})"
+      "Bash(xargs -I {} basename {})",
+      "Bash(git mv 6A_constitution.md green_constitution.md)",
+      "Bash(git mv 6A_design_sop.md green_design_sop.md)",
+      "Bash(git mv 6A_import_model_table_sop.md green_import_model_table_sop.md)",
+      "Bash(git mv 6A_init_event_list_sop.md green_init_event_list_sop.md)",
+      "Bash(git mv 6A_init_map_sop.md green_init_map_sop.md)",
+      "Bash(git mv 6A_model_sop.md green_model_sop.md)",
+      "Bash(git mv 6A_new_sop.md green_new_sop.md)",
+      "Bash(git mv 6A_rollback_sop.md green_rollback_sop.md)",
+      "Bash(git mv 6A_visual_logic_sop.md green_visual_logic_sop.md)",
+      "Bash(git mv 6A_code_implementation_sop.md green_code_implementation_sop.md)",
+      "Bash(git mv 6A_archive_sop.md green_archive_sop.md)",
+      "Bash(git mv 6A_continue_sop.md green_continue_sop.md)",
+      "Bash(git mv 6A_tasks_sop.md green_tasks_sop.md)",
+      "Bash(git mv 6A_clarify_sop.md green_clarify_sop.md)",
+      "Bash(git mv 6A_status_sop.md green_status_sop.md)",
+      "Bash(ls -la .6aspec/rules/green/6A_*.md)",
+      "Bash(xargs sed -i '' 's/6A_\\\\\\([a-z_]*\\\\\\)\\\\.md/green_\\\\1.md/g')",
+      "Bash(openspec --help)",
+      "Bash(openspec schemas --json 2>/dev/null | head -100)",
+      "Bash(openspec status --json 2>/dev/null | head -50)"
     ]
   }
 }

package/.cursor/commands/6aspec/brown/explore.md

@@ -0,0 +1,11 @@
+---
+name: "6aspec:brown: Explore"
+description: 前期探索（轻量级流程可选）
+category: Workflow
+tags: [workflow, explore, lightweight, brownfield]
+---
+
+1. Immediate response upon activation: brown field requirement workflow - **Explore** has been activated
+2. **Read and strictly follow the brown field constitution**: `.6aspec/rules/brown/brown_constitution.md`
+3. Read file: `.6aspec/rules/brown/brown_explore_sop.md`
+4. Strictly follow the SOP defined in that file

package/.cursor/commands/6aspec/green/archive.md

@@ -4,6 +4,6 @@ alwaysApply: false
 ---
 
 1. Immediate response upon activation: archive workflow has been activated
-2. Read file: `.6aspec/rules/green/6A_archive_sop.md`
+2. Read file: `.6aspec/rules/green/green_archive_sop.md`
 3. Strictly follow the "Archive Workflow SOP" defined in that file
 4. Archive the completed requirement

package/.cursor/commands/6aspec/green/clarify.md

@@ -4,11 +4,11 @@ alwaysApply: false
 ---
 
 1. Immediate response upon activation: clarify workflow has been activated
-2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/6A_constitution.md`
+2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/green_constitution.md`
 3. **Context Restriction**: 
    - Do NOT perform `codebase_search`.
    - Do NOT read any files unless they are explicitly provided by the user (via '@') or explicitly listed in the SOP steps.
    - Stop and ask the user if you think you need more information.
-4. Read file: `.6aspec/rules/green/6A_clarify_sop.md`
+4. Read file: `.6aspec/rules/green/green_clarify_sop.md`
 5. Strictly follow the "Requirement Clarification SOP" defined in that file
 6. Update the requirement document with clarified details

package/.cursor/commands/6aspec/green/continue.md

@@ -4,6 +4,6 @@ alwaysApply: false
 ---
 
 1. Immediate response upon activation: continue workflow has been activated
-2. Read file: `.6aspec/rules/green/6A_continue_sop.md`
+2. Read file: `.6aspec/rules/green/green_continue_sop.md`
 3. Strictly follow the "Continue Workflow SOP" defined in that file
 4. Automatically execute the next step based on current status

package/.cursor/commands/6aspec/green/design.md

@@ -3,7 +3,7 @@ description: design workflow
 alwaysApply: false
 ---
 1. Immediate response upon activation: design workflow has been activated.
-2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/6A_constitution.md`
-3. Read file: `.6aspec/rules/green/6A_design_sop.md`
+2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/green_constitution.md`
+3. Read file: `.6aspec/rules/green/green_design_sop.md`
 4. Strictly follow the "New Feature Architecture SOP" defined in that file.
 5. Output the Technical Design Document (TDD).

package/.cursor/commands/6aspec/green/{execute-task.md → implement.md}

@@ -11,7 +11,7 @@ alwaysApply: false
 当用户提供一个任务文件路径（如 `@task_01_api_xxx.md`）并要求“执行任务”时：
 
 1.  **激活角色**：切换至 `Senior Developer` 角色。
-2.  **调用 SOP**：严格遵循 `.6aspec/rules/green/6A_code_implementation_sop.md` 中的协议。
+2.  **调用 SOP**：严格遵循 `.6aspec/rules/green/green_code_implementation_sop.md` 中的协议。
     - **Step 0**: 上下文加载 (Task + TDD + Rules)
     - **Step 1**: 自底向上编码 (DTO -> Repo -> Service -> API)
     - **Step 2**: 质量检查 (Lint)

package/.cursor/commands/6aspec/green/import-model-table.md

@@ -3,7 +3,7 @@ description: import-model-table workflow
 alwaysApply: false
 ---
 1. Immediate response upon activation: import-model-table workflow has been activated
-2. Read file: `.6aspec/rules/green/6A_import_model_table_sop.md`
+2. Read file: `.6aspec/rules/green/green_import_model_table_sop.md`
 3. Strictly follow the "Import Model Table SOP" defined in that file
 4. Execute the python script to import entities
 

package/.cursor/commands/6aspec/green/init.md

@@ -5,11 +5,11 @@ alwaysApply: false
 Immediate response upon activation: Project Artifacts Initialization workflow has been activated.
 
 Phase 1: Functional Capability Map
-1. Read file: `.6aspec/rules/green/6A_init_map_sop.md`
+1. Read file: `.6aspec/rules/green/green_init_map_sop.md`
 2. Strictly follow the "Init Functional Capability Map SOP" defined in that file.
 3. Execute the codebase scan and update the artifact at `.6aspec/biz/functional-capability-Map.md`.
 
 Phase 2: Event List
-1. Read file: `.6aspec/rules/green/6A_init_event_list_sop.md`
+1. Read file: `.6aspec/rules/green/green_init_event_list_sop.md`
 2. Strictly follow the "Event List Generation SOP" defined in that file.
 3. Execute the codebase scan and update the artifact at `.6aspec/biz/event-list.md`.

package/.cursor/commands/6aspec/green/model.md

@@ -3,11 +3,11 @@ description: model workflow
 alwaysApply: false
 ---
 1. Immediate response upon activation: model workflow has been activated
-2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/6A_constitution.md`
+2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/green_constitution.md`
 3. **Context Restriction**: 
    - Do NOT perform `codebase_search`.
    - Do NOT read any files unless they are explicitly provided by the user (via '@') or explicitly listed in the SOP steps.
    - Stop and ask the user if you think you need more information.
-4. Read file: `.6aspec/rules/green/6A_model_sop.md`
+4. Read file: `.6aspec/rules/green/green_model_sop.md`
 5. Strictly follow the "Domain modeling and database design Architecture SOP" defined in that file
 6. Output the Domain model and table design

package/.cursor/commands/6aspec/green/new.md

@@ -4,11 +4,11 @@ alwaysApply: false
 ---
 
 1. Immediate response upon activation: new feature workflow has been activated
-2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/6A_constitution.md`
+2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/green_constitution.md`
 3. **Context Restriction**: 
    - Do NOT perform `codebase_search`.
    - Do NOT read any files unless they are explicitly provided by the user (via '@') or explicitly listed in the SOP steps.
    - Stop and ask the user if you think you need more information.
-4. Read file: `.6aspec/rules/green/6A_new_sop.md`
+4. Read file: `.6aspec/rules/green/green_new_sop.md`
 5. Strictly follow the "New Feature Requirement SOP" defined in that file
 6. Output the structured requirement document

package/.cursor/commands/6aspec/green/rollback.md

@@ -4,6 +4,6 @@ alwaysApply: false
 ---
 
 1. Immediate response upon activation: rollback workflow has been activated
-2. Read file: `.6aspec/rules/green/6A_rollback_sop.md`
+2. Read file: `.6aspec/rules/green/green_rollback_sop.md`
 3. Strictly follow the "Rollback SOP" defined in that file
 4. **Do not** perform any file deletion or status file update until the user has explicitly confirmed (e.g. "确认回退" or "执行回退")

package/.cursor/commands/6aspec/green/status.md

@@ -4,6 +4,6 @@ alwaysApply: false
 ---
 
 1. Immediate response upon activation: status workflow has been activated
-2. Read file: `.6aspec/rules/green/6A_status_sop.md`
+2. Read file: `.6aspec/rules/green/green_status_sop.md`
 3. Strictly follow the "Status Query SOP" defined in that file
 4. Output the current status and progress

package/.cursor/commands/6aspec/green/tasks.md

@@ -3,7 +3,7 @@ description: tasks workflow
 alwaysApply: false
 ---
 1. Immediate response upon activation: tasks workflow has been activated
-2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/6A_constitution.md`
-3. Read file: `.6aspec/rules/green/6A_tasks_sop.md`
+2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/green_constitution.md`
+3. Read file: `.6aspec/rules/green/green_tasks_sop.md`
 4. Strictly follow the "Task Decomposition SOP" defined in that file
 5. Output the task list

package/.cursor/commands/6aspec/green/visual-logic.md

@@ -3,8 +3,8 @@ description: visual-logic workflow
 alwaysApply: false
 ---
 1. Immediate response upon activation: visual-logic workflow has been activated.
-2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/6A_constitution.md`
-3. Read file: `.6aspec/rules/green/6A_visual_logic_sop.md`.
+2. **You must first read and strictly abide by the principles in the constitutional documents**：`.6aspec/rules/green/green_constitution.md`
+3. Read file: `.6aspec/rules/green/green_visual_logic_sop.md`.
 4. Strictly follow the "Visual Logic Diagrams SOP" defined in that file.
 5. Output Mermaid diagrams as specified in the SOP.
 

package/.cursor/commands/opsx-apply.md

@@ -0,0 +1,152 @@
+---
+name: /opsx-apply
+id: opsx-apply
+category: Workflow
+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! You can archive this change with `/opsx:archive`.
+```
+
+**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

package/.cursor/commands/opsx-archive.md

@@ -0,0 +1,157 @@
+---
+name: /opsx-archive
+id: opsx-archive
+category: Workflow
+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