Add impact scope summary to change impact report

Compute per-branch lowest common ancestors of all impacted requirements
through the derivedFrom hierarchy, giving reviewers a high-level view
of affected model areas. Section appears between Changed Elements and
Invalidated Verifications in both text and JSON output.

Bump version to 0.11.0.

Author: Test User

Cargo.lock

@@ -6,7 +6,7 @@ members = [
 resolver = "2"
 
 [workspace.package]
-version = "0.10.0"
+version = "0.11.0"
 edition = "2021"
 rust-version = "1.86"
 license = "Apache-2.0"

Cargo.toml

@@ -46,9 +46,12 @@ ${1:-Comparing against: HEAD~1 (previous commit)}
 3. **Analyze the results:**
 
    Extract from JSON:
-   - `added_elements[]` - New requirements/verifications
-   - `modified_elements[]` - Changed requirements/verifications
-   - `affected_elements[]` - Elements impacted by changes
+   - `added[]` - New requirements/verifications
+   - `changed[]` - Changed requirements/verifications
+   - `removed[]` - Removed elements
+   - `relocated[]` - Relocated elements (same name, different path)
+   - `impact_scope[]` - Per-branch scope roots (common parent requirements covering all impacted elements)
+   - `invalidated_verifications[]` - Verifications that need re-review
 
 4. **For each modified requirement:**
 
@@ -65,19 +68,22 @@ ${1:-Comparing against: HEAD~1 (previous commit)}
 
 5. **Present impact findings:**
 
+   **Impact Scope** (high-level affected areas):
+   - [Parent Requirement A](file.md#parent-a) - covers changed children
+   - [Standalone Req](file.md#standalone) - directly changed
+
    **Added Elements:**
    - [New Requirement](file.md#new-req) - type: requirement
 
    **Modified Elements:**
    - [Changed Requirement](file.md#changed) - review needed
 
-   **Affected Elements (propagation):**
-   - Verifications needing review: X
-   - Implementations needing update: Y
-   - Child requirements affected: Z
+   **Invalidated Verifications:**
+   - Verifications needing re-review: X
 
 6. **Provide recommendations:**
-   - Review and update affected verifications
+   - Start with impact scope to understand affected model areas
+   - Review and update invalidated verifications
    - Update test criteria if requirements changed
    - Review implementations marked with satisfiedBy
    - Run tests for affected verifications

claude-plugins/commands/analyze-impact.md

@@ -37,7 +37,11 @@ Generate implementation task plan from requirement changes on a feature branch.
    reqvire change-impact --git-commit=$BASE_COMMIT --json > /tmp/impact.json
    ```
 
-3. **For each changed requirement:**
+3. **Review impact scope** (from JSON `impact_scope[]`):
+
+   The `impact_scope` array shows the per-branch common parent requirements covering all impacted elements. Use this to understand the high-level affected model areas before diving into details.
+
+4. **For each changed requirement:**
 
    Get full context using collect:
    ```bash
@@ -62,7 +66,7 @@ Generate implementation task plan from requirement changes on a feature branch.
    - satisfiedBy relations (code to update)
    - derivedFrom relations (context)
 
-4. **For each verification:**
+5. **For each verification:**
 
    Get test paths:
    ```bash
@@ -71,7 +75,7 @@ Generate implementation task plan from requirement changes on a feature branch.
 
    Extract satisfiedBy relations (test files).
 
-5. **Generate TodoWrite task plan:**
+6. **Generate TodoWrite task plan:**
 
    **Use collected context** from `/tmp/req_<requirement-id>.json` to create concise summaries:
    - Extract parent requirement purpose (why this exists)
@@ -108,13 +112,13 @@ Generate implementation task plan from requirement changes on a feature branch.
      ☐ Validate: reqvire validate
    ```
 
-6. **Generate git blob links:**
+7. **Generate git blob links:**
    ```bash
    REPO_URL=$(git remote get-url origin | sed 's/\.git$//' | sed 's/git@github.com:/https:\/\/github.com\//')
    BLOB_URL="${REPO_URL}/blob/${BASE_COMMIT}/${file_path}#${element-anchor}"
    ```
 
-7. **Save collected context for reference:**
+8. **Save collected context for reference:**
 
    For each requirement, save a formatted summary:
    ```bash
@@ -124,7 +128,7 @@ Generate implementation task plan from requirement changes on a feature branch.
 
    This provides developers with full context documents they can reference during implementation.
 
-8. **Present task plan:**
+9. **Present task plan:**
    - Phase 1: New requirements to implement (with context summaries)
    - Phase 2: Modified requirements to update (with impact analysis)
    - Phase 3: Affected verifications to review
@@ -139,6 +143,7 @@ Generate implementation task plan from requirement changes on a feature branch.
 **Feature**: {current_branch}
 
 ## Summary
+- Impact scope: {scope root names from impact_scope[]}
 - New requirements: X
 - Modified requirements: Y
 - Tests to run: Z

claude-plugins/commands/generate-tasks.md

@@ -348,9 +348,10 @@ reqvire change-impact --git-commit=HEAD~1
 ```
 
 The change-impact command shows:
-- Which requirements were modified
+- Which requirements were added, changed, removed, or relocated
 - Which downstream elements are affected (via derivedFrom, verifiedBy)
-- Impact scope and traceability
+- **Impact scope**: Per-branch common parent requirements covering all impacted elements (high-level summary of affected areas)
+- Invalidated verifications that need re-review
 
 For detailed analysis workflows, see [Explore](reference/explore.md).
 

claude-plugins/skills/syseng/SKILL.md

@@ -36,9 +36,12 @@ reqvire change-impact --git-commit=HEAD~1
 ```
 
 The change-impact command identifies:
-- `added_elements[]` - New requirements/verifications
-- `modified_elements[]` - Changed requirements/verifications
-- `affected_elements[]` - Elements impacted by changes (via derivedFrom, verifiedBy)
+- `added[]` - New requirements/verifications
+- `changed[]` - Changed requirements/verifications
+- `removed[]` - Removed elements
+- `relocated[]` - Relocated elements (same name, different path)
+- `impact_scope[]` - Per-branch scope roots: common parent requirements covering all impacted elements. Use this for a high-level summary of affected model areas
+- `invalidated_verifications[]` - Verifications that need re-review
 
 **Change Propagation Rules:**
 - **Parent → Child**: Parent changes propagate to all derived children