What problem does it solve? Making a large-scale change to a structured requirements document — such as renaming a core concept across hundreds of occurrences — is error-prone: global replacements corrupt tables and diagrams, acceptance criteria drift out of sync, and statistics sections go stale. This Skill enforces a disciplined review-then-execute workflow so mass revisions stay consistent and verifiable. ## Core Features & Use Cases - Semantic change mapping: Identifies every surface form of an old concept (nouns, table headers, diagram labels, requirement titles) and distinguishes pure renames from behavioral changes that require rewriting acceptance criteria. - Ordered patching with fallout repair: Applies replacements in dependency order (terminology → data model → requirements → diagrams → statistics) and fixes common breakage such as double-pipe table corruption, mermaid diagram damage, and spacing artifacts. - Grep-based validation: Verifies zero remaining occurrences of old terms, checks requirement counts against statistics tables, and includes a Python script to automate old-term residue checks. - Use Case: Replacing "Panel Stacking" with "Tab Group" across a 4700-line SRS — updating term definitions, rewriting Given/When/Then acceptance criteria, adding new requirements with suffix IDs, and regenerating the statistics section. ## Quick Start Ask the agent to rename a core concept across your SRS document and have it propose a comparison table of changes for approval before patching anything.
