vibepro-story-refactorlisted

# VibePro Story Refactor ## Purpose Use this Skill when VibePro is driving a refactor. The goal is to find and fix code defects, security risks, DRY gaps, and responsibility-boundary problems while preserving Story / Architecture / Spec consistency. ## When to Use Use this Skill when a refactor, cleanup, bug fix, architecture correction, security hardening, performance refactor, UI modernization, or DRY pass is expected to move through VibePro. It applies even when the user asks for "just a small refactor" if the work changes behavior, boundaries, user flows, verification, or PR readiness. ## Required Workflow 1. Start from a Story. If no Story exists, run `vibepro story derive` and inspect the Story map before implementing. 2. Resolve the output language from `.vibepro/config.json` `output.language` or the explicit CLI `--language` override before manually adding or editing human-facing Story, Architecture, Spec, Task, Review, Diagnosis, Journey, or PR artifacts. 3. Check Architecture. If the boundary, dependency direction, or responsibility split is missing, restore or add Architecture docs before changing code. 4. Check Spec. If behavior, invariant, API, or data-flow expectations are missing, restore or add Spec docs before changing code. 5. Use VibePro task context: - `vibepro story plan <repo>` - `vibepro task create <repo> --from-plan --id <story-id>` - `vibepro task brief|plan|handoff <repo> --task <task-id> --id <story-id>` 6. Use a diagnosis package wh