One-click install
npx skills add https://github.com/ajbmachon/ajbm-skills --skill prd-ajbmachon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/ajbmachon/ajbm-skills/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/ajbmachon/ajbm-skills --skill prd-ajbmachon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents unclear requirements by turning a fuzzy feature request into a complete, implementable Product Requirements Document (PRD) that can be executed deterministically by Ralph.

Core Features & Use Cases

  • Clarifying Questions First: Collects 5–10 targeted requirements in batches (up to 5), explicitly including scope and quality gates.
  • Quality-Gated PRD Output: Produces a detailed PRD in a consistent JSON structure with stack, routes, data model, rules, and verifiable acceptance criteria.
  • Deterministic Story Planning: Generates sequential story IDs, open status, explicit dependencies, and required setup stories for new projects (including installs and env/config).

Quick Start

Use the prd skill to produce an implementable JSON PRD by prompting it to plan a new feature with required quality gates.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a product requirements document in JSON format from a feature request?

To generate a product requirements document in JSON, the skill asks 5–10 clarifying questions about scope, stack, routes, data model, rules, and quality gates, then outputs a structured JSON PRD with verifiable acceptance criteria and actionable user stories.

What are quality gates in a PRD and how are they defined?

Quality gates in a PRD are explicit acceptance criteria defined during the clarifying questions phase. They ensure user stories contain verifiable examples and negative cases, making feature requirements deterministic and testable before implementation begins.

How do I write user stories that are sized for a single iteration?

To write user stories sized for single-iteration completion, the skill applies deterministic story sizing by generating sequential IDs (US-001 style), assigning open status, mapping explicit dependencies, and including required setup stories for new project environments.

Can I use this PRD generator for planning new features in an existing software stack?

Yes, you can use this PRD generator for existing software stacks. The clarifying questions explicitly capture your current tech stack, routes, and data model, ensuring the generated JSON document captures missing implementation details accurately for your specific architecture.

What is the best way to create deterministic specs for feature planning?

The best way to create deterministic specs is by enforcing a strict JSON output structure with required top-level fields like dataModel, rules, and qualityGates, preventing unclear requirements by turning fuzzy feature requests into complete, implementable documents.

What happens if my feature request is missing implementation details for user stories?

If your feature request is missing implementation details, the skill prompts you with targeted clarifying questions in batches of up to 5, specifically addressing scope, stack, and rules to fill gaps and ensure stories are fully actionable.