prd-analysis

Parse PRD files, URLs, or text into structured requirements artifacts.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hamzaPixl/pixl-ai --skill prd-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-analysis
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/prd-analysis
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill prd-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts unstructured product requirements documents (files, URLs, or pasted text) into a standardized, machine-readable project foundation so downstream planning and review workflows can run reliably without manual reformatting.

Core Features & Use Cases

  • Input ingestion: Accepts file paths, URLs, or pasted text and saves the canonical source to .context/prd.md.
  • Structured analysis: Parses content into eight categories (overview, domain model, architecture, milestones, features, technical requirements, risks, open questions) using explicit extraction and marked inferences.
  • Atomic decomposition & artifacts: Produces a requirements JSON with R-IDs, MoSCoW priorities, acceptance criteria, and search hints, plus a project-overview markdown that downstream skills consume.
  • Clarification flow: Prioritizes and prompts the user with top clarifying questions and updates artifacts based on answers.
  • Persistence & integration: Writes .context/spec/requirements.json and .context/project-overview.md and optionally registers artifacts with the pixl CLI if available.

Quick Start

Analyze the provided PRD and write structured artifacts to .context/spec/requirements.json and .context/project-overview.md.

Frequently Asked Questions about prd-analysis

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

FAQPage Schema
How do I convert a product requirements document into structured JSON for task planning?

You can analyze a product requirements document by ingesting files, URLs, or pasted text to generate a structured JSON artifact containing atomic requirements with R-IDs, MoSCoW priorities, and acceptance criteria for downstream task planning.

What is the best way to parse PRD text into categorized project artifacts?

Parsing PRD text into categorized project artifacts involves extracting content into eight predefined categories: overview, domain model, architecture, milestones, features, technical requirements, risks, and open questions, then persisting the results as machine-readable files.

Can I use a markdown PRD file to generate a project overview with acceptance criteria?

Yes, you can use a markdown PRD file as input to generate a project-overview markdown file alongside a requirements JSON that includes MoSCoW priorities and acceptance criteria for each decomposed atomic requirement.

How do you prioritize requirements when decomposing a spec for engineering teams?

When decomposing a spec for engineering teams, requirements are prioritized using the MoSCoW method, assigning each atomic requirement an R-ID and specific acceptance criteria to ensure structured downstream planning.

Does PRD analysis work with unstructured text pasted directly into the prompt?

Yes, PRD analysis works with unstructured text pasted directly into the prompt, saving the canonical source to a markdown file before parsing it into structured categories and atomic requirements.

What limitations exist when ingesting product requirements from external URLs?

When ingesting product requirements from external URLs, the tool relies on explicit extraction and marked inferences to parse content into eight categories, meaning highly ambiguous or unstructured web pages may require additional clarification prompts to ensure accurate decomposition.