Name: prd-quality-gate
Author: shipshitdev

About

Imported from shipshitdev/skills (skills/prd-quality-gate/SKILL.md). Install upstream with npx skills add shipshitdev/skills --skill prd-quality-gate. Copyright stays with the author.

<prd_quality_gate> A well-formed PRD (or the issue body that serves as one) must contain ALL of the following sections as markdown headings (## or ###).

Required sections:

Executive Summary
Problem Statement
Goals
Functional Requirements
Acceptance Criteria
Verification Plan

Acceptance Criteria must be written in EARS (Easy Approach to Requirements Syntax) so each bullet is machine-checkable and pass/fail without judgement. Every bullet under Acceptance Criteria must match one of:

WHEN THE SYSTEM SHALL (event-driven)
WHILE THE SYSTEM SHALL (state-driven)
WHERE THE SYSTEM SHALL (optional feature)
IF THEN THE SYSTEM SHALL (unwanted behavior)
THE SYSTEM SHALL (ubiquitous)

A bullet that does not match this grammar (case-insensitive regex ^\s*(\d+\.\s*)?(WHEN|WHILE|WHERE|IF|THE SYSTEM)\b.*\bSHALL\b) is free-form prose, not a verifiable criterion.

When the quality gate is ENABLED (blocking):

Missing any required section → fail immediately with an actionable message listing the missing sections.
Any Acceptance Criteria bullet that is not EARS-shaped → fail, quoting each offending bullet and the EARS pattern it should take.
The author must update the PRD and re-run the gate before planning proceeds.

When the quality gate is DISABLED (default, warning-only):

Missing sections → log a warning.
Non-EARS Acceptance Criteria bullets → log a warning listing each offending bullet.
Planning proceeds. The planner should still note the 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>

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/shipshitdev-skills-prd-quality-gate/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

shipshitdev-skills-prd-quality-gate.ocm.jsonjson

{
  "ocm": "1",
  "id": "shipshitdev-skills-prd-quality-gate",
  "kind": "skill",
  "name": "prd-quality-gate",
  "description": "PRD completeness validation. Use to check that a PRD (or issue body that serves as one) contains the required sections before it is handed to a planning/execution agent, so the plan is built from a complete spec instead of hallucinated scope. Run it as a blocking gate or a warning-only lint.",
  "publisher": "shipshitdev",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "prd",
      "planning",
      "validation",
      "quality-gate",
      "spec",
      "requirements",
      "ears",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "PRD completeness validation. Use to check that a PRD (or issue body that serves as one) contains the required sections before it is handed to a planning/execution agent, so the plan is built from a complete spec instead of hallucinated scope. Run it as a blocking gate or a warning-only lint."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/shipshitdev/skills",
      "path": "skills/prd-quality-gate/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/shipshitdev/skills/blob/HEAD/skills/prd-quality-gate/SKILL.md",
      "key": "shipshitdev/skills/skills/prd-quality-gate/SKILL.md"
    }
  },
  "instructions": "<prd_quality_gate>\nA well-formed PRD (or the issue body that serves as one) must contain ALL of the\nfollowing sections as markdown headings (## or ###).\n\nRequired sections:\n\n- Executive Summary\n- Problem Statement\n- Goals\n- Functional Requirements\n- Acceptance Criteria\n- Verification Plan\n\nAcceptance Criteria must be written in EARS (Easy Approach to Requirements\nSyntax) so each bullet is machine-checkable and pass/fail without judgement.\nEvery bullet under Acceptance Criteria must match one of:\n\n- WHEN <trigger> THE SYSTEM SHALL <response>        (event-driven)\n- WHILE <state> THE SYSTEM SHAL",
  "cost": {
    "context_tokens": 478
  }
}

Fetch it by URL: GET /api/v1/registry/shipshitdev-skills-prd-quality-gate/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.