Verified:GitHub

requirements-analyzer

Extracts minimum viable information from requirements documents to bootstrap an FSD blueprint.

1|Updated Feb 12, 2026

Search Tags:#workflow #documentation #validation #frontend-design #requirements-analysis #fsd-blueprint #architecture-skeleton

Ready to run

npx skills add https://github.com/dev-goraebap/grimoire --skill requirements-analyzer-dev-goraebap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-analyzer
Source: https://github.com/dev-goraebap/grimoire/tree/main/fsd-workshop/skills/requirements-analyzer
Command: npx skills add https://github.com/dev-goraebap/grimoire --skill requirements-analyzer-dev-goraebap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The requirements-analyzer reads PRD, DDD outputs, and rough notes to extract the minimal information needed to bootstrap an FSD blueprint. It writes the initial fsd-blueprint.md skeleton with the core pages, roles, and domain hints, triggering the next steps in the fsd-workshop pipeline (structure-planner, framework-adapter).

Core Features & Use Cases

Reads diverse requirement artifacts (PRD, DDD artifacts, rough memos) to identify candidate pages, routes, user roles, and domain hints.
Outputs an initial fsd-blueprint.md skeleton containing the minimum viable structure for the first design pass.
Serves as the starting gate in the fsd-workshop pipeline, handing off to subsequent skills (structure-planner, framework-adapter) for detailing and implementation.

Quick Start

Provide your requirements document and confirm the extracted pages, routes, roles, and domain hints to generate the initial fsd-blueprint.md.

Frequently Asked Questions about requirements-analyzer

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

FAQPage Schema

How do I generate an FSD blueprint from a PRD or rough requirements document?▼

Yes, DDD artifacts and rough memos can be analyzed to extract the minimum viable information needed to bootstrap an FSD blueprint, identifying pages, routes, roles, and domain hints for the skeleton.

How do I start the FSD workshop pipeline using extracted requirements?▼

Starting the FSD workshop pipeline requires confirming the extracted pages, routes, roles, and domain hints from your input document, which drafts the initial blueprint and defers layout decisions to later skills.

Does requirements analysis for an FSD blueprint include layout and design decisions?▼

No, requirements analysis for an FSD blueprint explicitly defers layout decisions to later skills, focusing only on extracting the minimum viable structure like core pages and domain hints for the first design pass.

What is the minimal information needed to bootstrap a frontend architecture skeleton?▼

The minimal information needed to bootstrap a frontend architecture skeleton includes core pages, routes, user roles, and domain hints, which are extracted and confirmed before drafting the initial blueprint.

Can I use rough notes instead of a formal PRD to create an FSD blueprint?▼

Yes, you can use rough notes instead of a formal PRD; the analysis reads diverse requirement artifacts to identify the minimum viable structure and populate the fsd-blueprint.md skeleton.