Skill

Reconciling Changes

Analyse what changed in docs/technical/, map impact to code and tests, and define frozen scope before edits.

// workflow;

Behaviour

What it does

Establishes a baseline from the last plan, git tag, or CHANGELOG.md entries
Classifies each doc change as ADD, MODIFY, REMOVE, or CLARIFY
Maps affected REQ-IDs to files, modules, and existing tests
Defines frozen scope: areas that must not change in the delta
Writes an impact report to docs/plans/ for your approval
Hands off to planning in delta mode only after you approve the report

When to use

Good fits

After updating requirements or technical docs on an existing app

Before planning a brownfield delta

When you need to know what a spec change will touch before code changes

Skip on greenfield work; go straight to planning instead

Development harness

Step 4 of 8 · Change control

Part of the design-to-ship pipeline: brainstorming → technical-documentation → conformance-check → reconciling-changes → planning → project-setup → executing-plans → shipping. Install the full set for structured feature work.

Test-Driven Development End-to-End Testing Component Development Component Testing

Conformance Check Planning

Install

Get this skill

Uses Agent Kit via npx; no global install required.

Quick install

npx @levi-putna/agent-kit@latest add levi-putna/skills --skill reconciling-changes

Global (Cursor)

npx @levi-putna/agent-kit@latest add levi-putna/skills --skill reconciling-changes --global --agent cursor

Global (Claude)

npx @levi-putna/agent-kit@latest add levi-putna/skills --skill reconciling-changes --global --agent claude

Project install

npx @levi-putna/agent-kit@latest add levi-putna/skills --skill reconciling-changes --project

Interactive install

npx @levi-putna/agent-kit@latest add levi-putna/skills

Uninstall

npx @levi-putna/agent-kit@latest remove reconciling-changes

Example

Example prompt