cc-switch-web: Skill for Claude Code

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.

When archive guidance discusses embedded sync or artifact write-back, treat openspec/config.yaml as the compact source of truth and follow the shared prompt/runtime projection contract rather than reinterpreting raw config keys inside the template body.

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. Unified Full Verify Gate

   Run the CLI gate:

   openspec verify status "<change-name>" --json
   

Verify Result Freshness Rules:

A verify result is considered FRESH if ALL of the following hold:

• .verify-result.json exists in the change directory
• verificationContext.evidenceFingerprint matches the current workspace fingerprint
• verificationContext.contractVersion is "1.0"
• result is PASS or PASS_WITH_WARNINGS

A verify result is considered STALE if ANY of the following hold:

• verificationContext.evidenceFiles is missing or the file list changed
• verificationContext.evidenceFingerprint does not match the recomputed fingerprint
• verificationContext.gitHeadCommit does not match the current HEAD (if recorded)
• verificationContext.contractVersion is missing or not "1.0"
• result is not PASS or PASS_WITH_WARNINGS

Optimization metadata compatibility:

• optimization metadata is advisory for archive gating, not part of the freshness hash inputs
• Legacy verify results without optimization may still be fresh if every freshness rule above passes
• If optimization.status exists, evaluate its acceptability separately from freshness

When verify result is STALE or MISSING:

• Archive MUST execute full verify before continuing
• Do NOT attempt to repair or reuse a stale verify result

Fingerprint Computation:

• Sort evidenceFiles alphabetically before hashing
• For each evidence file, collect normalized relative POSIX path + content hash
• Hash the JSON-serialized entries with SHA-256
• Use path.join(), path.resolve(), and path.normalize() for all path handling
• Persist evidenceFiles as relative POSIX paths for cross-platform comparison

Verify State Machine:

Phase 1 PASS / PASS_WITH_WARNINGS
  |
  v
PENDING_VERIFICATION
  |-- no affectedFileHashes --> Phase 2 optimization analysis
  |                              |-- NO_OPTIMIZATION_NEEDED --> NOT_NEEDED
  |                              |-- SKIPPED / optimization.enabled=false --> SKIPPED
  |-- affectedFileHashes ------> PENDING_VERIFICATION (optimization proposed)
                                 |-- verification PASS --> IMPROVED
                                 |-- verification FAIL_NEEDS_REMEDIATION --> retry or DEGRADED
                                 |-- retries exhausted --> DEGRADED

Archive gate accepts: SKIPPED | NOT_NEEDED | IMPROVED | DEGRADED
Archive gate rejects: PENDING_VERIFICATION | ABORTED_UNSAFE

Verify CLI JSON Schema Reference:

CLI call	--input JSON
openspec verify phase1 "<change-name>" --input '<json>' --json	{"result":"PASS","issues":[],"evidenceFiles":["..."],"executionMode":"..."}
openspec verify phase2 "<change-name>" --type=optimization --input '<json>' --json	{"status":"NO_OPTIMIZATION_NEEDED","summary":"..."} (summary is required, must be non-empty)
openspec verify phase2 "<change-name>" --type=optimization --files "<affected-files>" --input '<json>' --json	{"status":"OPTIMIZATION_PROPOSED","summary":"..."}
openspec verify phase2 "<change-name>" --type=optimization --input '<json>' --json	{"status":"SKIPPED"}
openspec verify phase2 "<change-name>" --type=verification --input '<json>' --json	{"result":"PASS","issues":[]}
openspec verify phase2 "<change-name>" --type=verification --input '<json>' --json	{"result":"FAIL_NEEDS_REMEDIATION","issues":[...],"behaviorRetryCounter":N}