Prd Create

PRD Creation Slash Command

Instructions

You are helping create a Product Requirements Document (PRD) for a new feature. In this repository the PRD is its GitHub issue: the issue body is the project management document — milestone tracking and implementation plan — and its comments are the record of progress and decisions. Nothing is written under prds/ and nothing is committed (issue #1591).

The layout of an issue PRD — what goes in the body, what goes in comments, how to edit the body without losing someone else's edit — is in ../prd-start/issue-prd.md; read it before writing the body. Older PRDs that already have a prds/<n>-*.md file keep it; this skill never creates one.

Process

Step 1: Understand the Feature Concept

Ask the user to describe the feature idea to understand the core concept and scope.

Step 2: Create the GitHub Issue FIRST, or Use the One Named

Create the GitHub issue immediately to get the issue ID, with the short initial body below. If the user names an existing issue instead — typically a PRD-labelled issue whose body is only a stub ("Detailed PRD: not written yet") — use that issue and keep its number; its current body is the starting point for the discussion, not something to discard.

IMPORTANT: Add the "PRD" label to the issue for discoverability.

If the existing issue was opened by someone without write access, do not write the PRD into it: its author can rewrite the body at any time, so prd-source.sh never treats it as a PRD. Create a new issue, write the PRD there, and link the original from it.

Step 3: Write the PRD into the Issue Body

Work through the template sections below with the user, then write the result as the issue body, following ../prd-start/issue-prd.md ("The body" and "Editing the body"): write it to .dot-agent-deck/prd-[issue-id]-body.md with your file-writing tool and gh issue edit [issue-id] --body-file that file. Write as you go — after each agreed section rather than once at the end — so a session that ends early has not lost the discussion.

Step 4: Create PRD as a Project Management Document

Work through the PRD template focusing on project management, milestone tracking, and implementation planning. Documentation updates should be included as part of the implementation milestones.

Key Principle: Focus on 5-10 major milestones rather than exhaustive task lists. Each milestone should represent meaningful progress that can be clearly validated.

Consider Including (when applicable to the project/feature):

• Tests - If the project has tests, include a milestone for test coverage of new functionality
• Documentation - If the feature is user-facing, include a milestone for docs following existing project patterns

Good Milestones Examples:

• Core functionality implemented and working
• Tests passing for new functionality (if project has test suite)
• Documentation complete following existing patterns (if user-facing feature)
• Integration with existing systems working
• Feature ready for user testing

Avoid Micro-Tasks:

• ❌ Update README.md file
• ❌ Write test for function X
• ❌ Fix typo in documentation
• ❌ Individual file modifications

Milestone Characteristics:

• Meaningful: Represents significant progress toward completion
• Testable: Clear success criteria that can be validated
• User-focused: Relates to user value or feature capability
• Manageable: Can be completed in reasonable timeframe

Step 5: Confirm It Reads as a PRD

bash .claude/skills/prd-start/prd-source.sh [issue-id]

It must print SOURCE=issue. SOURCE=none names what is missing in REASON= — usually the ## Milestones section has no checkbox yet. This is the same check /prd-queue applies before it will dispatch the PRD, so a body that fails it is a PRD nobody can start.

GitHub Issue Template

Initial Issue Creation — title PRD: [Feature Name]; the body is replaced by the full PRD in Step 3:

**Priority**: [High/Medium/Low] · **Created**: [YYYY-MM-DD]

## Problem

[1-2 sentence problem description]

## Solution

[1-2 sentence solution overview]

Don't forget to add the "PRD" label to the issue after creation.

The full PRD body is the template in ../prd-start/issue-prd.md ("The body"): Problem, Solution, Scope, Success Criteria, Milestones as checkboxes, Risks and Dependencies, and Decisions. Create the issue with --body-file too, for the reason that page gives.

Discussion Guidelines