Requirements prd scope review
Skill jukrap/ai-agent-playbook/skills/project/requirements-prd-scope-review
Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.
npx -y skills add jukrap/ai-agent-playbook --skill requirements-prd-scope-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when turning vague requests into PRDs, scope boundaries, acceptance criteria, or open questions.
SKILL.md
1.1 KB, as published. Nobody here has run it
Requirements PRD Scope Review
Turn broad intent into reviewable scope without inventing contracts or implementation facts.
Workflow
- Identify the artifact type: PRD, lightweight spec, scope brief, acceptance criteria, or open-question list.
- Separate known goals, users, workflows, constraints, non-goals, dependencies, assumptions, and unknowns.
- Check whether product language, technical plan, worklog history, and generated evidence are being mixed.
- Define acceptance criteria from externally observable behavior, not from guessed implementation details.
- Mark backend/API/data fields as open questions unless source evidence already proves them.
- Capture owners, decision status, verification expectations, and what should not become durable memory yet.
Reference
Read references/prd-scope-checks.md when shaping a PRD, spec, or scope brief.
Read references/acceptance-criteria-and-open-questions.md when turning vague requests into testable criteria and unresolved questions.