mcpField
P
prd-quality-gate

prd-quality-gate

github.com/shipshitdevDevelopment3865 installsUpdated 2d ago
Repository

About prd-quality-gate

A read-only gate for reviewing requirements and implementation plans before agent execution. It distinguishes draft linting from execution readiness, returning a verdict, evidence, and specific blockers.

Key features

  1. 01Lint requirements drafts
  2. 02Assess execution readiness
  3. 03Check acceptance criteria
  4. 04Inspect repository evidence
  5. 05Report blockers and remediation owners

Use cases

  1. 01Review requirements before planning
  2. 02Check a plan before agent handoff
  3. 03Identify unresolved implementation decisions
  4. 04Verify checks and evidence are current

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shipshitdev/skills --skill prd-quality-gate

After installing, type/prd-quality-gatein Claude Code to confirm it loaded.

Bundled filesreferences/execution-readiness.md

Details

From the project README

PRD Quality Gate

Contract

Inputs:

  • Requirements, implementation plan, target repository, and requested mode.
  • Live issue body/comments and repository revision when execution is requested.

Outputs:

  • draft-lint: warnings for incomplete requirements; never execution permission.
  • execution-readiness: READY or BLOCKED, evidence for each check, and exact gaps.

Creates/Modifies:

  • No implementation or tracker mutations; return findings to the calling engine.

External Side Effects:

  • Read-only repository and tracker inspection.

Confirmation Required:

  • None for read-only validation. Preserve the caller's access restrictions.

One shared contract

Read Execution readiness before validating or supplying preparation templates. This reference owns the requirements template, plan template, decomposition rule, decision boundary, and readiness checklist. Consumers read this reference from the sibling path ../prd-quality-gate/references/execution-readiness.md. Do not maintain alternate copies.

Use draft-lint for an explicit requirements-only review. Check required headings, nonempty scope and EARS acceptance criteria; report missing information as warnings. Draft lint may help the planner continue research. It cannot mark an issue ready for an executor, even if every heading is present.

Use blocking execution-readiness for feature-intake, execution handoff, AFK classification, or any request to declare work ready for an agent. An unspecified mode in one of those contexts means execution-readiness. Otherwise default to draft-lint and label that limitation in the output.

Validate meaning and evidence

Check actual behavior, complete decisions, repository evidence, verification feasibility, and freshness. Headings and EARS grammar alone cannot establish readiness. Read source files and command definitions; distinguish observed facts from proposed changes. Fail unknowns that require an executor decision.

Accept numbered or checkbox acceptance bullets, removing their marker and optional AC-N: prefix before checking EARS. Accept WHEN, WHILE, WHERE, IF ... THEN, or THE SYSTEM SHALL forms with an observable response. Give each criterion a stable ID for the plan-to-verification mapping. Reject subjective pass conditions and criteria that merely repeat a heading.

Return the validation mode, verdict, issue/plan identity, inspected revision, passed checks, and blockers with remediation owners. Missing or unavailable checks are BLOCKED, never an inferred pass. A blocked draft may be saved within authorized scope, but stays off the runnable path until the planner repairs it.

Comments

Markdown supported