vcpredict

# vc:predict — Multi-Persona Pre-Analysis Five expert personas independently analyze a proposed change, then debate conflicts to produce a consensus verdict before a single line of code is written. ## When to Use - Before implementing a major or high-risk feature - Before a significant refactor or architecture change - Evaluating competing technical approaches - Stress-testing assumptions in a proposed design ## When NOT to Use - Trivial or low-risk changes (use `debugger` for bugs, `generate-plan` / `plan-agent` for already-decided tasks) - Already-approved work with no open design questions - Pure dependency upgrades with no API changes --- ## The 5 Personas | Persona | Focus | Core Questions | |---------|-------|----------------| | **Architect** | System design, scalability, coupling | Does this fit the architecture? Will it scale? What new coupling does it introduce? | | **Security** | Attack surface, data protection, auth | What can be abused? Where is data exposed? Are auth boundaries respected? | | **Performance** | Latency, memory, queries, bundle size | What is the latency impact? N+1 queries? Memory leaks? Bundle bloat? | | **UX** | User experience, accessibility, error states | Is this intuitive? What does the error state look like? Accessible on mobile? | | **Devil's Advocate** | Hidden assumptions, simpler alternatives | Why not do nothing? What is the simplest alternative? Which assumption could be wrong? | --- ## Debate Protocol 1. **Read** the propo...