Can I use this for large PDF documentation?

Yes, the skill includes optimized workflows for incrementally reading and extracting requirements from large PDF files (up to 20MB) using page-specific parameters.

How does it help with 'Definition of Done'?

It provides a standardized checklist ensuring code reviews, unit tests, documentation, and QA sign-offs are completed before a story is marked as finished.

Does this skill support Gherkin syntax?

Yes, it provides specific patterns for writing Given-When-Then scenarios to define clear, testable behavior for features.

What is the INVEST criteria for user stories?

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable—a standard framework used to ensure user stories are high quality and ready for development.

What is included in the PRD template?

The template includes sections for problem statements, goals, non-goals, success metrics, prioritized user stories (P0-P2), technical design links, and risk mitigations.

Requirements Engineering

Name: Requirements Engineering
Author: yonatangross

byyonatangross

•

コラボレーションツール

Standardizes the translation of product vision into actionable engineering specifications using proven agile patterns and templates.

The requirements-engineering skill provides Claude Code with a structured framework for generating high-quality product documentation, including user stories, acceptance criteria, and full Product Requirements Documents (PRDs). By implementing industry-standard INVEST criteria and Gherkin-style testing scenarios, it bridges the gap between product vision and technical implementation. This skill ensures that engineering teams receive clear, testable, and estimable tasks while maintaining rigorous 'Definition of Ready' and 'Definition of Done' standards across the development lifecycle.

主な機能

01Automated Gherkin-style (Given-When-Then) and checklist-based acceptance criteria

02Optimized PDF handling for extracting requirements from large enterprise specification documents

03Standardized User Story creation using INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)

04Comprehensive Product Requirements Document (PRD) templates with success metrics and risk assessment

05Standardized 'Definition of Ready' and 'Definition of Done' checklists for sprint management

0669 GitHub stars

ユースケース

01Translating a high-level product vision into a structured Product Requirements Document (PRD)

02Analyzing large PDF specifications to extract actionable technical requirements and constraints

03Drafting clear, testable user stories and acceptance criteria for sprint planning

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add yonatangross/orchestkit requirements-engineering

For use in Claude.ai and ChatGPT

Download Skill