vibecode-pro-max-kit: Skill for Claude Code

vc-generate-phase-program

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

Generate kickoff artifacts for a multi-phase RIPER-5 program: umbrella plan, Program Goal Charter, session-goal block, per-phase plan stubs, and the 7-step per-phase inner loop reference (R → I → P → PVL → E → EVL → UP, which SKIPS SPEC).

The 7 steps are: Research → Innovate → Plan-Supplement → PVL (plan-validate loop — the gate that confirms the plan is ready before EXECUTE runs) → Execute → EVL (execute-validate loop — the confirmation run after EXECUTE, re-running gate tests independently) → Update-Process.

Source of truth: process/development-protocols/phase-programs.md

---

When To Invoke

Invoke this skill at PLAN phase when phase-program initiation is detected (3 or more dependent phases), or at ORCHESTRATOR when the incoming request involves 3 or more dependent phases.

Signal patterns that trigger this skill:

• the work naturally breaks into 3 or more dependent phases
• each phase needs its own validation gate before the next phase starts
• the work spans multiple packages, services, or runtime surfaces
• the user wants high-confidence progress with durable checkpoints
• repeated research is needed because new facts will emerge during execution

Do not invoke for a simple one-session feature or a small bug fix. Use the normal RIPER flow instead.

---

Kickoff Procedure

Before creating any plan files, follow these steps in order:

Step 1 — invoke vc-agent-strategy-compare. For programs with 3 or more phases, output will always recommend parallel-subagents (one per phase plan) or dynamic workflow. Plans are created in the recommended parallel mode, not sequentially.

Per-phase strategy invocation (mandatory): For each individual phase during scaffold, invoke vc-agent-strategy-compare with that phase's scope before writing that phase's plan stub — not once at the program level. Each phase may have a different recommended execution strategy.