Prompt Analyze Simplify Scope

# Prompt: Analyze Simplify Scope

Use this prompt for one bounded discovery subagent.

## Template

You are analyzing a bounded code area for behavior-preserving simplification
only. Do not edit files.

Scope:
- <paths, packages, modules, or symbols>

Task:
1. Check whether the baseline verification path for this scope is green. If
   not, keep the output analysis-focused.
2. Record the code state reviewed if it is obvious from local context.
3. Map the local ownership and call flow relevant to this scope.
4. Identify human-usability problems only:
   - generic or misleading names
   - shallow wrappers or pass-through helpers
   - speculative abstractions or extension points
   - over-splitting that hides the main path
   - repeated parameter plumbing
   - duplicated helpers that should be deleted, inlined, or consolidated
   - misplaced behavior or classes
   - comment-heavy code that still obscures intent
   - state or branching complexity that can be reduced without changing behavior
5. Cite local evidence for both the problem and the preferred pattern.
6. Classify each issue as:
   - `DELETE`
   - `INLINE`
   - `RENAME`
   - `MOVE`
   - `EXTRACT`
   - `LEAVE ALONE`
7. Recommend the smallest coherent simplify batches.
8. Note whether a native `/simplify` command is visibly available locally. Only
   mention it if confirmed; do not assume it exists.
9. Return enough structure to fill `docs/simplify-review-report.md` without
   another discovery pass.

Guardrails:
- Preserve behavior exactly.
- Prefer simpler code over more abstract code.
- Prefer deletion before new abstraction.
- Do not suggest bug fixes or feature additions.
- Do not infer a pattern from a single weak example.
- You are not alone in the codebase; do not revert or overwrite unrelated edits.

Return:
- trigger summary
- baseline verification status
- code state reviewed, if known
- local pattern inventory
- issue list ordered by human-maintenance impact, and for each issue include:
  - kind
  - priority
  - paths
  - problem
  - local evidence
  - recommended action
  - why this is simpler for a human
  - invariants to preserve
  - verification notes
- recommended batch list, and for each batch include:
  - goal
  - files in scope
  - allowed edits
  - do-not-change notes
  - verification
  - stop conditions
- deferred or rejected changes
- blockers or uncertainty