shipshitdev/prd-quality-gate
bundles/dev-loop/skills/prd-quality-gate/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library prd-quality-gateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 2, 2026, 5:24 AM139.9s1 file scanned
SKILL.md
- 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.
- version:
- 1.1.0
- tags:
- prd, planning, validation, quality-gate, spec, requirements, ears
<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 <trigger> THE SYSTEM SHALL <response> (event-driven)
- WHILE <state> THE SYSTEM SHALL <response> (state-driven)
- WHERE <feature> THE SYSTEM SHALL <response> (optional feature)
- IF <condition> THEN THE SYSTEM SHALL <response> (unwanted behavior)
- THE SYSTEM SHALL <invariant> (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>
Related Skills
shipshitdev/typescript-refactor
development
VerifiedTrustedCommunity
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/typescript-expert
tools
VerifiedTrustedCommunity
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/turborepo
tools
VerifiedTrustedCommunity
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/tailwind
tools
VerifiedTrustedCommunity
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.
30SKILL.mdUpdated Jul 14, 2026