Sync delta specs from a change to main specs and refresh the implementing repos/modules' local SPEC.md files.

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 openspec-sync-specs (e.g., openspec-sync-specs add-auth). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Steps

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) or pending local SPEC.md updates recorded in their artifacts.

IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.
Find delta specs

Recursively find spec.md files under openspec/changes/<name>/specs/. Include both specs/<capability>/spec.md and specs/<domain>/<capability>/spec.md (and deeper domain paths). Ignore a spec.md directly in the specs/ root. The capability ID is the full relative directory path, such as identity/authentication, not just authentication.