What problem does it solve? When an architecture document fails review with a rework verdict, the original author tends to rewrite correct sections alongside the flagged ones. This Skill performs surgical repairs: it fixes only what the reviewer flagged, preserving everything that was already correct. ## Core Features & Use Cases - Finding-driven edits: Every critical and important review finding maps to an explicit document change, with no silent deferrals. - Scoped modification: Untouched sections stay intact; the artifact is updated in place rather than forked or rewritten. - Honest escalation: Findings that cannot be resolved with the given inputs become open questions to the owner instead of fake fixes. - Debt tracking: Non-critical residue after the second review cycle is recorded as accepted debt inside the architecture document itself. - Use Case: After architecture-reviewer returns a rework verdict on your system design doc, run this Skill to close each finding, write a repair report to .process/<task-id>/architecture_repair.md, and resubmit for re-review. ## Quick Start Fix the architecture document according to the architecture-review findings and write the repair report.
