# Vc Agent Strategy Compare

Evaluate 4 execution strategies (sequential, parallel-subagents, workflow, agent-team)...

- Repository: https://github.com/withkynam/vibecode-pro-max-kit (1164 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-06-21
- Runs scripts: yes, review before use

## Install

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

## Description

Evaluate 4 execution strategies (sequential, parallel-subagents, workflow, agent-team) for a phase or fan-out task. Outputs 7-signal score table, agent count math, cost guards, and strategy recommendation.

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

# vc-agent-strategy-compare

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

Evaluate 4 execution strategies for any RIPER-5 phase or fan-out task. Computes the 7-signal score, shows explicit agent count math, applies cost guards, and outputs a ranked strategy recommendation.

All strategies use the existing vc-system agents and skills. The question is only how they are orchestrated.

---

## Model Selection Policy

Every spawned agent, across ALL four strategies (sequential, parallel subagents, dynamic workflow, agent team), defaults to **sonnet**. Spawn opus ONLY when the agent is carrying out real source-code or build execution (writing/editing code, running builds, applying migrations). Planning, research, analysis, validation, review, and synthesis all run on sonnet.

Concrete rules:

- **Default = sonnet** for any teammate, parallel subagent, or `agent()` call in a workflow. State the model explicitly when spawning.
- **opus ONLY for execution work**: the agent that actually implements code (the vc-execute-agent leg, or a workflow `agent()` step whose job is to modify source / run a build). The RIPER-5 phase that runs on opus is EXECUTE; all other phases (RESEARCH, SPEC, INNOVATE, PLAN, VALIDATE, UPDATE PROCESS) run on sonnet.
- **Agent-team members**: assign sonnet to reviewers, researchers, validators, and planners; assign opus only to the teammate doing real code execution.
- **Dynamic workflows**: pass `model: 'sonnet'` on `agent()` calls by default; pass `model: 'opus'` only on the execution stage that writes code or runs builds.
- **Parallel subagents**: fan-out investigation/review subagents are sonnet; only an implementing subagent is opus.

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