spec

Generate a detailed SPEC.md from structured software requirement interviews.

125|35|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/jh941213/my-claude-code-asset --skill spec-jh941213
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/jh941213/my-claude-code-asset/tree/main/skills/spec
Command: npx skills add https://github.com/jh941213/my-claude-code-asset --skill spec-jh941213

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SPEC-driven interviews generate precise software requirements from vague ideas.

Core Features & Use Cases

  • Structured interviews: Guides a reliable conversation to elicit functional, non-functional, and interface requirements.
  • SPEC.md generation: Outputs a complete SPEC.md ready for implementation and review.
  • Use Case: From an initial concept, capture decisions, trade-offs, and acceptance criteria to drive design.

Quick Start

Read SPEC.md and start the implementation session.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I capture software requirements from vague ideas?

Capturing software requirements from vague ideas is achieved through structured interviews that guide a conversation to elicit functional, non-functional, and interface details. This ensures all project decisions and trade-offs are documented.

How do I generate a SPEC.md file for software implementation?

To generate a SPEC.md file, you undergo a spec-driven interview that captures your project's specific requirements. The session outputs a complete SPEC.md containing acceptance criteria, ready for immediate implementation and review.

What is the best way to define functional and non-functional specifications?

Defining functional and non-functional specifications is best handled by an interactive workflow that systematically queries your project scope. It checks for completeness, ensuring no critical interface or behavioral details are missed before development.

Can I use an interactive workflow to prepare requirements for automation-ready implementation?

Yes, you can use an interactive workflow to prepare requirements for automation-ready implementation. It transforms initial concepts into precise specifications, capturing necessary interface details and checking completeness to enable automated development.

Does requirements capture through interviews work for complex software engineering projects?

Requirements capture through interviews works for complex software engineering projects by structuring the conversation to handle detailed trade-offs and acceptance criteria. It reliably extracts deep functional details regardless of the initial idea's vagueness.