skills.rest
vertexcover-io
vertexcover-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spec-generation

Convert approved design documents into EARS-formatted SPEC.md files.

4|Updated Jan 1, 2026
Search Tags:#planning#specification#requirements#verification#edge-cases#ears#design-doc
One-click install
npx skills add https://github.com/vertexcover-io/tarash --skill spec-generation-vertexcover-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-generation
Source: https://github.com/vertexcover-io/tarash/tree/main/.claude/skills/spec-generation
Command: npx skills add https://github.com/vertexcover-io/tarash --skill spec-generation-vertexcover-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting approved design documents into a structured SPEC.md is error-prone and time-consuming; this skill automates the process and ensures a consistent, testable spec.

Core Features & Use Cases

  • Automatic SPEC generation: Converts approved brainstorms into EARS-formatted requirements, edge cases, and a verification matrix.
  • Directory structure output: Writes SPEC.md to docs/plans/<feature-name>/SPEC.md aligned with planning phases.
  • Guided workflow: Keeps planning steps aligned with design approvals and planning milestones.

Quick Start

Provide path to an approved design doc and trigger SPEC.md generation using the skill.

Frequently Asked Questions about spec-generation

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

FAQPage Schema
How do I convert a design document into a testable specification?▼

To convert a design document into a testable specification, use an automated process that transforms approved brainstorms into a structured SPEC.md using the EARS format.

What is the EARS format for writing software requirements?▼

The EARS format is a structured approach for writing software requirements that ensures specifications are testable, incorporating measurable requirements and edge cases sourced from design documents.

How do I generate a SPEC.md from an existing design doc?▼

Provide the path to an approved design document and trigger the SPEC.md generation workflow to output requirements and edge cases to docs/plans/<feature-name>/SPEC.md.

Can I automatically include edge cases and a verification matrix in my requirements?▼

Yes, you can automatically include edge cases and a verification matrix by transforming approved design documents into a structured SPEC.md aligned with planning milestones.

Does generating a specification require an already approved brainstorm design document?▼

Yes, specification generation requires an approved brainstorm design document as input to produce a structured and measurable SPEC.md aligned with planning workflows.

What is the best way to structure feature specifications for testability?▼

The best way to structure feature specifications for testability is using the EARS format within a SPEC.md, pairing requirements with edge cases and a verification matrix.

Related Skills

Explore More Product & Management Skills→
n0rvynn0rvyn
1

brainstorm

Generate and evaluate design options before implementation.

Community
Advanced
gkswls5006-webgkswls5006-web

moai-workflow-spec

Orchestrate SPEC workflows with EARS requirements and Plan-Run-Sync integration.

Community
Advanced
dobrinz123dobrinz123

gsd-progress

Check project progress and route to the next action using workflow context.

Community
Advanced
bromankobromanko

ears-requirements

Generate EARS specifications from unstructured text, design documents, user stories, or codebases.

Community
Intermediate