requirements

Draft formal requirements.md documents for regulated epics with acceptance criteria.

1|Updated Apr 25, 2026

Search Tags:#documentation #requirements #compliance #prd #regulatory #epic #stakeholders

Ready to run

npx skills add https://github.com/daddia/space --skill requirements-daddia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/daddia/space/tree/main/.agents/skills/requirements
Command: npx skills add https://github.com/daddia/space --skill requirements-daddia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts formal requirements documents for regulated epics to ensure external traceability and compliance, replacing ad-hoc narrative briefs with structured, auditable artifacts.

Core Features & Use Cases

Generate a comprehensive requirements.md for a given epic, including problem statement, objectives with measurable targets, success metrics with baselines and targets, functional requirements with acceptance criteria, scope (Must/Should/Could/Won't), risks, and open questions.
Integrate with existing artifacts (e.g., product.md, backlog) to derive context and ensure alignment with strategy and regulatory obligations.
Provide a production-ready template that teams can review and customize for governance or audit needs.

Quick Start

Provide the epic context and constraints, and the skill will generate a complete requirements.md.

Frequently Asked Questions about requirements

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

FAQPage Schema

How do I write formal requirements for regulated epics to ensure compliance traceability?▼

Formal requirements for regulated epics are drafted by generating a requirements.md that includes a problem statement, measurable objectives, success metrics, and functional requirements with acceptance criteria to ensure external compliance traceability.

What sections should a PRD include for payments and auth compliance domains?▼

A PRD for compliance domains should include an overview, problem statement, objectives with measurable targets, success metrics with baselines, functional requirements with acceptance criteria, scope, risks, and open questions to satisfy regulatory audits.

Can I generate a requirements document from an existing product.md and backlog?▼

Yes, generating a requirements document can consume existing product.md and related artifacts to derive context, ensuring alignment with product strategy and regulatory obligations while producing a comprehensive requirements.md output.

How do I structure functional requirements with acceptance criteria for stakeholder review?▼

Structure functional requirements by pairing each specific behavior with explicit acceptance criteria, then grouping them within a formal requirements.md alongside scope boundaries using Must, Should, Could, and Won't categorization for stakeholder review.

When do I need a formal requirements document instead of an ad-hoc narrative brief?▼

A formal requirements document is needed when starting a new epic or refining requirements in regulated domains like payments, auth, or compliance, replacing ad-hoc narrative briefs with structured, auditable artifacts for governance needs.