skills.rest
divad12
divad12COMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-interview

Interview users to generate feature specifications in docs/specs/.

25|4|Updated Sep 5, 2010
Search Tags:#documentation#specification#requirements#interview#feature#product-management#docs-specs
One-click install
npx skills add https://github.com/divad12/dotfiles --skill spec-interview-divad12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-interview
Source: https://github.com/divad12/dotfiles/tree/main/.claude/skills/spec-interview
Command: npx skills add https://github.com/divad12/dotfiles --skill spec-interview-divad12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of interviewing a user to gather requirements and produce a complete feature spec document.

Core Features & Use Cases

  • Conduct structured, multi-round interviews to uncover requirements, edge cases, and data-model implications.
  • Generate a formal spec in docs/specs/ with clear sections for overview, user stories, acceptance criteria, and constraints.
  • Use in workflows when a user asks for a spec or says "spec interview", "create a spec", or "write a spec".

Quick Start

Begin a guided user interview and generate a complete feature specification in docs/specs/.

Frequently Asked Questions about spec-interview

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

FAQPage Schema
How do I write a feature specification from rough product requirements?▼

A feature specification is formalized through a multi-round interview that uncovers requirements and edge cases. This process extracts details and generates a structured document with user stories, acceptance criteria, and constraints in docs/specs/.

What is the best way to gather product management requirements for documentation?▼

Gathering product management requirements is best achieved through structured, multi-round interviews. This method identifies edge cases and data-model implications, translating them directly into production-ready documentation within the docs/specs/ directory.

How do I create a formal spec when a feature outline is unclear?▼

Creating a formal spec from an unclear outline involves conducting a guided interview to clarify the request. This extracts missing requirements and formalizes them into a structured document featuring an overview, user stories, and constraints.

Does structured spec writing work for generating user stories and acceptance criteria?▼

Structured spec writing works effectively for generating user stories and acceptance criteria. By applying a multi-phase interview approach, it captures the necessary constraints and details required for production-ready feature documentation.

When do I need a formal specification document in docs/specs/?▼

You need a formal specification document in docs/specs/ when requirements must be formalized for production readiness. It is necessary when a user requests a spec, an outline is unclear, or structured documentation is needed.

Related Skills

Explore More Product & Management Skills→
dariomazzitellireplik-coderdariomazzitellireplik-coder
1

sdd-requirement

Conduct structured interviews to define software requirements and generate requirement.md.

Community
Advanced
raphaelmansraphaelmans

user-stories

Convert PRDs, specs, or descriptions into domain-based user stories with acceptance criteria.

Community
Advanced
Sumeet138Sumeet138
1

track-management

Organize Conductor tracks with spec.md, plan.md, and tracks.md.

Community
Advanced
madebyarismadebyaris
192

sdd-evolve

Update specification files and changelog after implementation discoveries.

Community
Intermediate