auto-optimize

# Auto-Optimize: Bounded optimization process Use VibeGuard to assess a project and deliver one bounded, verified optimization. ## When to Activate - The user asks for repository optimization discovery and implementation. - A project needs a rotating scan across security, quality, reliability, performance, and maintainability. - Existing guard or audit findings should be converted into prioritized implementation work. - The task needs an optimization report before deciding which fixes to execute. - The user explicitly asks for optimization across quality, reliability, security, or DX dimensions. ## Red Flags - The workflow starts without a bounded target or explicit authorization to implement. - More than one writable session operates on the repository. - A finding is repaired before it has evidence, classification, and a verification command. ## Checklist - [ ] Confirm target, authorization, and done-when before execution. - [ ] Classify every finding as FIX, SKIP, or DEFER with evidence. - [ ] Run VibeGuard deterministic checks before and after implemented fixes. ## Execution Boundary Start only when the user authorizes implementation and the optimization target is bounded. Keep one writable session for the repository and one short issue-sized batch per run. Do not build coordinator/reviewer lanes by default. If the user explicitly requests delegation, follow [`workflows/references/delegation-contract.md`](../references/delegation-contract.md). ## Core principles...