spec

Interview users to generate a SPEC.md with goals, constraints, and acceptance criteria.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Hoang604/get-thing-done --skill spec-hoang604
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/Hoang604/get-thing-done --skill spec-hoang604

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requirements analysts waste time guessing project scope. This Skill guides user interviews to extract clear requirements and materialize them into a SPEC.md file.

Core Features & Use Cases

  • Structured Interview Flow: Elicit goals, constraints, and acceptance criteria.
  • AUTOMATED SPEC Generation: Produce a fully formed SPEC.md at ./.gtd/<task_name>/SPEC.md with status, timestamps, and sections for Must Have, Nice to Have, Won't Have, and Constraints.
  • Validation & Confirmation: Mirror understanding and require user confirmation before writing SPEC.md.

Quick Start

Conduct an interview to define the task and generate ./.gtd/<task_name>/SPEC.md.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I extract clear project requirements from user interviews?

Extracting clear requirements from user interviews requires a structured flow that elicits goals and constraints, mirrors understanding for validation, and materializes confirmed details into a SPEC.md file.

What is the best way to generate a spec.md file for a new project feature?

The best way to generate a spec.md file is through an automated interview process that defines the task scope, captures acceptance criteria, and outputs the finalized document into a designated task directory.

How do I define scope and acceptance criteria before starting a new project?

Define scope and acceptance criteria by conducting a structured interview to separate must-have features from nice-to-have items, identify constraints, and require user confirmation before formalizing the details.

Can I automate creating project specifications without manually writing markdown?

Automating project specification creation is possible by running an interview flow that captures goals and constraints, automatically generating a fully formed markdown file with status and timestamps without manual writing.

What should be included in a project specification document?

A project specification document should include the project goal, scope, constraints, acceptance criteria, and categorized sections for must-have, nice-to-have, and won't-have features, along with metadata and timestamps.

Does generating a spec document require any specific task management setup?

Generating a spec document requires a specific directory structure, saving the finalized markdown file directly into a defined task folder path to maintain organization and integrate with task management workflows.