prd-pilot

Detect PRD conflicts with codebases using ripgrep and generate evidence reports.

3|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/Gopherlinzy/prd-pilot --skill prd-pilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-pilot
Source: https://github.com/Gopherlinzy/prd-pilot/tree/main
Command: npx skills add https://github.com/Gopherlinzy/prd-pilot --skill prd-pilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AI coding agents frequently implement PRD requirements that conflict with existing code or miss stale implementations, leading to rework and technical debt. This skill validates product requirement documents against actual codebases before coding begins, ensuring requirements are feasible and conflicts are caught early.

Core Features & Use Cases

  • Conflict Detection: Cross-analyzes PRD requirements against code using ripgrep, producing evidence-backed reports with file paths and line numbers.
  • Diff Mode: Audits only changed requirements when a PRD is updated incrementally, reducing audit time by up to 90% on typical changes.
  • Documentation Health Check: Detects stale or inaccurate project documentation before relying on it for implementation.
  • Use Case: Ideal for teams using spec-kit or Superpowers, where an audit report feeds directly into specification generation and implementation planning.

Quick Start

Use the prd-pilot skill to audit the provided PRD document against the current project codebase and generate a structured conflict report with code evidence.

Frequently Asked Questions about prd-pilot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate PRD requirements against an existing codebase?

PRD-code conflict detection works by cross-analyzing markdown PRD files against your actual codebase using ripgrep searches, producing structured audit reports that highlight discrepancies with specific file paths and line numbers as evidence.

What is the best way to audit only updated sections of a product requirement document?

Auditing updated sections of a product requirement document is best handled using a diff mode that audits only changed requirements incrementally, reducing audit time by up to 90% on typical changes compared to a full codebase scan.

How does PRD conflict detection prevent technical debt in AI coding workflows?

PRD conflict detection prevents technical debt in AI coding workflows by validating product requirement feasibility against actual code before implementation begins, catching stale implementations and conflicts early to avoid rework.

Can I use ripgrep to find stale project documentation before implementation?

Yes, you can use ripgrep to find stale project documentation by searching the codebase for outdated references, performing a documentation health check before relying on it for implementation.

Does PRD validation generate structured reports for specification generation tools?

Yes, PRD validation generates structured audit reports containing file paths and line numbers as evidence, which feed directly into specification generation and implementation planning for teams using spec-kit or Superpowers.

What are the limitations of automated PRD-code conflict detection?

Automated PRD-code conflict detection requires reading markdown PRD files and executing codebase searches, meaning it relies heavily on the accuracy of existing documentation and the completeness of ripgrep search patterns to identify valid conflicts.