القائمة
PRD completeness validation — required sections for pipeline entry
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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>
Planner skill — turn a user task into a precise, atomic, verifiable ShipCodePlan
Expert in application security, OWASP Top 10, authentication, authorization, data protection, and security best practices for React, Next.js, and NestJS applications. Use when implementing authentication or authorization, reviewing code for vulnerabilities, handling sensitive data, or implementing encryption or hashing.
Validate Biome 2.3+ configuration and detect outdated patterns. Ensures proper schema version, domains, assists, and recommended rules. Use before any linting work or when auditing existing projects.
Validate Bun workspace configuration and detect common monorepo issues. Ensures proper workspace setup, dependency catalogs, isolated installs, and Bun 1.3+ best practices. Use when setting up a Bun monorepo, before adding workspace dependencies, auditing an existing Bun workspace, or validating package.json in CI.
Expert React/Next.js component architect specializing in creating consistent, reusable, and maintainable components for monorepo projects. Use when creating or refactoring UI components, reviewing component architecture, or setting up shared component patterns in a monorepo.
Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, debug agent behavior, or design content generation prompts.
