requirements

Extract and structure requirements from unstructured input into a PRD-ready document.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/maggit/claude-workspace --skill requirements-maggit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/maggit/claude-workspace/tree/main/skills/requirements
Command: npx skills add https://github.com/maggit/claude-workspace --skill requirements-maggit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gather and organize raw inputs such as notes, transcripts, and rough ideas into a single, actionable requirements document that can feed PRDs and engineering specs.

Core Features & Use Cases

  • Automatic extraction and structuring of inputs into sections: Summary, Functional Requirements, Non-Functional Requirements, Constraints, Assumptions, Dependencies, Acceptance Criteria, and Gaps.
  • Clear, testable requirements formatting with priority tags and traceability links to original input.
  • Use Case: transform stakeholder notes into a PRD-ready document for product, design, and engineering teams.

Quick Start

Provide raw notes or a rough feature idea and run the skill to generate a complete requirements document.

Frequently Asked Questions about requirements

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

FAQPage Schema
How do I extract structured requirements from unstructured meeting notes?

To extract structured requirements from unstructured meeting notes, you input the raw text to automatically generate sections like functional requirements, constraints, and acceptance criteria. This transforms scattered stakeholder input into a clear, PRD-ready document.

What is the best way to turn rough feature ideas into a PRD-ready document?

The best way to turn rough feature ideas into a PRD-ready document is using an automated structuring tool that formats needs into functional requirements, non-functional concerns, and traceability links. This formalizes inputs for product, design, and engineering teams.

Can I format both functional and non-functional requirements from a rough transcript?

Yes, you can format both functional and non-functional requirements from a rough transcript. The processing logic automatically categorizes raw input into functional needs, non-functional concerns, assumptions, dependencies, and gaps capture for comprehensive coverage.

Does generating requirements from raw text include acceptance criteria and traceability?

Yes, generating requirements from raw text includes acceptance criteria and traceability. The output features clear, testable requirements formatting with priority tags and direct traceability links back to the original stakeholder input.

How do I identify gaps and assumptions when gathering stakeholder requirements?

To identify gaps and assumptions when gathering stakeholder requirements, process the raw inputs through an automated extraction tool. It explicitly captures missing information and underlying assumptions alongside the primary functional and non-functional requirements.