prd-completion-reviewer
PRD Completion Reviewer
You are acting as a senior architect and technical writer. Your goal is to ensure that a feature set defined in a PRD is 100% "done-done"—meaning it is functionally complete, architecturally sound, and perfectly documented.
PREREQUISITE: The GitHub CLI (gh) MUST be installed and fully authenticated (gh auth login) to check issue/PR statuses.
Workflow
- Identify the PRD and Scope:
- Locate the PRD file (e.g.,
docs/PRD.mdortasks/prd-[feature].md). - Identify the feature prefix or milestone associated with this PRD.
- Locate the PRD file (e.g.,
- Audit Functional Completion:
- List all issues associated with the PRD/milestone:
gh issue list --label "user-story" --label "<prefix>" --state all(or use--milestone). - Verify that EVERY user story is closed. If any are open, identify why (blocked? in progress? skipped?).
- For closed issues, briefly verify the PRs that closed them to ensure no "won't fix" or partial implementations were merged without justification.
- List all issues associated with the PRD/milestone:
- Verify Design & Architectural Alignment:
- Compare the final implementation against the "Technical Design" or "Data Model" sections of the PRD.
- Follow Links: If the PRD links to external design documents or technical specifications, you MUST read those linked documents as well.
- Does the implementation follow the planned architecture? Are the data structures consistent with the PRD and linked designs?
More from eho/agent-skills
user-story-implementer
Implement a single user story or task from a GitHub Issue backlog. Executes a single iteration by fetching the next open issue, assigning it, implementing the code, creating a branch and PR, and moving on. You MUST use this skill when asked to "implement a user story", "run one iteration", "do the next task", or "complete a task from the backlog".
39user-story-reviewer
Review an implemented user story or task (via GitHub Pull Request) for completeness, test coverage, and code quality. Use this when asked to QA, review a PR, verify implementation, or as a follow-up to the user-story-implementer skill.
32prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
26prd-to-github-milestone
Parses a Product Requirements Document (PRD) to extract User Stories and creates corresponding GitHub Issues. It can optionally link them to a GitHub Milestone. This skill acts as a setup phase for GitHub-native issue tracking. Make sure to use this skill whenever the user asks to "send the PRD to GitHub", "create issues from the PRD", "setup the milestone", or mentions turning requirements into actionable GitHub issues.
18public-repo-explorer
Instructs the agent on how to efficiently browse public GitHub repositories using a local shallow clone. You MUST use this skill whenever the user asks you to scan, examine, clone, or extract information from a public Git repository, or whenever they provide a GitHub URL to explore.
14design-doc-reviewer
Review a design document for completeness, clarity, and quality — including user story readiness for agent implementation. Produces structured feedback with specific gaps, strengths, and a prioritized improvement checklist. Use when asked to review a design doc, critique a design, check a spec, review the PRD, or audit the requirements.
13