Does this tool generate documentation files?

Yes, it creates structured Markdown files in your project directory (e.g., docs/requirements/) to maintain a persistent and version-controlled record of project specs.

What happens if my initial intent is too vague?

The skill is programmed to ask strategic clarifying questions about personas, goals, and success metrics to ensure the generated requirements meet the SMART criteria.

How does this skill help with traceability?

It maps original intent IDs (INT-*) to specific requirement keys (REQ-*), ensuring every feature is linked back to a business need via a traceability matrix.

Can I use this for non-functional requirements?

Yes, it automatically categorizes requirements into Functional (REQ-F), Non-Functional (REQ-NFR), and Data Quality (REQ-DATA) types to ensure comprehensive coverage.

What is the Requirement Extraction skill?

It is a specialized capability for Claude Code that analyzes raw user intent and creates formal, structured requirements with unique IDs and acceptance criteria.

Requirement Extraction for Claude Code

Name: Requirement Extraction for Claude Code
Author: foolishimp

byfoolishimp

Productivity & Workflow

Transforms vague user intent into structured, traceable requirements with unique keys and measurable acceptance criteria.

About

The Requirement Extraction skill bridges the gap between raw product ideas and formal engineering specifications within the Claude Code environment. By analyzing user intent, it automatically generates a hierarchy of functional, non-functional, and data-specific requirements (REQ-*), complete with business context, user stories, and clear acceptance criteria. This ensures development teams have a single source of truth that is both testable and traceable, significantly reducing scope creep and miscommunication during the initial phases of the software development lifecycle (SDLC).

Key Features

Standardized documentation output with automated Git commit workflows
Automatic transformation of vague user intent into standardized REQ-* keys
Classification of requirements into Functional, Non-Functional, and Data Quality types
Generation of detailed acceptance criteria and business context for every requirement
Automated traceability mapping from initial intent to specific requirement IDs
0 GitHub stars

Use Cases

Building formal requirements documentation and traceability matrices for greenfield projects
Kickstarting new feature development from a simple user story or feature request
Converting high-level business goals into actionable, testable engineering tasks

About

Key Features

Standardized documentation output with automated Git commit workflows
Automatic transformation of vague user intent into standardized REQ-* keys
Classification of requirements into Functional, Non-Functional, and Data Quality types
Generation of detailed acceptance criteria and business context for every requirement
Automated traceability mapping from initial intent to specific requirement IDs
0 GitHub stars

Use Cases

Building formal requirements documentation and traceability matrices for greenfield projects
Kickstarting new feature development from a simple user story or feature request
Converting high-level business goals into actionable, testable engineering tasks