vc-setup

vc-generate-context creates and updates process/context/all-context.md, your project's durable knowledge layer for sharing context across agents. It supports full scans for new projects, delta updates for existing repos, and grouped context generation for organized documentation. Validation scripts ensure routing integrity before context is marked refreshed.

vc-audit-context validates your project's context layer, routing tables, and shared-skill discovery across agents. Run built-in validators to catch missing context files, broken skill references, and protocol misalignment, then regenerate your machine-readable skill catalog.

vc-context-discovery is the canonical context-loading entry point for every agent session. It discovers and surfaces all nested files under process folders, extracts frontmatter metadata, and routes context by domain using keyword matching. Use the auto-discovery script or keyword-first routing to load exactly the docs your task needs.

vc-debug guides you through structured investigation before any fix, combining root cause tracing, defense-in-depth validation, and verification protocols. Handle code bugs, system failures, CI/CD issues, and performance degradation with frameworks for each scenario—from call stack analysis to log inspection to frontend verification.

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-spec turns research findings and user intent into a reviewable requirements document written for stakeholders, not engineers. It captures what users want and why before any implementation approach is chosen, serving as the authoritative bridge between discovery and planning. The skill enforces structured sections—from user stories through acceptance criteria—ensuring specs remain focused on observable outcomes and user-facing behavior.