turn2spec

Converts unstructured engineering-design documents into standardized specification files.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/VitaDynamics/vita-cc-market --skill turn2spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turn2spec
Source: https://github.com/VitaDynamics/vita-cc-market/tree/main/plugins/Vengineer/skills/turn2spec
Command: npx skills add https://github.com/VitaDynamics/vita-cc-market --skill turn2spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the transformation of design documents, ADRs, or rough plans into well-structured feature specifications, ensuring clarity and consistency.

Core Features & Use Cases

  • Automated Spec Generation: Converts existing design materials into a standardized specification format.
  • Information Extraction: Identifies and structures key elements like feature names, actors, requirements, and success criteria.
  • Use Case: You have a rough design document for a new user authentication feature. This Skill can process it and generate a formal specification document, ready for development.

Quick Start

Use the turn2spec skill to transform the design document located at 'docs/designs/auth_feature.md' into a formal specification.

Frequently Asked Questions about turn2spec

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

FAQPage Schema
How do I convert rough design documents into formal feature specifications?

Converting rough design documents into formal feature specifications is done by extracting key elements like actors, core actions, and constraints, then mapping them to a standardized spec template to ensure implementation-agnostic requirements.

Can I use ADRs to generate a structured specification document?

Yes, ADRs can be used to generate structured specification documents. The tool processes architecture decision records to extract specific decisions, open questions, and success signals into a predefined formal spec format.

What is the best way to extract actors and data entities from an unstructured plan?

Extracting actors and data entities from an unstructured plan requires automated information extraction. This process identifies and structures key elements like feature names, requirements, and data entities into measurable success criteria.

Does this feature specification generator work without external dependencies?

Yes, this feature specification generator works without external dependencies. It operates standalone to map extracted design information into a predefined template, ensuring clear and consistent specification generation.

How to ensure my requirements are implementation-agnostic when writing specs?

Ensuring requirements are implementation-agnostic when writing specs involves mapping extracted design information to a predefined template. This standardizes the output to focus on measurable success criteria rather than specific implementation details.

When do I need to use a predefined template for specification generation?

You need to use a predefined template for specification generation when transforming unstructured design materials into formal feature specifications. This ensures consistency, clarity, and standardized measurable success criteria across all generated documents.