# Prd Quality Gate

> PRD completeness validation — required sections for pipeline entry

- Skill: `shipshitdev/prd-quality-gate-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add shipshitdev/prd-quality-gate-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/shipshitdev/prd-quality-gate-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: shipshitdev (https://skillmd.com/u/shipshitdev)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/shipshitdev/prd-quality-gate-2

---


<prd_quality_gate>
A well-formed PRD (GitHub issue body) must contain ALL of the following sections
as markdown headings (## or ###). Missing sections reduce plan quality and risk
hallucinated scope.

Required sections:
- Executive Summary
- Problem Statement
- Goals
- Functional Requirements
- Acceptance Criteria
- Verification Plan

When the quality gate is ENABLED (blocking):
- Missing any required section → pipeline fails immediately with an actionable message
  listing the missing sections.
- The user must update the issue body and re-trigger the pipeline.

When the quality gate is DISABLED (default, warning-only):
- Missing sections → a warning is logged to the terminal lifecycle stream.
- Planning proceeds. The planner should still note gaps in its output.

Section matching is case-insensitive against ## and ### headings. Exact heading
text must appear (e.g. "## Executive Summary" or "### Goals"). Headings nested
inside code fences are ignored by convention (they are examples, not structure).
</prd_quality_gate>