uvs-spec

Convert vague requirements into structured technical specifications with scope, data models, APIs, and acceptance criteria.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/utsavanand/uv-suite --skill uvs-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uvs-spec
Source: https://github.com/utsavanand/uv-suite/tree/main/skills/uvs-spec
Command: npx skills add https://github.com/utsavanand/uv-suite --skill uvs-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague requirements into a structured, actionable technical specification that can be handed to engineers.

Core Features & Use Cases

  • Grounded spec drafting using project context, codebase maps, and prior artifacts.
  • Interactive clarification through targeted questions to resolve ambiguity.
  • Reuse of architecture decisions and existing specs to ensure consistency.

Quick Start

Provide a clearly stated requirement and the tool will generate a complete feature specification including scope, data models, APIs, and acceptance criteria.

Frequently Asked Questions about uvs-spec

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

FAQPage Schema
How do I turn vague project requirements into a structured technical specification?

To create a technical specification from vague requirements, provide your raw project needs to generate a complete spec including scope, data models, APIs, and acceptance criteria. It uses interactive clarification and project context to resolve ambiguity.

What is the best way to align product and engineering teams when starting new features?

Aligning product and engineering teams requires a structured technical specification that defines scope and acceptance criteria. This tool drafts grounded specs using codebase maps and prior architecture decisions to ensure stakeholder alignment.

How do I generate a feature specification that reuses existing architecture decisions?

To generate a feature specification that reuses architecture decisions, the tool references prior artifacts and existing codebase maps. It outputs a complete specification at the session output path, ensuring consistency across new features.

Can I use codebase maps to draft grounded technical specifications for new features?

Yes, you can use codebase maps to draft grounded technical specifications. The tool gathers project context and references existing architecture to convert vague requirements into actionable specs for engineers.

Does interactive clarification help resolve ambiguity in software engineering requirements?

Interactive clarification resolves ambiguity in software engineering requirements by asking targeted questions during the spec drafting process. This ensures vague needs are converted into actionable technical specifications with clear acceptance criteria.