# Vc Predict

5 expert personas debate proposed changes before implementation.

- Repository: https://github.com/withkynam/vibecode-pro-max-kit (1164 stars)
- Category: Design
- License: MIT
- Last updated: 2026-06-21
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add withkynam/vibecode-pro-max-kit --skill vc-predict -g -a claude-code -y`
Codex: `npx skills add withkynam/vibecode-pro-max-kit --skill vc-predict -g -a codex -y`
Cursor: `npx skills add withkynam/vibecode-pro-max-kit --skill vc-predict -g -a cursor -y`
Gemini CLI: `npx skills add withkynam/vibecode-pro-max-kit --skill vc-predict -g -a gemini-cli -y`

## Description

5 expert personas debate proposed changes before implementation. Catches architectural, security, performance, and UX issues early. Use before major features or risky changes.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# vc-predict, Multi-Persona Pre-Analysis

> **Output style:** Follow `process/development-protocols/communication-standards.md`, answer-first, plain language, no unexplained jargon, TL;DR on long responses.

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

---

## Mode Selection

`vc-predict` runs in **Simple** or **Deep** mode. Choose based on the conditions below.

| | Simple | Deep |
|---|---|---|
| Context source | Approach description already in context | Approach description + historical research subagent |
| Subagent spawned | No | Yes, reads git log, prior reports, test failure history |
| Persona debate quality | Reasons from first principles | "We tried this 3 months ago and hit X" |
| When to use | Contained feature, clear scope, no prior attempts | See trigger conditions below |

### Deep Mode, Trigger Conditions (any one is sufficient)

- The approach involves a pattern previously attempted in this codebase (git history may show prior attempts)
- The approach touches a surface with known failure history: auth, billing, container lifecycle, streaming, or WebSocket reconnect
- Caller explicitly requests deep mode (`--deep` flag or "use deep predict")
- The plan is **COMPLEX** shape and this is the pre-checklist predict call

### Simple Mode, Trigger Conditions (default)

The rest: https://github.com/withkynam/vibecode-pro-max-kit/blob/HEAD/.claude/skills/vc-predict/SKILL.md