dev-refactorlisted

# Refactor ## Overview Optional quality step on completed features. Not a status-gate — features are DONE after `/dev-verify`. This skill improves code structure, naming, and patterns on already-finished features. Batch-first architecture: analyzes ALL features in parallel via Explore agents, triages clean vs dirty, generates stack-aware refactor patterns via Context7, creates one combined plan with one approval, and applies changes with per-feature rollback. **Trigger**: `/dev-refactor`, `/dev-refactor {feature-name}`, or `/dev-refactor recent` (picks most recently modified feature.json with tests section) ## Scope Rule: Feature Files Only **This skill ONLY refactors files that belong to the feature.** - Extract all code file paths from `feature.json` → `files[]` — these are the **pipeline files** - ONLY these files may be analyzed, planned, and modified - **NEVER** touch, scan, plan, or modify files outside this list - **Exception:** New utility/helper files may be **created** if they exclusively extract code from pipeline files (e.g., extracting shared logic into a new `utils/` file). Existing external files may NEVER be modified. - If a pattern scan or research finding points to an external file → skip it, do not include in plan - If a DRY violation spans a pipeline file and an external file → only refactor the pipeline file side ## When to Use - After `/dev-verify` completes (features in DONE status) - When `.project/features/{name}/feature.json` exists with `te