requirements

Automate creation, updating, and validation of feature requirements in .docs/requirements.

1|Updated Feb 5, 2026

Search Tags:#workflow #templates #documentation #requirements #validation #traceability #feature

Ready to run

npx skills add https://github.com/eygraber/jellyfin-kmp --skill requirements-eygraber

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/eygraber/jellyfin-kmp/tree/main/.claude/skills/requirements
Command: npx skills add https://github.com/eygraber/jellyfin-kmp --skill requirements-eygraber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation, updating, and validation of feature requirements in the .docs/requirements directory.

Core Features & Use Cases

Define new feature requirements before implementation to drive scope and design.
Validate existing implementations against documented requirements to catch gaps.
Generate requirements from code when needed to bootstrap documentation and traceability.

Quick Start

Define a new feature requirement using the define workflow to capture scope, success criteria, and edge cases.

Frequently Asked Questions about requirements

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

FAQPage Schema

How do I create testable feature requirements before starting implementation?▼

You can create testable feature requirements by using the define workflow to capture scope, success criteria, and edge cases before development begins. This ensures your requirements are testable, traceable, and aligned with code.

Can I generate documentation requirements from existing source code?▼

Yes, you can generate requirements from code using the generate workflow to bootstrap documentation and traceability. This automates requirement creation in the .docs/requirements directory when documentation is missing.

How do I validate existing implementations against documented requirements?▼

You can validate existing implementations against documented requirements using the validate workflow to catch gaps. This process checks your code alignment with the requirements stored in the .docs/requirements directory.

What is the best way to maintain traceability between feature requirements and code?▼

The best way to maintain traceability is automating the creation, updating, and validation of feature requirements within the .docs/requirements directory. This ensures continuous alignment between documented scope and your codebase.

Do I need any specific dependencies to automate feature requirement updates?▼

No specific dependencies are required to automate feature requirement updates. The tool operates independently to guide teams through define, validate, and generate workflows within the .docs/requirements directory.

When should I avoid using automated workflows for feature requirements?▼

You should avoid using automated requirement workflows if your project lacks a structured .docs/requirements directory or if your feature scope cannot be broken down into testable, traceable success criteria and edge cases.