What problem does it solve? Changing an already-approved artifact in a spec-driven development pipeline normally forces you to restart the entire workflow from scratch, wasting the effort of every downstream stage. This Skill edits the artifact in place, logs the change, and marks only the genuinely affected downstream stages as requiring revalidation. ## Core Features & Use Cases - In-place artifact editing: Modifies PRD, TRD, implementation code, code review, QA report, security review, or SRE review files without recreating them, and marks resolved "VALIDAR DEPOIS" items as validated instead of deleting them. - Impact propagation: Uses the fixed pipeline order (PRD → TRD → implementation → code review → QA → security → SRE) to determine which downstream stages need revalidation and which stay approved. - Revision logging: Records date, author, change, and reason in each artifact's revision log, with rules that prevent revalidation flags from being accidentally re-triggered by closing entries. - Use Case: A stakeholder changes an acceptance criterion in an approved PRD. The Skill edits the PRD, flags the TRD, implementation, and QA stages for revalidation, and tells you exactly which commands to rerun. ## Quick Start Ask the assistant to amend the approved TRD for a feature slug to change a design decision and propagate revalidation only to the affected downstream stages.
