vc:generate-plan

To generate an implementation plan from a PRD, describe the feature to the assistant, which then reads your references and enforces the repo's plan contract to output an authoritative plan artifact directly into the designated active plan folder.

Structuring a phase program plan requires generating an umbrella plan alongside individual per-phase plans, ensuring all artifacts align with the repo's plan contract and are output to the appropriate active plan directories.

Yes, the plan generation workflow enforces the repository's existing plan contract by reading integrated context references and standardizing all output artifacts into the designated active plan folders.

Yes, you can use this to standardize project planning for normal work by creating a single authoritative plan file that aligns team expectations and execution with a single source of truth.

You need an umbrella plan for phase programs requiring an overarching strategy plus per-phase direct plans, while a single plan file suffices for normal work or isolated system features.

Generated plan artifacts must output to specific active plan folders like process/general-plans/active or process/features/{feature}/active to standardize project planning and maintain a single source of truth across the repository.