skills.rest
EmeaAppGbb
EmeaAppGbbOFFICIAL
Explore all skills by this author →
GitHub

spec-refinement

Review PRDs and FRDs for issues and convert PRDs into FRDs.

Updated Mar 30, 2026
Search Tags:#software development#product management#specification refinement#PRD review#FRD creation
One-click install
npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill spec-refinement-emeaappgbb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-refinement
Source: https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield/tree/main/.github/skills/spec-refinement
Command: npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill spec-refinement-emeaappgbb

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill reviews product requirements documents (PRDs) and feature requirement documents (FRDs) to identify gaps, ambiguities, and technical feasibility, ensuring specifications are ready for implementation.

Core Features & Use Cases

  • PRD and FRD Review: Systematically checks PRDs and FRDs through product and technical lenses.
  • Issue Identification: Highlights critical, major, and minor issues with specific recommendations.
  • Breakdown Strategy: Converts approved PRDs into FRDs, ensuring features are scoped and dependencies are identified.
  • FRD Review Standards: Ensures FRDs are specific, testable, and meet acceptance criteria.

Quick Start

Use the spec-refinement skill to review the PRD for your new feature and convert it into an FRD.

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 for technical feasibility and gaps before implementation?▼

Converting a PRD into an FRD requires applying a breakdown strategy to scope features and identify dependencies. The resulting FRD ensures features are specific, testable, and meet acceptance criteria for development.

What makes a feature requirement document ready for implementation?▼

A feature requirement document is ready when it passes FRD review standards, ensuring features are specific, testable, and meet acceptance criteria. This structured feedback highlights gaps, ambiguities, and technical feasibility.

How do I convert an approved PRD into an FRD?▼

Converting a PRD into an FRD requires applying a breakdown strategy to scope features and identify dependencies. The resulting FRD ensures features are specific, testable, and meet acceptance criteria for development.

What is the best way to identify ambiguities in product requirements documents?▼

The best way to identify ambiguities in product requirements documents is through systematic PRD review using product and technical lenses. This provides structured feedback highlighting critical, major, and minor issues with specific recommendations.

Related Skills

Explore More Software Engineering Skills→
fhltafhlta

guildops-prd-discovery

Transforms GuildOps feature concepts into structured, Spec Kit-ready PRDs with ambiguity checklist and template.

Community
Intermediate
garethrhughesgarethrhughes
5

jira-feature

Fetch Jira tickets and convert them into feature briefs.

Community
Advanced
Exia-thdExia-thd

project-manager

Plan and execute agile sprints, tasks, and risks for software teams.

Community
Advanced
camelranchentertainmentcamelranchentertainment
1

feature-forge

Generates complete feature specs, including workflows, personas, and step-by-step task lists.

Community
Advanced