vibepro-workflowlisted

# VibePro Workflow ## Purpose Use VibePro as a Story / Architecture / Spec / Graphify / Gate control plane. The CLI creates evidence; this Skill tells the agent how to use that evidence without skipping the intended order. ## Operating Order 1. Confirm the target repository and current branch. 2. Initialize only when needed: `vibepro init <repo> --language ja`. 3. Before manually adding or editing human-facing VibePro artifacts, resolve the output language from `.vibepro/config.json` `output.language` or the explicit CLI `--language` override. 4. Select or create the Story before diagnosing or changing code. 5. Import Graphify context before impact-sensitive work: `vibepro graph <repo> --run-graphify`. 6. Diagnose and derive the repo context: - `vibepro story diagnose <repo> --id <story-id> --run-graphify` - `vibepro story derive <repo> --run-graphify` - `vibepro story map <repo>` 7. When the user asks for a purpose-level check, use diagnosis packages instead of guessing the scanner set: - `vibepro check list` - `vibepro check ui <repo>` - `vibepro check security <repo>` - `vibepro check performance <repo>` - `vibepro check architecture <repo>` - `vibepro check pr-readiness <repo> --base <ref> --head <ref>` - `vibepro check launch-readiness <repo>` 8. For performance improvement stories, define and record Story-level performance evidence before claiming speedups: - `vibepro performance define <repo> --id <story-id> --metric-id <id> --user-