vc-predict

Simulates five expert personas debating proposed changes to surface architectural, security, and performance risks before implementation.

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-predict-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-predict
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-predict
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-predict-marsley01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often discover architectural flaws, security holes, and performance regressions only after code is written. This Skill runs a structured pre-implementation review where five expert personas independently analyze a proposed change and debate conflicts, catching costly issues before a single line of code is written. ## Core Features & Use Cases - Multi-Persona Analysis: An Architect, Security, Performance, UX, and Devil's Advocate persona each independently evaluate the proposal, then reconcile disagreements into a consensus verdict. - Simple and Deep Modes: Simple mode reasons from first principles for contained changes; Deep mode spawns a research subagent that scans git history, prior phase reports, and test failure logs to ground the debate in past attempts. - Structured Verdict Output: Produces a GO / CAUTION / STOP verdict with agreements, conflict resolutions, a risk severity table, and actionable recommendations. - Use Case: Before migrating authentication from JWT to session cookies, run the Skill to have the Security persona flag session-fixation risks and the Architect flag coupling concerns, receiving a CAUTION verdict with concrete mitigations. ## Quick Start Ask the AI to run vc-predict on your proposed change, for example: predict the risks of adding WebSocket support for real-time notifications before I implement it.

Frequently Asked Questions about vc-predict

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a proposed feature for risks before writing code?

Run vc-predict with a description of the proposed change, optionally with file paths. Five personas (Architect, Security, Performance, UX, Devil's Advocate) independently analyze it, debate conflicts, and return a GO, CAUTION, or STOP verdict with mitigations.

What is the difference between simple mode and deep mode?

Simple mode reasons from first principles using only the proposal in context. Deep mode spawns a research subagent that scans git history, prior phase reports, and test failure logs, so personas can cite concrete past attempts and known landmines.

When should I use deep mode for architectural review?

Use deep mode when the approach touches surfaces with known failure history such as auth, billing, container lifecycle, streaming, or WebSocket reconnect, when a pattern was previously attempted, or when the plan is complex. It also triggers via the --deep flag.

When should I not use multi-persona pre-implementation analysis?

Skip it for trivial or low-risk changes, already-approved work with no open design questions, and pure dependency upgrades without API changes. Use a debugger skill for bugs or a planning skill for already-decided tasks instead.

What triggers a STOP verdict in the prediction report?

A STOP verdict is issued when Security finds an unmitigated auth bypass or data exposure, the Architect finds a fundamental design incompatibility, Performance finds unacceptable latency with no workaround, or the Devil's Advocate exposes an assumption that invalidates the approach.