Skip to main content

prd-quality-gate

PRD completeness validation — required sections for pipeline entry

소스 정보

저장소
shipshitdev/shipcode
최근 소스 활동
2026년 5월 2일 11:41
감지된 SKILL.md 언어
영어
스타
7
포크
1

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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: - Executive Summary - Problem Statement - Goals - Non-Goals - User Stories - System Specification - Functional Requirements - Non-Functional Requirements - Feature Phase Breakdown - Success Criteria - Out of Scope - Dependencies - Verification Plan - Risks & Open Questions Additional quality rules: - Feature Phase Breakdown must describe exactly three ordered phases. - Success Criteria and Out of Scope must each contain at least one concrete bullet. - System Specification must cover observable behavior and boundaries, not implementation file names. 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>
GitHub에서 보기