spec-driven-extended-reconcile

Reconcile stage outputs against Intake and existing artifacts in spec-driven workflows.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/kxnzee/multi-repo-specs --skill spec-driven-extended-reconcile-kxnzee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-extended-reconcile
Source: https://github.com/kxnzee/multi-repo-specs/tree/main/extensions/spec-driven-extended/skills/spec-driven-extended-reconcile
Command: npx skills add https://github.com/kxnzee/multi-repo-specs --skill spec-driven-extended-reconcile-kxnzee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stage outputs in a spec-driven change workflow can drift out of sync with the Intake record and previously accepted artifacts, leaving stale conclusions, contradictions, and unresolved questions that undermine planning and acceptance. ## Core Features & Use Cases - Mandatory post-stage reconciliation: Runs before completing Intake, Explore, Proposal, Specs, Design, Tasks, each Apply task, and Verify to compare findings against Intake and existing artifacts. - Controlled updates or conflict escalation: Updates stale conclusions in their primary section with a brief rationale, or returns semantic conflicts to Planning instead of bending requirements to fit implementation. - Review mode: Returns findings to the calling workflow without editing any files, listing exact sections that need correction. - Use Case: After the Design stage of a change, an agent notices a conclusion contradicts the accepted Intake scope; the skill updates the stale statement with its basis and revision stage, or escalates the conflict back to Planning for the owner. ## Quick Start Ask the agent to reconcile the outputs of the current stage for a given change ID against Intake and existing artifacts in update or review mode.

Frequently Asked Questions about spec-driven-extended-reconcile

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

FAQPage Schema
How do I keep spec-driven change artifacts consistent after each stage?▼

Run the reconciliation step before completing each stage. It compares current stage findings against the Intake record and existing artifacts, updates confirmed stale conclusions in place, and records the basis and revision stage next to each correction.

What is the difference between update and review mode in artifact reconciliation?▼

Update mode edits stale conclusions directly in their primary section and closes permitted questions. Review mode edits no files at all and instead returns findings with exact section references to the calling workflow.

Can reconciliation run without MCP access to OpenSpec?▼

Yes. If MCP is unavailable, the same instructions can be obtained through the standard OpenSpec CLI in an explicitly selected Store. It does not permit guessing the Store or bypassing access restrictions.

When should a conflict be returned to Planning instead of updating artifacts?▼

Return a conflict when a new business decision or a change to accepted scope appears, especially during Apply or Verify. The skill stops affected work and escalates rather than adjusting requirements to match the implementation.

What are the limitations of the reconciliation step?▼

It does not launch the next stage, replace requirements validation or acceptance, run new code research, builds, or tests, and never modifies configuration, Master Specs, code, task checkboxes, or service records.