vcgenerate-plan

# Generate Plan 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 1. Read `references/generate-plan.md` for the full plan contract. 2. Run `date +%d-%m-%y` before choosing the filename. 3. If complexity is not obvious, ask whether the plan is `SIMPLE` or `COMPLEX`. 4. Save the plan to `process/general-plans/active/` unless the work belongs to an existing `process/features/{feature}/active/` folder. 5. Read `process/context/all-context.md` when present to choose relevant context docs. 6. For complex plans, read `process/development-protocols/references/example-complex-prd.md` before writing. 7. Include automated and manual verification gates from `process/context/tests/all-tests.md`. 8. For new or newly touched direct `*_PLAN_*.md` plans, include explicit sections for `Touchpoints`, `Public Contracts`, `Blast Radius`, `Verification Evidence`, and `Resume and Execution Handoff`. 9. Keep resume/dependency notes Markdown-structur...