functional-spec-generator

Convert design documents into a 9-section Functional Spec in Spanish Markdown.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill functional-spec-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: functional-spec-generator
Source: https://github.com/Avila-Tek/avila-tek-skill-pack/tree/main/skills/planning-2-functional-spec-generator
Command: npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill functional-spec-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the challenge of turning unstructured design documents into a structured, production-ready Functional Spec in Markdown.

Core Features & Use Cases

  • Automated conversion: Transforms a design doc (PDF, DOCX, or MD) into a complete Spec Funcional in Markdown.
  • Idioma y formato consistentes: Produce outputs in Spanish, suitable for global teams.
  • Guía de uso: Supports extracting design details for epics and descriptions, and generates sections with flows and requirements.

Quick Start

Carga un diseño (PDF, DOCX o MD) y solicita generar un Spec Funcional en Markdown en español.

Frequently Asked Questions about functional-spec-generator

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

FAQPage Schema
How do I convert a design document into a functional spec in Markdown?

To convert a design document into a functional spec in Markdown, load your design file (PDF, DOCX, or MD) and request generation. The tool transforms unstructured design inputs into a formal 9-section spec in Spanish without inventing details.

What is a functional spec and how does it structure design documents?

A functional spec formalizes unstructured design documents into a structured Markdown format. It organizes design inputs describing epics, flows, actors, and rules into a complete 9-section specification document written in Spanish.

Can I use PDF and DOCX files to generate requirements and epics documentation?

Yes, you can use PDF and DOCX files to generate requirements and epics documentation. The tool extracts design details from these formats to produce a complete Spec Funcional in Markdown, ensuring the design content is used verbatim.

Does the functional spec generator support languages other than Spanish?

No, the functional spec generator currently produces outputs specifically in Spanish. It generates a complete Spec Funcional in Markdown designed to be suitable for global teams requiring Spanish language documentation.

Why does the generated specification include invented details not in my original design?

The generated specification should not include invented details not in your original design. The tool requires the design content to be used verbatim, transforming only the structure into a 9-section spec without hallucinating new flows or rules.

What is the best way to structure epics and flows for a design doc conversion?

The best way to structure epics and flows for a design doc conversion is to clearly define actors and rules in your input file. Providing structured design inputs allows the tool to accurately extract details and map them into the 9-section spec.