spec-refinement

Review and refine PRDs and FRDs using product and technical checklists.

Updated May 6, 2026
One-click install
npx skills add https://github.com/crgarcia12/compy --skill spec-refinement-crgarcia12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-refinement
Source: https://github.com/crgarcia12/compy/tree/main/.github/skills/spec-refinement
Command: npx skills add https://github.com/crgarcia12/compy --skill spec-refinement-crgarcia12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps in the comprehensive review and refinement of Product Requirements Documents (PRDs) and Feature Requirements Documents (FRDs), ensuring they are complete, unambiguous, and technically feasible before implementation.

Core Features & Use Cases

  • Multi-Lens Review: Conducts a product and technical lens review across up to 5 passes to ensure quality.
  • Structured Feedback: Provides feedback in a structured format with severity, impact, suggestion, and alternative for easy resolution.
  • PRD Diagram Standards: Enforces PRD diagramming standards for clarity and consistency.
  • PRD to FRD Breakdown: Breaks down approved PRDs into individual FRDs, ensuring each feature is implementable and testable.
  • FRD Review Standards: Sets high standards for FRDs, requiring clear, testable requirements and acceptance criteria.

Quick Start

Run the spec-refinement skill on your PRD to start the review process.

Frequently Asked Questions about spec-refinement

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

FAQPage Schema
How do I review a PRD to ensure requirements are complete and technically feasible?

PRD review applies product and technical lens checklists across multiple passes to ensure requirements are complete, unambiguous, and technically feasible. This structured process provides feedback with severity, impact, and alternative suggestions for easy resolution.

What is the best way to break down a PRD into individual FRDs?

Breaking down a PRD into FRDs translates approved product requirements into individual feature requirements. This ensures each feature is implementable, testable, and meets high standards for clear acceptance criteria.

How does structured feedback work when refining a Feature Requirements Document?

Structured feedback for FRD refinement categorizes issues by severity, impact, suggestion, and alternative. This format enables developers to quickly understand ambiguities and resolve technical feasibility gaps before implementation begins.

Do I need diagram standards for my PRD review process?

PRD diagram standards are required during the review process to enforce clarity and consistency. Applying these diagramming standards ensures visual requirements are unambiguous and easily understood by both product and technical teams.

When do I need to use both product and technical lenses for specification refinement?

Specification refinement requires both product and technical lenses when transitioning PRDs to FRDs. Using dual-lens checklists across up to 5 passes guarantees the final requirements are unambiguous, completely scoped, and technically feasible.