prd-normalizer

Normalize unstructured product requirement documents into an 11-field markdown format.

Updated Apr 12, 2026

Search Tags:#workflow #planning #documentation #normalization #prd #product-management

Ready to run

npx skills add https://github.com/olivermorgan2/workflow-generator --skill prd-normalizer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-normalizer
Source: https://github.com/olivermorgan2/workflow-generator/tree/main/skills/prd-normalizer
Command: npx skills add https://github.com/olivermorgan2/workflow-generator --skill prd-normalizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the friction caused by inconsistent product documentation by transforming disparate notes, briefs, or rough PRDs into a single, canonical format that downstream planning tools can reliably process.

Core Features & Use Cases

Canonical Mapping: Automatically maps unstructured input into an 11-field normalized PRD structure.
Intelligent Elicitation: Identifies missing critical information and prompts the user with batched, context-aware questions to fill gaps.
Workflow Integration: Acts as the essential bridge between initial ideation and technical scoping, ensuring downstream skills like prd-to-mvp and adr-writer have consistent data to work with.

Quick Start

Run the prd-normalizer skill on your current design/brief.md file to generate a standardized normalized PRD.

Frequently Asked Questions about prd-normalizer

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

FAQPage Schema

How do I standardize unstructured product requirement documents for development planning?▼

Standardize unstructured product requirement documents by mapping semantic content into a canonical 11-field normalized PRD markdown format. This process ensures consistency for downstream development workflows by extracting data from raw notes or standard PRDs.

What is the best way to normalize rough product briefs into a consistent format?▼

Normalizing rough product briefs involves transforming disparate notes into a single canonical markdown artifact. The process identifies missing critical fields and queries the user with batched context-aware questions to fill information gaps before generating the final structured document.

How do I handle missing information when structuring a PRD?▼

Handle missing information during PRD structuring through intelligent elicitation. The normalization process automatically identifies missing critical fields in the input file and prompts the user with batched, context-aware questions to ensure all eleven canonical fields are populated.

Can I use this normalization process with any markdown product brief?▼

Yes, you can use this process with any valid PRD-like markdown input file, such as a rough brief or standard notes. It requires no additional dependencies and processes the raw semantic content to produce a standardized markdown artifact for project planning.

Why does my normalized PRD need an 11-field canonical structure?▼

An 11-field canonical structure is needed to provide consistent data for downstream technical scoping workflows. Normalizing unstructured input into this specific format ensures that subsequent development planning tools can reliably parse and process the product requirements.

When should I avoid automating product spec normalization?▼

Avoid automating product spec normalization if the input file lacks valid PRD-like semantic content, as the process requires recognizable product requirements to map into the canonical 11-field structure and trigger accurate missing field elicitation.