vv-spec

Guide users through a dependency-ordered decision tree to generate spec.xml documents.

11|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/osovv/vv-opencode --skill vv-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vv-spec
Source: https://github.com/osovv/vv-opencode/tree/main/templates/skills/vv-spec
Command: npx skills add https://github.com/osovv/vv-opencode --skill vv-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the risk of incomplete, misaligned specification documents that cause rework and scope creep by guiding users through a structured, decision-tree interview to capture every required design decision before implementation begins.

Core Features & Use Cases

  • Guided Decision-Tree Interview: Walks through all spec sections (goal, architecture, tech stack, components, data flow, error handling, testing, non-goals) one question at a time, with recommended answers, trade-off analysis, and codebase evidence where available.
  • Automated Spec Generation: Produces a structured spec.xml document saved to the canonical .vvoc/specs/YYYY-MM-DD-<slug>/ directory, plus an optional design-context.xml companion for complex sessions with non-obvious tradeoffs.
  • Use Case: For a new feature like a batch data migration tool, use this skill to walk through all design decisions (data model, error handling, rollback semantics) and get a complete, user-approved spec before any code is written.

Quick Start

Invoke the vv-spec skill to start a guided decision-tree interview that will generate a complete structured spec document for your planned feature.

Frequently Asked Questions about vv-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gather complete software requirements before implementation to avoid scope creep?

Guided spec creation eliminates scope creep by walking you through a dependency-ordered decision tree, capturing all design decisions, tradeoffs, and edge cases before coding begins.

What is spec-first development and when do I need a structured specification document?

Spec-first development requires structured specification documents to define architecture, data flow, and error handling before implementation, preventing incomplete or misaligned project requirements.

How do I draft a spec.xml document for a new software feature?

Automated spec generation produces a structured spec.xml document by guiding you through an interview covering goals, tech stack, components, testing, and non-goals, saving it to a canonical date-prefixed directory.

Can I capture design tradeoffs and edge cases during pre-implementation planning?

Pre-implementation planning captures design tradeoffs and edge cases through a guided interview that provides recommended answers and codebase evidence for each spec section.

Does spec-first development work for complex sessions with non-obvious tradeoffs?

Spec-first development handles complex sessions by optionally generating a curated design-context.xml companion file alongside the main spec document to capture non-obvious tradeoffs.

What is the best way to plan architecture and data flow for a batch data migration tool?

Guided spec planning covers data model, error handling, and rollback semantics for batch data migration tools by walking through all design decisions to produce a user-approved spec.