osovv/vv-opencode

vv-execute

Use when given an approved plan.xml to validate it, choose an execution mode with the user, and execute tasks with verification and commits

vv-plan

Use AFTER an approved spec exists in .vvoc/specs/<id>/spec.xml — reads the approved spec and optional sibling design-context.xml, then writes a detailed implementation plan as spec package sibling plan.xml

vvoc-usage-analytics

Use when the user asks about token usage, cache hit rate, cache efficiency, model or provider consumption, session costs, or whether a vvoc release or OpenCode upgrade changed caching behavior. Runs read-only analysis over vvoc analytics (CLI and JSONL) and…

vv-spec

Use BEFORE any implementation or planning — interviews the user one question at a time, proposes approaches, presents a design, writes a spec document to .vvoc/specs/YYYY-MM-DD-<slug>/spec.xml, and optionally creates a design-context.xml companion for complex…

vv-handoff

Use at the end of a session to write a project-local XML handoff note from already-visible context only.

vv-review

Use for review requests — routes to reviewer sub-agents through a vvoc review-only workflow, reports findings, and stops before fixes

vv-reflect

Use at the end of a long development, debugging, bugfix, ops, or investigation session to preserve reusable findings as durable repository memory for future agents.