Can I use this for code that never had a spec?

Yes, Mode 3 (Generate) allows you to generate a specification retroactively based on existing artifacts and the current codebase.

Does it automatically overwrite my specification files?

No, it generates a Divergence Report first and walks you through each recommended update, allowing you to confirm, modify, or reject changes before they are applied.

What counts as a divergence during the scan?

It focuses on high-level changes like dropped or added requirements, integration surface changes, and success criteria that were modified during development, rather than minor implementation details.

How does Back-Propagate identify spec drift?

It analyzes implementation artifacts like notes, retros, and commission logs to find where reality diverged from the original plan, checking fields like 'Divergence' or 'Lessons Learned'.

Back-Propagate

Name: Back-Propagate
Author: rjroy

byrjroy

•

Aprendizaje y Documentación

Reconciles stale specifications with actual code implementation using development artifacts, notes, and retrospectives.

Back-Propagate is a specialized documentation maintenance skill for Claude Code that ensures your project specs stay in sync with reality. It flips the traditional development flow by pulling insights from implementation notes, retrospectives, and commissions back into the original design documents. Whether you are dealing with 'spec drift' after a fast-paced feature cycle or need to retroactively generate specifications for work done without them, this skill identifies divergences and updates your lore to reflect what was truly delivered, keeping documentation honest and useful.

Características Principales

01Automated drift detection between specifications and implementation artifacts

02Retroactive specification generation for existing code and unspecced work

03Guided revision history updates to maintain a clear audit trail of design changes

04Intelligent artifact scanning across lore plans, notes, and retrospectives

053 GitHub stars

06Detailed divergence reporting covering requirement shifts and changed entry points

Casos de Uso

01Updating technical specs after a feature sprint where implementation diverged from the plan

02Generating formal documentation for existing features that were built without initial specs

03Performing health checks on project documentation to identify stale or 'implemented' specs that need reconciliation

Características Principales

01Automated drift detection between specifications and implementation artifacts

02Retroactive specification generation for existing code and unspecced work

03Guided revision history updates to maintain a clear audit trail of design changes

04Intelligent artifact scanning across lore plans, notes, and retrospectives

053 GitHub stars

06Detailed divergence reporting covering requirement shifts and changed entry points

Casos de Uso

01Updating technical specs after a feature sprint where implementation diverged from the plan

02Generating formal documentation for existing features that were built without initial specs

03Performing health checks on project documentation to identify stale or 'implemented' specs that need reconciliation