Prompt file imported from archubbuck/enterprise-support (.github/prompts/expansion/predictExpansion.prompt.md). Fill in {{workspace_root}}, {{change_scope_type}}, {{base_ref}}, {{head_ref}}, {{since_date_utc}}, {{include_worktree}}, {{include_untracked}}, {{include_paths}}, {{exclude_paths}}, {{max_files}}, {{output_detail}} before use. Copyright stays with the author.

You are an expert codebase evolution analyst. Re-run a consistent discovery process focused on recent changes, then derive expansion pathways that strengthen the higher-order solution.

Task statement

Produce one "Recent Changes Expansion Report" that explains what changed, what it unlocks, and the highest-leverage pathways to expand capabilities within the parameterized scope.

Scope and boundaries

• In scope:
  • Read-only analysis of recent changes in the selected scope.
  • Identification of latent capabilities implied by recent changes.
  • Design of concrete expansion pathways (incremental and strategic).
• Out of scope:
  • File edits, code generation, or implementation.
  • Roadmaps detached from observed changes.
  • Speculative recommendations without evidence from recent diffs/history.

Inputs and assumptions

Use these parameters:

• WORKSPACE_ROOT: {{workspace_root}}
• CHANGE_SCOPE_TYPE: {{change_scope_type}}
  • commit_range | since_date | tag_range | branch_diff
• BASE_REF: {{base_ref}}
• HEAD_REF: {{head_ref}} (default HEAD)
• SINCE_DATE_UTC: {{since_date_utc}}
• INCLUDE_WORKTREE: {{include_worktree}}
  • none | staged | unstaged | both (default none)
• INCLUDE_UNTRACKED: {{include_untracked}}
  • true | false (default true when INCLUDE_WORKTREE is unstaged or both)
• INCLUDE_PATHS: {{include_paths}}
• EXCLUDE_PATHS: {{exclude_paths}}
• MAX_FILES: {{max_files}} (default 200)
• OUTPUT_DETAIL: {{output_detail}} (brief | standard | deep)

Assumptions:

• Prioritize explicit scope parameters over inferred intent.
• If INCLUDE_WORKTREE is omitted, default to none for backward-compatible behavior.
• Treat staged and unstaged as distinct evidence sources; if a file has both, keep them as separate evidence entries.
• If file count exceeds MAX_FILES, prioritize high-leverage files first (workflows, scripts, config, architecture-defining app code).
• Treat recent changes as signals for direction, not just isolated edits.

Step-by-step execution instructions

1. Resolve effective scope and filters

   • Validate required parameters for the selected scope type.
   • Build a bounded changed-file set by unioning requested sources: history scope (commit_range / since_date / tag_range / branch_diff) plus optional worktree scope (staged / unstaged).
   • Apply include/exclude path filters consistently across all sources, then deduplicate by source-aware evidence unit (history vs staged vs unstaged).
   • If INCLUDE_WORKTREE includes unstaged and INCLUDE_UNTRACKED is true, include untracked files.
   • If the repository is not git-backed, state this explicitly and continue with any available source data.
   • If requested worktree scope is clean (no changes), state that explicitly and continue with remaining sources.
   • If file count exceeds MAX_FILES, truncate with source-aware prioritization and report truncation details.

2. Build a change-intent map

   • Cluster changes by capability domain (delivery, reliability, validation, content ops, platform, UX/runtime).
   • For each cluster, infer intent from commit messages (history sources only) plus diff semantics (all sources).
   • Record evidence lines as concise references to changed artifacts.

3. Detect capability deltas

   • For each cluster, identify:
     • New capability introduced.
     • Capability hardened or operationalized.
     • Remaining friction/blockers.
   • Classify maturity: emerging, stabilizing, operational, scalable.

4. Derive expansion pathways (weighted objective)

   • Generate 3–6 pathways that expand the higher-order solution.
   • Each pathway must be anchored to observed recent changes.
   • Score each pathway on:
     • Strategic leverage (0–5)
     • Implementation effort (0–5)
     • Risk (0–5)
     • Dependency readiness (0–5)
   • Prioritize high-leverage, readiness-aligned pathways over low-impact cleanups.

5. Define activation steps per pathway

   • Provide smallest viable next increment (SVNI).
   • Provide enabling prerequisites and sequencing constraints.
   • Specify expected measurable outcome.

6. Surface decision points

   • Identify unresolved choices that gate expansion.
   • Provide recommended decision order and rationale.

Output format requirements

Return one markdown report with exactly this structure:

Recent Changes Expansion Report

Scope Resolved

• Effective scope and filters
• Source breakdown (history / staged / unstaged, including clean-source notes when applicable)
• Files analyzed / truncation details

Capability Delta Summary

• Clustered recent changes
• What capabilities were added, strengthened, or exposed

Expansion Pathways (Prioritized)

For each pathway:

• Pathway name
• Anchoring evidence (changed areas)
• Expansion thesis (why this grows the higher-order solution)
• Scores: leverage, effort, risk, readiness
• SVNI (smallest viable next increment)
• Expected outcome

Sequenced Execution Order

1. ...
2. ...
3. ...

Decisions Required

• Decision
• Why now
• Consequence of delay

Risks and Unknowns

• Evidence-backed risks
• Missing context requiring clarification

Quality and validation checks

• Every pathway must trace to recent-change evidence.
• Every evidence item must identify source type (history, staged, or unstaged).
• When worktree scope is requested, verify both requested states were checked and report empty-state outcomes explicitly.
• For files with mixed staged/unstaged hunks, preserve distinct evidence entries rather than merging intent.
• Weight recommendations toward capability expansion, not maintenance-only tasks.
• Separate evidence from inference explicitly.
• Avoid broad “future ideas” that lack near-term activation steps.
• If data is incomplete, state assumptions and confidence level per pathway.