openspec-sync-specslisted

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. **Resolve change context** Run: ```bash openspec status --change "<name>" --json ``` If status reports `actionContext.mode: "workspace-planning"`, explain that workspace spec sync is not supported in this slice and STOP. Do not fall back to repo-local paths or edit linked repos. 3. **Find delta specs** Use `artifactPaths.specs.existingOutputPaths` from the status JSON as the list of delta spec files. 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