spec-feature

Interview stakeholders to generate structured feature specification files.

1|Updated Mar 1, 2026

Search Tags:#documentation #product management #feature specification #requirements gathering #structured interview

Ready to run

npx skills add https://github.com/mgoericke/claude-skills-devcontainer --skill spec-feature-mgoericke

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of gathering detailed business requirements by guiding users through a structured interview, ensuring all critical aspects of a feature are captured before development begins.

Core Features & Use Cases

Structured Interview: Asks targeted questions across Context, Behavior, Technical Hints, and Quality.
Spec File Generation: Creates a well-organized specification document in specs/ for clear project direction.
Use Case: Kick off a new feature development by using this skill to define user registration, ensuring all requirements like input validation, error handling, and success criteria are documented upfront.

Quick Start

Use the spec-feature skill to create a spec for the user registration feature.

Frequently Asked Questions about spec-feature

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

FAQPage Schema

What is a structured interview for gathering feature requirements?▼

A structured interview for feature requirements systematically collects context, behavior, technical details, and quality attributes through targeted questions. This guided process ensures all critical aspects of a new feature are captured before development begins.

How do I write a feature specification for product management?▼

You write a feature specification by using a guided, multi-stage questioning process to gather business requirements. This generates a well-organized specification document in the specs directory, providing clear project direction for development.

What's the best way to capture business requirements for a new feature?▼

The best way to capture business requirements is through a structured interview that asks targeted questions across context, behavior, technical hints, and quality. This approach streamlines gathering detailed requirements and prevents missing critical feature aspects.

Does structured requirements gathering work for defining user registration flows?▼

Yes, structured requirements gathering works for defining user registration flows. The interview process systematically collects input validation, error handling, and success criteria, documenting all necessary feature requirements upfront in a specification file.

What categories should be included in a feature specification document?▼

A feature specification document should include categories for context, behavior, technical hints, and quality attributes. Collecting these specific areas ensures comprehensive requirement capture and creates a well-organized spec for clear project direction.