What is the Requirements Engineer skill for Claude Code?

It is a specialized tool that helps developers and product owners create structured requirements catalogs including functional requirements, non-functional requirements, and constraints in Markdown format.

What is the benefit of the ID prefixing system?

It uses standard prefixes (FR for Functional, NFR for Non-Functional, C for Constraints) to prevent duplicate IDs and provide clear traceability across the project documentation.

Can I use the output for project tracking?

Absolutely. Every requirement includes a Priority (High, Medium, Low) and a Status (Open, In Progress, Implemented, etc.), making the output ready for use in project management workflows.

How does it handle non-functional requirements (NFRs)?

The skill categorizes NFRs into areas like Performance, Security, and Availability, ensuring every requirement is measurable and testable.

Does this skill follow standard user story formats?

Yes, it strictly enforces the 'As a [role], I want [goal] so that [benefit]' format for all functional requirements to ensure clarity and user-centricity.

Requirements Engineer

Name: Requirements Engineer
Author: martinellich

bymartinellich

•

Productivity & Workflow

Generates structured requirements catalogs featuring functional user stories, measurable non-functional requirements, and technical constraints.

About

The Requirements Engineer skill streamlines the software planning phase by transforming project visions into professional, structured documentation. It enforces industry best practices, such as the user story format for functional requirements and measurable quality attributes for non-functional requirements. By organizing data into standardized Markdown tables with unique IDs, priority levels, and status tracking, this skill ensures that development teams have a clear, traceable roadmap from the start of the AI Unified Process.

Key Features

Automated generation of functional requirements using standardized user story formatting.
Categorized non-functional requirement tables for performance, security, and scalability.
Formalized constraint tracking for technical, business, and schedule limitations.
8 GitHub stars
Integrated priority and status columns for seamless project management handoff.
Standardized ID prefixing (FR, NFR, C) for improved documentation traceability.

Use Cases

Establishing measurable quality benchmarks like uptime and response time for a new application.
Converting a project brief or vision document into a technical requirements specification.
Documenting technical stack boundaries and budgetary constraints before development begins.

About

Key Features

Automated generation of functional requirements using standardized user story formatting.
Categorized non-functional requirement tables for performance, security, and scalability.
Formalized constraint tracking for technical, business, and schedule limitations.
8 GitHub stars
Integrated priority and status columns for seamless project management handoff.
Standardized ID prefixing (FR, NFR, C) for improved documentation traceability.

Use Cases

Establishing measurable quality benchmarks like uptime and response time for a new application.
Converting a project brief or vision document into a technical requirements specification.
Documenting technical stack boundaries and budgetary constraints before development begins.