prd-skill

Converts a messy PRD into a normalized Markdown document and JSON packet.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Galharel/my-codex-skills --skill prd-skill-galharel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-skill
Source: https://github.com/Galharel/my-codex-skills/tree/main/prd-skill
Command: npx skills add https://github.com/Galharel/my-codex-skills --skill prd-skill-galharel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize and refine an existing PRD (PDF/GDoc/MD text) into a structured PRD packet and a clean handoff for the User Story Mapper, especially when preparing downstream story mapping and architecture work.

Core Features & Use Cases

  • Reframes messy PRDs into a canonical Markdown PRD with clearly defined sections for downstream mapping.
  • Generates a PRD Packet JSON conforming to assets/prd_packet.schema.json.
  • Produces a User Story Mapper handoff contract embedded in the PRD packet, with optional Markdown summary for quick reference.

Quick Start

Input: a raw PRD text; Output: a normalized PRD, a PRD packet JSON, and an embedded handoff contract for the User Story Mapper.

Frequently Asked Questions about prd-skill

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

FAQPage Schema
How do I normalize a messy PRD for downstream story mapping?

To normalize a messy PRD, this Skill reads existing artifacts, reconciles changes, and outputs a canonical Markdown PRD with clearly defined sections to guide downstream story mapping workflows.

What is a PRD packet and how does it structure product requirements?

A PRD packet is a JSON file conforming to a specific schema that structures product requirements, embeds a handoff contract for the User Story Mapper, and surfaces ambiguities as open questions.

Can I use a raw text PRD to generate a handoff contract for User Story Mapping?

Yes, you can input a raw PRD text to generate a normalized PRD, a structured packet JSON, and an embedded handoff contract specifically formatted for the User Story Mapper.

Does this PRD normalization process work with existing Markdown or PDF artifacts?

Yes, the normalization process reads existing PRD artifacts in formats like PDF, GDoc, or Markdown, reconciles changes across them, and refines the content into a structured packet.

How do you handle ambiguities when converting a raw PRD into a normalized document?

When converting a raw PRD, ambiguities are surfaced as open questions within the normalized document and packet JSON, guiding refinement before downstream architecture work begins.