What problem does it solve? When requirements change after a Case has already been opened, teams need a controlled way to propagate re-agreed Definition changes into existing GitHub Issues and execution structures without duplicating pull requests, rewinding completed work, or making unauthorized scope decisions. ## Core Features & Use Cases - Re-agreement Gatekeeping: Accepts only Definition changes already agreed in req-define, rejecting unagreed changes back to the requirements phase. - Idempotent Amendment PRs: Detects and reuses existing Definition Amendment PRs via idempotency keys, never creating duplicates, and skips PR creation entirely when no real change exists. - Impact Reassessment: Evaluates all Issues in the Case execution structure (including completed Epic children) against Definition changes, marking only affected Issues for re-evaluation while leaving unaffected completed Issues untouched. - Use Case: A stakeholder renegotiates a requirement mid-project. Run the case-revise command with the Root Case and the re-agreed Definition draft; the workflow creates (or reuses) an Amendment PR, marks impacted Issues, and hands off to case-ready for execution structure re-confirmation. ## Quick Start Invoke the /agentdev/case-revise command with the Root Case Issue number and the re-agreed Definition changes from req-define.
