reconcile-delta

Reconcile delta implementations into long-lived feature documentation.

1|1|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/asermax/claude-plugins --skill reconcile-delta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reconcile-delta
Source: https://github.com/asermax/claude-plugins/tree/main/katachi/skills/reconcile-delta
Command: npx skills add https://github.com/asermax/claude-plugins --skill reconcile-delta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile delta implementations into the long-lived feature documentation to keep specs, designs, and plans aligned with actual code changes.

Core Features & Use Cases

  • Provide a repeatable workflow to update feature-specs, feature-designs, and delta-docs based on completed delta implementations.
  • Silently gather delta context, compare against planned impacts, and draft updates to feature documentation.
  • Trace decisions and surface ADR/DES candidates when cross-cutting changes are detected.

Quick Start

Run the reconciliation workflow on a completed delta to update the living feature documentation.

Frequently Asked Questions about reconcile-delta

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

FAQPage Schema
What is feature documentation reconciliation after a delta implementation?

Feature documentation reconciliation is the process of updating long-lived feature specs and designs to align with actual delta-driven code changes. It compares completed delta implementations against planned impacts and traces decisions to keep living docs accurate.

How do I update feature specs and designs after completing a delta implementation?

Run the reconciliation workflow on your completed delta to automatically gather context, compare against planned impacts, and draft updates to feature-specs and feature-designs. The workflow ensures living feature documentation reflects actual code changes.

When do I need to reconcile delta workflows with feature documentation?

You need to reconcile delta workflows when completed delta implementations introduce changes that affect existing feature-specs, feature-designs, or implementation plans, ensuring living documentation stays aligned with actual code and decisions are traced.

Does the reconciliation workflow handle cross-cutting changes across feature designs?

Yes, the reconciliation workflow detects cross-cutting changes during impact analysis and surfaces ADR or DES candidates, tracing decisions with references to delta documents to keep feature designs and specs aligned with actual code changes.

What's the best way to trace decisions during delta reconciliation?

The best way to trace decisions during delta reconciliation is to run the workflow that automatically surfaces ADR and DES candidates when cross-cutting changes are detected, providing references to delta documents for updated feature documentation.

Can I use delta reconciliation for implementation plans and delta specs?

Yes, delta reconciliation applies to delta-driven changes across features, delta specs, delta designs, and implementation plans, guiding the reconciliation workflow to update living feature documentation based on completed delta implementations.