spec

Generates formal specification documents for software changes from a prompt.

Updated Nov 12, 2025
One-click install
npx skills add https://github.com/f-esquivel/dotfiles --skill spec-f-esquivel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/f-esquivel/dotfiles/tree/main/claude/skills/spec
Command: npx skills add https://github.com/f-esquivel/dotfiles --skill spec-f-esquivel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create structured specification documents for software changes without writing code, enabling teams to formalize intent and requirements quickly.

Core Features & Use Cases

  • Auto-detects spec type (feature, bug, refactor, integration, infrastructure) from user prompts and applies the correct template.
  • Produces structured, ready-to-use specification documents that include sections like Overview, Requirements, Architecture, API/Contracts, and QA criteria.
  • Supports interactive clarification when prompts are ambiguous to ensure complete, accurate specs.

Quick Start

Describe your feature, bug, or change and I will generate a complete spec draft.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I generate a specification document for a software feature without writing code?

To generate a specification document without coding, describe your intended software feature, bug, or refactor in a text prompt, and the system automatically produces a structured spec draft covering requirements, architecture, and QA criteria.

What types of specification documents can I auto-create for software engineering changes?

You can auto-create specification documents for feature, bug, refactor, integration, and infrastructure scenarios. The system detects the appropriate spec type from your prompt and applies the matching template with sections like Overview, API/Contracts, and QA.

How do I structure an API contract and architecture document for a system integration?

To structure an API contract and architecture document for an integration, input your integration scenario as a prompt. The system outputs a formal specification containing dedicated sections for architecture, API/contracts, requirements, and QA criteria.

Can I use this to write a formal spec for a bug fix or refactoring task?

Yes, you can use this to write a formal spec for a bug fix or refactoring task. It auto-detects bug or refactor scenarios from your description and generates a structured document with overview, requirements, and QA sections.

What happens if my software change description is too vague for generating a spec?

If your software change description is too vague, the system supports interactive clarification by asking follow-up questions. This ensures your ambiguous prompts are refined to produce complete and accurate specification documents.

Does generating a specification document require any prior architecture diagrams or dependencies?

Generating a specification document requires no prior architecture diagrams or dependencies. You simply provide a text prompt describing the intended software change, and the system outputs a ready-to-use formal spec draft independently.