openspec-extend-change

Extends existing OpenSpec change artifacts with new requirements, review findings, or verify reports.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill openspec-extend-change-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-extend-change
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/openspec-extend-change
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill openspec-extend-change-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an in-flight OpenSpec change request needs new requirements, review findings, debug/RCA results, or verification feedback incorporated, this Skill updates the change artifacts (proposal, design, specs, tasks, debug log) in a controlled way without touching BSL code or XML metadata. ## Core Features & Use Cases - Two operating modes: user-extend shows a brief and waits for confirmation; repair-from-verify runs silently inside the verify repair loop. - Source classification: ingests review reports, debug/RCA files, verify reports, architecture reports, and explore handoffs via --from-* flags, plus a --code-sync mode to align artifacts with actual code. - Scope coherence gates: drift-check classification (pass / drift-warning / scope-violation) and architect delegation when scope creep or acceptance loops are detected. - Use Case: After a code review flags architecture findings on an active change, run the extend command with the review report to update the design and tasks, then hand off to verification. ## Quick Start Ask the assistant to extend the current OpenSpec change with the findings from your review report file.

Frequently Asked Questions about openspec-extend-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add new requirements to an existing OpenSpec change?

Run the extend command with the change name and the new requirement text or a source file. The skill shows a brief describing the proposed artifact updates and waits for your confirmation before editing proposal, design, specs, or tasks.

How to incorporate code review findings into a change request?

Pass the review report with the --from-review flag. The skill classifies findings, extracts dispositions and architecture issues, and updates the change artifacts after you confirm the brief.

Does openspec-extend-change modify BSL code or XML metadata?

No. It only edits OpenSpec change artifacts such as proposal.md, design.md, specs, tasks.md, and debug.md. Code implementation remains the responsibility of the apply command, and writer or reviewer agents are never invoked.

What is the difference between user-extend and repair-from-verify modes?

User-extend shows a brief and requires confirmation before editing artifacts. Repair-from-verify is triggered internally by the verify repair loop, skips the brief and chat output, and applies remediation directly from the verification report.

When does the skill trigger an architect review during extend?

An architect is called when the drift-check shows drift-warning or scope-violation, when three or more extends occurred without architect involvement, when an acceptance loop is detected, or when changes affect extension points, contracts, or multiple files.