PRD completeness validation — required sections for pipeline entry
npx skills add https://github.com/shipshitdev/shipcode --skill prd-quality-gateCopia y pega este comando en Claude Code para instalar la habilidad
Executor skill — implement an approved ShipCodePlan inside a git worktree
Verifier skill — confirm a diff matches the plan and satisfies acceptance criteria
Ensure ShipCode-required GitHub labels exist on the current repository using the gh CLI and the canonical definitions in packages/shared/src/github-labels.ts.
Planner skill — turn a user task into a precise, atomic, verifiable ShipCodePlan
Reviser skill — rewrite a plan to address adversarial review findings
Use when the user wants to draft, scope, or formalize a feature for shipcode — "write a PRD for X", "let's plan X", "scope this out", "what should X do", or when a GitHub issue body needs to be fleshed out before the pipeline plans it. Writes a PRD that maps cleanly onto shipcode's pipeline (objective / acceptanceCriteria / outOfScope / estimatedComplexity) so the planner agent can consume it without re-elicitation. Do NOT use for code edits, debugging, or PR reviews.
| name | prd-quality-gate |
| description | PRD completeness validation — required sections for pipeline entry |
<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:
Additional quality rules:
When the quality gate is ENABLED (blocking):
When the quality gate is DISABLED (default, warning-only):
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>
