What problem does it solve?
After a forward-cycle feature is coded, the original extraction artifacts (architecture.md, domain.md) become stale because the code has already changed. This Skill closes that gap by distilling each delivered feature into an addendum file, keeping the extraction readable and accurate until the next full re-extraction.
Core Features & Use Cases
- Addendum Generation: Creates a dated addendum per delivered feature in
_reversa_sdd/addenda/, summarizing impacts per extraction artifact with typed deltas (regra-alterada, componente-novo, delta-de-contrato-externo, etc.).
- Scenario Detection: Distinguishes legacy scenarios (anchored to architecture.md and domain.md) from greenfield scenarios (anchored to prd.md and sdd/ specs) and adapts the impact table accordingly.
- Read-Only Safety: Never modifies original extraction artifacts; writes only inside the addenda folder, appending update sections on re-execution instead of overwriting.
- 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 /reversa re-extraction supersedes it.
Quick Start
Run the reversa-sync skill after /reversa-coding completes to generate the convergence addendum for the active feature.