deltas

Extract numbered deltas from a vision document into DELTAS.md inventory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracting and organizing deltas from a project vision can be error-prone and time-consuming. This skill standardizes the process, ensuring traceability from vision to a numbered delta inventory.

Core Features & Use Cases

  • Delta extraction from the project vision into a structured inventory (e.g., DELTAS.md).
  • State tracking and validation via an agent-driven review cycle.
  • Iterative refinement, numbering, and documentation to support planning workflows.

Quick Start

Review the current vision document at docs/planning/VISION.md and extract all deltas into docs/planning/DELTAS.md.

Frequently Asked Questions about deltas

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

FAQPage Schema
How do I extract deltas from a project vision document for planning workflows?

To extract deltas from a project vision, review your vision document and map actionable sections into a structured, numbered delta inventory. This ensures traceability from vision to task scoping and cross-team validation.

What is a delta inventory and how does it support traceability?

A delta inventory is a structured document, like DELTAS.md, that logs project changes with traceable numbering such as DLT-001. It supports traceability by mapping vision sections to actionable deltas for cross-team validation.

How do I number and document project deltas for cross-team validation?

You number and document project deltas by applying standardized identifiers like DLT-001 to each extracted change. This structured documentation integrates with a DELTAS.md file to support cross-team validation and iterative refinement.

Can I use an agent-driven review cycle for iterative refinement of a delta inventory?

Yes, you can apply an agent-driven review cycle for iterative refinement of a delta inventory. This process handles state tracking and validation, ensuring your extracted project deltas remain accurate throughout planning workflows.

Does delta discovery work without predefined dependencies or components?

Yes, delta discovery works without predefined dependencies or components. The process directly analyzes your vision document to generate a traceable delta inventory, requiring no additional environment setup or external tool integrations.

What is the best way to maintain traceability from project vision to actionable tasks?

The best way to maintain traceability from project vision to actionable tasks is by standardizing delta extraction into a numbered inventory. Mapping vision sections to identifiers like DLT-001 ensures consistent tracking and cross-team validation.