PRD Parser

Parse PRD Markdown documents into semantic structures and dependency graphs.

5|1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/fabioeloi/omni-architect --skill prd-parser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PRD Parser
Source: https://github.com/fabioeloi/omni-architect/tree/main/skills/prd-parse
Command: npx skills add https://github.com/fabioeloi/omni-architect --skill prd-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill extrai a estrutura semântica de um PRD em Markdown, identificando features, user stories, entidades de domínio, fluxos de negócio e critérios de aceite. É uma sub-habilidade do pipeline Omni Architect (Phase 1).

Core Features & Use Cases

  • Extração semântica: tokenização por headings (H1, H2, H3), classificação de seções em features, stories, requisitos, entidades e fluxos.
  • Reconhecimento de entidades: identificação de entidades de domínio usando NER para mapear o domínio do PRD.
  • Saídas estruturadas: geração de parsed_prd com features, stories, entities e flows, mais completeness_score para avaliação de completude.
  • Mapeamento de relacionamentos: construção de grafos de dependência entre features e fluxos de negócio para validação de consistência.

Quick Start

Forneça o PRD completo em Markdown como prd_content e rode o PRD Parser para retornar o parsed_prd e o completeness_score.

Frequently Asked Questions about PRD Parser

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

FAQPage Schema
How do I extract user stories and features from a PRD in Markdown?

To extract user stories and features from a PRD, the parser tokenizes Markdown headings and applies semantic classification to identify structures like features, domain entities, business flows, and acceptance criteria, outputting a structured representation.

What is semantic parsing of product requirement documents?

Semantic parsing of product requirement documents involves categorizing text sections by headings, applying named entity recognition to map domain entities, and generating dependency graphs to validate consistency across business flows.

Can I automatically map domain entities and dependencies in a product requirement document?

Yes, you can map domain entities and dependencies in a product requirement document by using named entity recognition to identify domain elements and building relationship graphs to connect features with business flows.

How do I evaluate the completeness of a product requirement document?

You evaluate the completeness of a product requirement document by parsing its Markdown input to generate a completeness score, which assesses the presence and consistency of extracted features, user stories, and flows.

Does the PRD parser require any specific Markdown formatting to extract acceptance criteria?

The parser requires a standard Markdown document structured with headings like H1, H2, and H3 to properly tokenize sections and semantically classify content such as acceptance criteria and domain entities.