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. ## When to Use Use this Skill when the task mentions VibePro, Story/Spec/Architecture, Graphify, Gate DAG, PR preparation, Agent Review, diagnosis packages, review cockpit, or VibePro-managed evidence under `.vibepro/`. Also use it when the user asks whether VibePro work is done, PR-ready, verified, reviewable, or safe to merge. In those cases the answer must be grounded in current VibePro artifacts and repository state, not a general impression. ## 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 impact context before impact-sensitive work: - Run Graphify when artifact-level graph context is useful: `vibepro graph <repo> --run-graphify`. - Use `vibepro-codebase-memory` when `codebase-memory-mcp` is available and changed-file topology, symbols, routes, call paths, or risk hints would affect implementation, tests, review roles, or split boundaries. 6. Diagnose and derive the repo context: - Before