vibepro

Use when recording VibePro verification or review evidence, writing Architecture/Spec artifacts, or resolving blocked gates when pr prepare reports needs_verification, needs_review, or unresolved gate ids.

Use when the user asks VibePro to check UI, security, performance, architecture, PR readiness, launch readiness, or performance improvement evidence.

Use when working with VibePro CLI, Graphify, Story diagnosis, task planning, PR preparation, Gate evidence, or VibePro review artifacts.

Use when refactoring with VibePro so the agent follows Story -> Architecture -> Spec -> Task -> Code -> Gate -> PR instead of editing code first.

Use when generating, reviewing, or repairing Japanese business meeting minutes from transcripts, Slack attachments, recordings, or Meeting Pack inputs.

Use when VibePro work needs codebase-memory-mcp impact context for changed files, call paths, routes, symbols, or risk hints without treating topology as correctness evidence.

Use when reviewing VibePro PR preparation artifacts, deciding whether to proceed, split, add evidence, waive with reason, or block.