skills.rest
HirogaKatageri
HirogaKatageriCOMMUNITY
Explore all skills by this author →
Website𝕏@HirogaKatageriGitHub

generate-requirements

Generate a requirements document from a product-owner agent's output.

5|Updated Feb 4, 2026
Search Tags:#automation#requirements#user-stories#acceptance-criteria#product-owner#requirements-document
One-click install
npx skills add https://github.com/HirogaKatageri/hirokata-cc-marketplace --skill generate-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-requirements
Source: https://github.com/HirogaKatageri/hirokata-cc-marketplace/tree/main/plugins/cc-develop-plugin/skills/generate-requirements
Command: npx skills add https://github.com/HirogaKatageri/hirokata-cc-marketplace --skill generate-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates ambiguous feature ideas into precise, actionable requirements documents, reducing miscommunication and aligning stakeholders early in product planning.

Core Features & Use Cases

  • Single-file output: Generates one complete requirements document in the pattern [FEATURE_NAME]_REQUIREMENTS.md.
  • Structured scope: Includes Summary, User Stories with Acceptance Criteria, Edge Cases, Technical Considerations, and Definition of Done.
  • Agent-driven discovery: Invokes a product-owner agent to gather missing details, ask clarifying questions, and produce a polished requirements file.
  • Use Case Scenarios: Useful at feature kickoff, design reviews, and handoffs to development for faster, more reliable delivery.

Quick Start

Launch this skill to create a single, ready-to-use requirements file in the project’s requirements directory. For example, generate requirements for biometric sign-in and produce BIOMETRIC_SIGNIN_REQUIREMENTS.md.

Frequently Asked Questions about generate-requirements

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

FAQPage Schema
How do I convert ambiguous feature ideas into clear, actionable requirements?▼

To convert ambiguous feature ideas into actionable requirements, this skill uses a product-owner agent to ask clarifying questions and generate a structured document containing user stories, acceptance criteria, and edge cases.

What is the format for generating user stories and acceptance criteria?▼

The format for generating user stories and acceptance criteria is a single markdown file named [FEATURE_NAME]_REQUIREMENTS.md, containing structured sections for summary, technical considerations, and definition of done.

How do I create a requirements document for development team handoff?▼

You create a requirements document for development team handoff by providing a feature idea, which the product-owner agent processes into a polished markdown file with user stories and technical considerations.

Does this requirements generation tool handle edge cases and technical considerations?▼

Yes, this requirements generation tool handles edge cases and technical considerations by enforcing a structured scope within the output document, ensuring feature discovery details are documented.

Can I use a product-owner agent to automate requirements documentation?▼

Yes, you can use a product-owner agent to automate requirements documentation, as this skill invokes the agent to gather missing details and outputs a single file for stakeholder alignment.

Related Skills

Explore More Product & Management Skills→
sohei56sohei56
15

requirement-definition

Transform product briefs and stakeholder input into validated requirements and an initial Product Backlog.

Community
Advanced
haojing8312haojing8312
154

brainstorming

Guide teams from raw ideas to validated design concepts with structured steps.

Community
Advanced
ramirlmramirlm

prd

Create and manage PRDs with user stories and acceptance criteria in JSON.

Community
Advanced
team-attentionteam-attention
171

specify

Interview teams to produce DRAFT.md and PLAN.md work plans.

Official
Advanced