vc-generate-plan

Generates structured implementation plan artifacts in SIMPLE or COMPLEX formats with validation.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-generate-plan-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-generate-plan
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-generate-plan
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-generate-plan-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning an idea, PRD, or approved direction into a consistent, verifiable implementation plan is error-prone and inconsistent across teams. This Skill enforces a canonical plan contract so every plan artifact includes verification gates, blast radius, and execution handoff details. ## Core Features & Use Cases - Plan Generation: Creates SIMPLE (one-session) or COMPLEX (multi-phase) plan files saved to dated task folders under process/general-plans or process/features. - Phase Program Support: Produces umbrella orchestration plans plus per-phase plan files for large multi-phase programs. - Artifact Validation: Runs a Node.js validation script that checks required sections like Touchpoints, Public Contracts, Verification Evidence, and Validate Contract. - Use Case: A developer has an approved feature idea and needs a plan that Cursor Plan mode or RIPER-5 can execute phase by phase with explicit test gates and resume instructions. ## Quick Start Ask the assistant to create a COMPLEX implementation plan for your feature idea and save it as a dated plan artifact in the repo's process folder.

Frequently Asked Questions about vc-generate-plan

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

FAQPage Schema
How do I create an implementation plan from a feature idea?

Provide a brief description of your idea and specify whether it is SIMPLE (one-session) or COMPLEX (multi-phase). The skill asks clarifying questions if needed, then generates a dated plan file saved inside a task folder under process/general-plans or process/features.

What is the difference between SIMPLE and COMPLEX plan formats?

SIMPLE plans cover one-session work with 8-15 checklist steps and no phase gates. COMPLEX plans cover multi-phase projects with architecture decisions, RFCs, phased delivery, and per-phase verification gates requiring user confirmation before proceeding.

How are generated plan files validated?

Run the included Node.js script validate-plan-artifact.mjs against the plan path. It checks for required sections like Overview, Phase Completion Rules, Acceptance Criteria, Validate Contract, and verification language, failing on blockers and reporting warnings.

When should I use a phase program instead of one plan file?

Use a phase program when work has three or more dependent milestones with separate proof boundaries, or spans multiple packages requiring re-research per phase. It produces one umbrella plan plus one direct plan file per phase, each with its own gates and report path.

Can a phase be marked complete when the code compiles?

No. The contract forbids marking a phase VERIFIED based only on builds or type checks. A phase is VERIFIED only after integration testing, manual user testing, database or state verification, error handling checks, and explicit user confirmation.