vc-generate-plan

Generate plan artifacts with required sections and validation hooks.

1.1k|223|Updated May 27, 2026
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-generate-plan-withkynam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-generate-plan
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-plan
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-generate-plan-withkynam

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The vc-generate-plan skill provides a formal, repeatable process to create authoritative plan artifacts for projects, ensuring consistent structure and compliance with the repository's plan contract.

Core Features & Use Cases

  • Generates a single authoritative plan file for standard work or a complete plan set for phase-based programs.
  • Validates artifacts against the plan contract, including required sections like Phase Completion Rules, Test Plans, and Verification Evidence.
  • Assists with Cursor Plan mode and RIPER-5 guided execution, providing a clear next-step for execution.
  • Integrates with references/example-complex-prd.md to emulate depth and rigor for complex plans.

Quick Start

Run the plan generator to produce the canonical vc-generate-plan artifact for your feature, date-stamped.

Frequently Asked Questions about vc-generate-plan

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

FAQPage Schema
How do I generate a project plan that includes phase gates and validation hooks?

To generate a project plan with phase gates and validation hooks, you need a plan generator that formats outputs to your repository's contract. It assesses complexity to produce either a single plan file or a phased plan set with required validation sections.

What is an authoritative plan artifact and when do I need one for project management?

An authoritative plan artifact is a structured Markdown document enforcing compliance with a repository's plan contract. You need one when executing features or programs to ensure consistent structure, validation hooks, and clear execution guidance.

Does Cursor Plan mode work with generated plan artifacts for RIPER-5 workflows?

Cursor Plan mode works with generated plan artifacts by providing clear next-steps for execution. The Markdown plan artifact includes required sections and execution guidance suitable for RIPER-5 guided execution workflows.

What's the best way to structure complex program plans versus simple feature plans?

The best way to structure complex program plans is to organize outputs into a phased plan set with phase gates. Simple feature plans use a single plan file, while complex programs emulate depth and rigor using reference PRDs.

Can I validate artifacts against required sections like Test Plans and Verification Evidence?

You can validate artifacts against the plan contract by checking for required sections like Phase Completion Rules, Test Plans, and Verification Evidence. The generation process ensures these validation hooks are built into the Markdown output.