requirements-phase

Name: requirements-phase
Availability: InStock
Author: MetaSaver

Generate PRDs and epics/stories with HITL clarification loops.

Updated Aug 23, 2026

Search Tags:#workflow #documentation #requirements #product management #clarification #PRD #human-in-the-loop

Ready to run

npx skills add https://github.com/metasaver/metasaver-marketplace --skill requirements-phase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-phase
Source: https://github.com/metasaver/metasaver-marketplace/tree/main/plugins/metasaver-core/skills/workflow-steps/requirements-phase
Command: npx skills add https://github.com/metasaver/metasaver-marketplace --skill requirements-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating clear and complete Product Requirements Documents (PRDs) from initial prompts often requires iterative clarification. This Skill automates PRD drafting with a human-in-the-loop (HITL) feedback loop.

Core Features & Use Cases

Automated PRD Drafting: Spawns a Business Analyst agent to draft an initial PRD based on the user prompt and context, accelerating the documentation process.
Human-in-the-Loop Clarification: Engages the user in a loop via AskUserQuestion to resolve questions and uncertainties, ensuring the PRD accurately reflects requirements.
Project Folder Creation: Automatically sets up a structured project folder (docs/projects/{yyyymmdd}-{descriptive-name}/) for the PRD, maintaining organization.
Use Case: For a new feature request, this skill drafts the PRD, asks the user clarifying questions about scope or edge cases, and iteratively refines the document until all requirements are clear.

Quick Start

Initiate the requirements phase to draft a PRD for "Implement a new user dashboard with real-time data updates."

Frequently Asked Questions about requirements-phase

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

FAQPage Schema

How do I create a PRD with clarification loops instead of writing it manually?▼

PRD creation with human-in-the-loop clarification automates drafting by spawning a Business Analyst agent to generate an initial document, then engages you in iterative feedback loops via questions to resolve uncertainties and refine requirements until the PRD accurately reflects your needs.

Can I generate epics and user stories automatically from a PRD?▼

Yes. This Skill extracts epics and user stories from the PRD analysis, generates them with sequential numbering (EPIC-001, US-001), and organizes them under a structured project folder (docs/projects/{yyyymmdd}-{descriptive-name}/) alongside the prd.md document.

What's the best way to structure project documentation and requirements artifacts together?▼

Automated project folder creation establishes a consistent structure under docs/projects with timestamped, descriptive naming. The Skill populates this folder with the PRD and organized epics and stories, maintaining all artifacts in one location for easy reference and version control.

How does human-in-the-loop feedback improve requirement clarity during PRD drafting?▼

The Skill iteratively asks clarifying questions through AskUserQuestion prompts to resolve ambiguities about scope, edge cases, and functional gaps. This back-and-forth ensures the final PRD and derived stories capture intent accurately before development begins.

Do I need to manually format epic and story numbering in my PRD?▼

No. The Skill automatically applies sequential numbering templates (EPIC-001, US-001) across both the PRD document and generated story artifacts, eliminating manual formatting and ensuring consistency.

When should I use PRD generation instead of writing requirements from scratch?▼

Use PRD generation when you have an initial product concept or feature request but need structured, clarified requirements. The Skill accelerates documentation when scope is unclear and benefits from iterative refinement—ideal for new feature requests, product pivots, or cross-team alignment.