gen-spec

Generate technical specification documents from feature descriptions or PRD paths.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/pe-menezes/vibeflow-claude --skill gen-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-spec
Source: https://github.com/pe-menezes/vibeflow-claude/tree/main/skills/gen-spec
Command: npx skills add https://github.com/pe-menezes/vibeflow-claude --skill gen-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed technical specifications for software features, ensuring clarity and completeness before implementation.

Core Features & Use Cases

  • Automated Spec Generation: Creates comprehensive specs including objective, Definition of Done, scope, anti-scope, technical decisions, and applicable patterns.
  • Contextual Grounding: Leverages existing project analysis (.vibeflow/) for pattern adherence and consistency.
  • Use Case: When you have a new feature idea, use this Skill to generate a well-defined technical spec that can be directly handed off to a developer for implementation.

Quick Start

Generate a technical spec for adding a user authentication endpoint.

Frequently Asked Questions about gen-spec

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

FAQPage Schema
How do I generate a technical specification from a feature description?

To generate a technical specification, you provide a feature description or PRD path. The skill analyzes existing project patterns to produce a grounded spec document detailing objectives, scope, and technical decisions.

What should a technical spec include for a new software feature?

A comprehensive technical spec should include the objective, Definition of Done, scope, anti-scope, technical decisions, and applicable patterns. Generating these elements ensures clarity and completeness before code implementation begins.

Can I create a technical spec that matches my existing codebase conventions?

Yes, you can generate a technical spec that matches existing codebase conventions. The skill leverages existing project analysis directories to ensure pattern adherence and contextual grounding for consistency.

How do I handle technical specs that exceed file budget or Definition of Done limits?

When technical specs exceed defined limits for Definition of Done or file budget, the generation process can auto-split the document. This ensures the specification remains manageable and adheres to project constraints.

When do I need to automate technical spec generation for software development?

You need to automate technical spec generation when transitioning a new feature idea into a well-defined document. This ensures the resulting specification is complete enough for direct handoff to a developer for implementation.

What is the best way to document technical decisions and feature scope before implementation?

The best way to document technical decisions and feature scope is to generate a structured technical specification. This process defines boundaries, applicable patterns, and anti-scope to prevent scope creep during development.