vc-generate-plan

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

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-generate-plan-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-generate-plan
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-generate-plan
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-generate-plan-marsley01

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 rigorous, executable implementation plan is error-prone: plans often lack verification gates, test stages, and resume context, causing agents to mark unfinished work as done. This Skill produces the repo's canonical plan artifact with enforced structure and automated validation. ## Core Features & Use Cases - SIMPLE and COMPLEX plan generation: Creates one-session plans (8-15 checklist steps) or multi-phase plans with RFCs, architecture decisions, and phased delivery gates. - Phase program support: For large programs, generates an umbrella orchestration plan plus one direct plan file per phase under a feature folder. - Mandatory quality sections: Enforces Touchpoints, Public Contracts, Blast Radius, Verification Evidence, and Resume and Execution Handoff sections in every direct plan. - Artifact validation: Ships a Node.js validator script that checks filenames, date stamps, required sections, and status markers before a plan is accepted. - Use Case: A developer describes a new dashboard feature; the Skill asks whether it is SIMPLE or COMPLEX, runs date +%d-%m-%y, writes the plan into a task folder under process/general-plans/active/, and validates it with the bundled script. ## Quick Start Ask the assistant to create an implementation plan for your feature idea and specify whether it is simple or complex.

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 the feature and specify whether it is SIMPLE (one session) or COMPLEX (multi-phase). The Skill runs a short Q&A if details are missing, gets the current date, and saves a structured plan file into a task folder under process/general-plans/active/ or a feature folder.

What is the difference between a SIMPLE and COMPLEX plan?

A SIMPLE plan covers one-session work with 8-15 atomic checklist steps and no phase gates. A COMPLEX plan covers multi-phase projects with architecture decisions, sequential RFCs, pre-phase research gates, and per-phase verification before proceeding.

How do I validate a generated plan artifact?

Run node .claude/skills/vc-generate-plan/scripts/validate-plan-artifact.mjs followed by the plan path. The script checks filename date stamps, required sections like Validate Contract and Acceptance Criteria, and reports failures as JSON; add --strict to treat warnings as blocking.

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 where each milestone needs its own research-execute-validate loop. It produces one umbrella plan plus one direct plan file per phase.

Why can't a phase be marked VERIFIED after the code compiles?

The Skill enforces that VERIFIED status requires end-to-end integration testing, database or state verification, error handling checks, and explicit user confirmation. Build success or passing TypeScript only qualifies as CODE DONE.