# CRITICAL WORKFLOW REQUIREMENT
- You MUST NOT add comments that describe the change they just made (e.g., “removed”, “legacy”, “cleanup”, “hotfix”, “flag removed”, “temporary workaround”).
- Only add comments for genuinely non‑obvious, persistent logic or external invariants. Keep such comments short (max 2 lines).
- When migrating or refactoring code, do not leave legacy code. Remove all deprecated or unused code.
- Put change reasoning in your plan/final message — not in code.

## Default Response Style

- Avoid using difficult words. Explain things simply. If you can't explain something simply, you don't understand it.
- Default to a terse, low-filler style in all user-facing responses.
- Keep grammar and full sentences, but cut pleasantries, hedging, repetition, and throat-clearing.
- Prefer short, direct wording. Say the answer first.
- Preserve exact technical terms, commands, paths, errors, and code.
- Keep explanations compact unless the user asks for more detail.
- For security warnings, destructive actions, or anything where brevity could cause confusion, switch to clear normal wording first.

## Work Summary

- Keep `set_work_summary` up to date before you start work
- `theme`: what has the work been about overall?
- `now` answers: what the user asked you to do and/or what are you about to do?
- Keep both labels concrete and under 40 characters.
- Since the summary line has dedicated space, prefer richer phrases that help a forgetful human re-orient instantly.
- Keep phrasing simple

---------

## Adaptive Burst Workflow

### How to Burst

- Trigger bursts only when needed; otherwise continue normal execution.
- Choose burst size by complexity:
  - low: 2 subagents
  - medium: 3 subagents
  - high/risky: 4-5 subagents
- Use one burst round by default.
- Run a second round only if confidence is still low.
- Assign non-overlapping scopes to reduce duplicate findings.

### What to Burst

- `discover-locator`: locate relevant files, symbols, and entry points.
- `discover-xref`: map defs/usages/callers/callees.
- `discover-flow`: trace execution or data flow paths.
- `discover-blast`: map direct and indirect impact surface.

### When to Burst

- Unfamiliar code area.
- Multiple plausible implementation paths.
- Unclear failure/root cause after initial inspection.
- Cross-cutting change touching multiple modules.
- High-impact change with regression risk.

### When Not to Burst

- Straightforward single-file changes.
- Clear path with high confidence.
- Small, low-risk, reversible changes.

### Burst Output Contract

Each discovery subagent returns compact, evidence-based output:

- `scope`: what was inspected
- `findings`: claim + `path:line` evidence + confidence
- `unknowns`: unresolved gaps

Limit each subagent to maximum 5 findings.