Agent skill
prd-check
Run PRD validation to check story quality, test coverage, and structure.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/prd-check
SKILL.md
PRD Check
Run PRD validation on demand to check story quality, test coverage, and structure before starting the autonomous loop.
Instructions
When the user runs /prd-check, validate their PRD file.
Step 1: Check PRD Exists
ls -la .ralph/prd.json 2>/dev/null || echo "NOT_FOUND"
If no PRD exists, tell the user:
No PRD found at
.ralph/prd.json. Generate one first with/ideaor/prd.
STOP if no PRD found.
Step 2: Run Validation (dry-run)
Run validation without auto-fix so you can present results and let the user decide:
npx ralph prd-check --dry-run 2>&1
Step 3: Present Results
Show the validation output to the user. If there are issues, summarize them clearly.
If issues were found, ask:
"Would you like me to fix these issues in the PRD?"
STOP and wait for user response.
If the user says yes, read .ralph/prd.json, fix the issues following PRD best practices (executable testSteps with curl/pytest/playwright, apiContract for backends, testUrl for frontends, security criteria for auth stories, pagination for list endpoints), and write the fixed file back.
Notes
- This is the same validation that runs automatically at
ralph runstartup --dry-runskips auto-fix so you have control over what changes- Custom checks in
.ralph/checks/prd/are also evaluated - Run this before
ralph runto catch and fix issues interactively
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?