What problem does it solve? After a feature is delivered in the Reversa forward cycle, the extraction artifacts in _reversa_sdd/ (architecture.md, domain.md) become stale because the code has already changed. This Skill closes that gap by distilling each delivered feature into a dated addendum, so anyone reading the extraction sees the system as it exists today—without modifying the original artifacts. ## Core Features & Use Cases - Addendum Generation: Creates a structured Markdown addendum per feature in _reversa_sdd/addenda/ with vigência tracking, delivery summary, and per-artifact impact tables. - Scenario Detection: Automatically distinguishes legacy scenarios (impacts mapped to architecture.md/domain.md sections) from greenfield scenarios (impacts mapped to prd.md and sdd/ specs). - Append-Only Updates: On re-execution for the same feature, appends a dated update section instead of overwriting, preserving the full synchronization history. - Use Case: After running /reversa-coding on a feature that changed a business rule, run this Skill to produce an addendum pointing readers to the new rule behavior until the next full /reversa re-extraction supersedes it. ## Quick Start Run the reversa-sync step after /reversa-coding completes to generate the feature addendum in _reversa_sdd/addenda.
