vc-generate-plan
vc-generate-plan transforms feature ideas and product requirements into structured implementation plan artifacts saved to your repo. It handles both straightforward single-phase work and large multi-phase programs, organizing plans with required sections for touchpoints, contracts, blast radius, and verification gates. The skill enforces answer-first communication and ensures execution handoff clarity through explicit resume notes.
vc-generate-plan creates implementation plan artifacts in SIMPLE or COMPLEX format from feature ideas and PRDs.
AI-generated summary based on this skill's SKILL.md
Install
withkynam/vibecode-pro-max-kit/vc-generate-plan · repository language: JavaScript
git clone https://github.com/withkynam/vibecode-pro-max-kit
cp -r vibecode-pro-max-kit/.claude/skills/vc-generate-plan ~/.claude/skills/vc-generate-plannpx skillfed install withkynam/vibecode-pro-max-kit/vc-generate-planFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create an implementation plan with vc-generate-plan?
vc-generate-plan transforms your feature idea or PRD into a structured implementation plan artifact saved directly to your repo. Provide your requirements, and the skill organizes them into a plan with required sections including touchpoints, contracts, blast radius, and verification gates—ensuring clarity for execution handoff.
Can vc-generate-plan generate a multi-phase program plan?
Yes. vc-generate-plan generates multi-phase program plans with both umbrella-level and phase-specific plans. It structures large initiatives across multiple phases while maintaining coherent contracts and verification gates across all phases.
What formats does vc-generate-plan support for plan writing?
vc-generate-plan writes plans in both SIMPLE and COMPLEX formats. Both formats include verification gates and handoff notes, with the COMPLEX format adding deeper detail for larger initiatives and cross-team dependencies.
Turn idea into plan—what does vc-generate-plan include in each plan?
vc-generate-plan includes touchpoints, contracts, blast radius, and test strategy in every plan artifact. These sections define stakeholder interactions, API/interface agreements, scope boundaries, and validation approach before execution begins.
Does vc-generate-plan validate plans before handoff?
Yes. vc-generate-plan structures and validates plan artifacts before execution handoff, enforcing answer-first communication and explicit resume notes to ensure teams have clarity on what to execute and where to pick up work.
SKILL.md
rendered from the published skill — quoted content, verbatim
Generate Plan
> Output style: write the plan answer-first with tables/bullets and a one-line TL;DR per the canonical rule — process/development-protocols/communication-standards.md.
Use this skill to produce the authoritative implementation plan artifact set for the project's work.
This skill is the canonical planning contract for the repo. Planning discipline previously spread across vc-plan now belongs here plus the plan-agent prompt.
Normal output is one plan file.
For large multi-phase programs, this skill instead defines how to create an umbrella plan plus
phase-plan set under one feature folder. See process/development-protocols/phase-programs.md.
Optional input: a feature idea plus simple or complex when the user already knows the intended depth.
Workflow
- Read
references/generate-plan.mdfor
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 5 files
.claude/skills/vc-generate-plan/SKILL.md
.claude/skills/vc-generate-plan/references/example-complex-prd.md
.claude/skills/vc-generate-plan/references/example-simple-prd.md
.claude/skills/vc-generate-plan/references/generate-plan.md
.claude/skills/vc-generate-plan/scripts/validate-plan-artifact.mjs