skills.rest
maverox
maveroxCOMMUNITY
Explore all skills by this author →
Website𝕏@M4veroXGitHub

requirements-architect

Extract functional and non-functional requirements from prompts into structured PRDs.

Updated Dec 11, 2025
Search Tags:#architecture#specification#requirements#decomposition#prd#workflows#stakeholders
One-click install
npx skills add https://github.com/maverox/claude-plugins --skill requirements-architect-maverox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-architect
Source: https://github.com/maverox/claude-plugins/tree/main/plugins/software-engineering-suite/skills/requirements-architect
Command: npx skills add https://github.com/maverox/claude-plugins --skill requirements-architect-maverox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze instructions, extract requirements, and transform them into a structured PRD to guide development with clear scope and traceability.

Core Features & Use Cases

  • Extraction of requirements (functional and non-functional) from stakeholder prompts.
  • Decomposition into epics, features, and tasks.
  • PRD and specification generation in PRD/ with standard templates.
  • Use Case: A product initiative from vague prompt to completed PRD.

Quick Start

Provide a project brief and I will generate a complete PRD draft in the PRD/ directory.

Frequently Asked Questions about requirements-architect

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

FAQPage Schema
How do I turn vague product requests into actionable PRDs?▼

To turn vague product requests into actionable PRDs, you provide a project brief to extract functional and non-functional requirements, generating a structured document with executive summaries, goals, and task breakdowns.

What is the best way to decompose complex initiatives into epics and tasks?▼

Decomposing complex initiatives into epics and tasks involves extracting stakeholder requirements and breaking them down into structured features, ensuring clear scope, acceptance criteria, and traceability throughout the workflow.

Can I generate a complete product specification from a simple project brief?▼

Yes, you can generate a complete product specification from a simple project brief by identifying functional and non-functional requirements, which produces a draft PRD in the PRD/ directory with technical approaches and risk sections.

What sections are included in a generated PRD for software development?▼

A generated PRD for software development includes sections for an executive summary, goals, requirements, technical approach, task breakdown, and risks, providing clear scope and traceability for development teams.

Does this PRD generation approach work for both single features and multi-epic programs?▼

Yes, this PRD generation approach works for both single features and multi-epic programs by applying requirement extraction and decomposition to initiatives of varying complexity, ensuring clear scope and acceptance criteria.

Related Skills

Explore More Product & Management Skills→
RenyEnnosRenyEnnos
1

enhance-prompt

Transforms vague UI ideas into structured, Stitch-ready prompt with design-system context.

Community
Basic
KilimcininKorOgluKilimcininKorOglu
12

task-plan

Generate and manage task breakdowns from PRD documents with Git branches.

Community
Advanced
fagnerjsfagnerjs
6

ralphi-backlog

Automate creation and synchronization of backlog.json files in PRD workflows.

Community
Intermediate
tgmarinhotgmarinho

to-prd

Convert conversation content into a Product Requirements Document and publish it to an issue tracker.

Community
Advanced