spec

Convert ambiguous tickets into testable feature specifications with /spec init and /spec validate.

1|Updated Jul 24, 2025

Search Tags:#design #templates #specification #requirements #validation #phase-1

Ready to run

npx skills add https://github.com/tarrragon/book_overview_v1 --skill spec-tarrragon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/tarrragon/book_overview_v1/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/tarrragon/book_overview_v1 --skill spec-tarrragon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The /spec tooling gates the quality of requirements by turning fuzzy tickets into unambiguous, actionable specs, helping teams move from idea to implemented features with confidence.

Core Features & Use Cases

Lightweight frontmatter-driven spec scaffolding for Phase 1 design.
Supports /spec init to generate skeletons and /spec validate to surface unanswered questions.
Templates for Lite and Full modes to fit ticket complexity and iteration needs.

Quick Start

Use /spec to initialize or validate a feature spec from a ticket.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I turn vague requirements into clear, testable specs?▼

To turn vague requirements into testable specs, use a specification tool that converts ambiguous tickets into concrete feature specifications with defined acceptance criteria, codified templates, and iteration rules.

How do I generate a feature specification from an existing ticket?▼

You can generate a feature specification by running an initialization command to create a lightweight frontmatter-driven skeleton, then applying Lite or Full mode templates to fit your ticket complexity and iteration needs.

What is the best way to validate requirements and surface unanswered questions?▼

The best way to validate requirements is using a validation command that analyzes your specification against codified rules, surfacing unanswered questions to ensure the artifact is ready for implementation.

Does this specification tooling support Phase 1 internal design workflows?▼

Yes, this specification tooling explicitly targets Phase 1 internal design workflows, acting as a gatekeeper to guide teams from discovery to ready-for-implementation artifacts.

When do I need to use Lite versus Full specification templates?▼

You need Lite specification templates for simpler tickets and Full templates for complex requirements, allowing you to scale iteration depth and validation rigor according to the feature scope.