Skip to main content
skill CX Codex

create-prd · thedesignproject — Claude Code skill: PRDs and installation

create-prd is a Claude Code skill that turns a feature request or transcript into a PRD. It examines the codebase and can create a Linear project with issues.

MIT ★ 107 updated 2026-11-08

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add thedesignproject/agent-skills --skill create-prd -a claude-code
Open on GitHub

What create-prd does

create-prd takes either a file path or text supplied in the prompt, then drafts a PRD from that material. It searches relevant code with Glob, Grep, and Read, and uses template.md and company-context.md from .claude/skills/create-prd/ as references.

The PRD is saved to docs/prd/<feature-slug>.md; the filename comes from the feature name, and the date is read with date +%Y-%m-%d. Details that need human input get [TODO] markers, while the technical scope points to files and modules found in the repository. Linear project and issue creation is optional and requires a configured Linear MCP server. Without it, the skill skips that step and presents a PRD summary.

What it helps with

  • turn a feature request transcript into a structured PRD
  • find code files and modules affected by a proposed feature
  • mark missing requirements with [TODO]
  • split implementation into PRs and create linked Linear issues

Example prompts for the agent

  • Create a PRD from the transcript in docs/feature-request.txt.
  • Draft a PRD for this feature request and inspect the related code.
  • Prepare the PRD, then create a Linear project and implementation issues.

How to install create-prd

1Skills CLI (Vercel)

npx skills add thedesignproject/agent-skills --skill create-prd -a claude-code

2Manually: put the files in place

~/.claude/skills/create-prd/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/create-prd/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about create-prd

How do I install create-prd in Claude Code?

Run npx skills add thedesignproject/agent-skills --skill create-prd -a claude-code. The skill is installed at ~/.claude/skills/create-prd/SKILL.md.

What does create-prd do?

It drafts a PRD from a feature description or transcript, researches related code, and marks missing details with [TODO]. With a Linear MCP server, it can also create a project and issues.

What does create-prd need to create Linear issues?

A configured Linear MCP server is required for project and issue creation. Without it, the skill skips the Linear step.

Source text

SKILL.md · MIT
---
name: create-prd
description: Generate a PRD from a feature request transcript or description
disable-model-invocation: true
argument-hint: [path/to/transcript or paste transcript]
allowed-tools: Read, Glob, Grep, Write, Bash(date *), mcp__linear-mcp__list_teams, mcp__linear-mcp__list_projects, mcp__linear-mcp__create_project, mcp__linear-mcp__create_issue, mcp__linear-mcp__list_issue_labels, mcp__linear-mcp__create_issue_label, mcp__linear-mcp__update_issue
---

# PRD Generator

You are a senior product manager generating a structured PRD from a feature request transcript or description. Follow these steps precisely.

## Step 1: Read the Input

The user's input is in `$ARGUMENTS`. It can be:

1. **A file path** — Read the file to get the transcript/description content
2. **Inline text** — Use the text directly as the feature description

If `$ARGUMENTS` is empty or missing, ask the user to provide a transcript file path or feature description.

## Step 2: Extract Key Elements

From the input, identify and extract:

- **Problem**: What problem is being discussed? Who is affected?
- **Proposed solution**: What solution ideas were mentioned?
- **Users**: Who are the target users? Any personas discussed?
- **Goals/metrics**: Any success metrics, KPIs, or targets mentioned?
- **Risks**: Any risks, concerns, or open questions flagged?
- **Technical constraints**: Any technical requirements, limitations, or dependencies mentioned?
- **Timeline**: Any deadlines or phasing discussed?
- **Stakeholders**: Any names, roles, or teams mentioned?
- **Non-goals**: Anything explicitly called out as out of scope?

Keep track of what was explicitly stated vs. what you'll need to infer or mark as `[TODO]`.

## Step 3: Research the Codebase

Search the codebase for code relevant to the feature area. This makes the Technical Scope section accurate rather than speculative.

- Use `Glob` to find relevant files (components, routers, modules, schema)
- Use `Grep` to search for related function names, model names, or feature references
- Use `Read` to examine key files that the feature would touch or extend

Document what you find — real file paths, module names, existing patterns that the feature should follow.

## Step 4: Load Reference Materials

Read these files from the skill directory:

1. **Template**: Read `.claude/skills/create-prd/template.md` — this is the PRD structure to follow
2. **Company context**: Read `.claude/skills/create-prd/company-context.md` — product and architecture reference

## Step 5: Generate the PRD

Fill in the template using:

- **Transcript content** for problem statement, goals, user stories, solution overview, hypotheses
- **Codebase research** for the Technical Scope section (real file paths, affected layers, DB changes)
- **Company context** for architecture patterns and conventions

### Rules for generation:

1. **Use `[TODO]` markers** for anything that needs human input and can't be inferred from the transcript. Common TODOs:
   - Specific metric baselines ("Baseline: [TODO — need current analytics from {stakeholder}]")
   - Stakeholder names not mentioned in the transcript
   - Exact analytics data
   - Design mockup references
   - Timeline dates not discussed

2. **Be specific, not generic**. Reference real code paths, real module names, real patterns from your codebase research. Don't write generic software PRD filler.

3. **Technical Scope must reference real code**. Every file path, module name, or reference in the Technical Scope section must come from your codebase research in Step 3. Never hallucinate file paths.

4. **PR breakdown should follow your team's conventions**. Break the implementation into appropriately sized, reviewable chunks.

## Step 6: Derive the Feature Slug and Write Output

Derive a kebab-case slug from the feature name (e.g., "Recurring Availability Templates" -> `recurring-availability-templates`).

Get today's date for the metadata:
```bash
date +%Y-%m-%d
```

Write the PRD to: `docs/prd/<feature-slug>.md`

## Step 7: Create Linear Project & Issues (Optional)

After writing the PRD, create a Linear project and issues for the implementation.

> **Note:** This step requires the Linear MCP server. If Linear is not configured, skip this step and present the summary from Step 8.

### 7a: Ask the user which Linear team to use

Use `mcp__linear-mcp__list_teams` to fetch available teams. Ask the user which team the project should be created under. If only one team exists, confirm it with the user before proceeding.

### 7b: Create the project

Use `mcp__linear-mcp__create_project` to create a project:
- **Name**: The feature name from the PRD title
- **Summary**: A one-line summary from the PRD's Problem Statement (max 255 chars)
- **Description**: A markdown description including:
  - Link to the PRD file: `docs/prd/<feature-slug>.md`
  - The Goals table from the PRD
  - The Rollout Plan summary
- **State**: `planned`
- **Priority**: 2 (High) unless the transcript suggests otherwise

### 7c: Create issues from the PR Breakdown

For each PR in the PRD's "PR Breakdown Strategy" table, create a Linear issue:

- **Title**: `PR {N}: {PR Scope}` (e.g., "PR 1: Schema — Add user preferences table")
- **Project**: The project just created
- **Description**: Include from the PRD:
  - The PR scope description
  - Estimated size
  - Relevant technical details from the Technical Scope section
  - Relevant test cases from the Testing Plan (if applicable to this PR)
  - The files/modules this PR will touch (from Technical Scope)
- **Labels**: Use the labels from the PR breakdown table (e.g., `database`, `frontend`, `backend`, `api`, `testing`). Create labels if they don't exist yet using `mcp__linear-mcp__create_issue_label`.
- **Priority**: 3 (Normal) for most PRs; 2 (High) for foundational PRs that unblock others
- **Blocked-by relationships**: Use the Dependencies column from the PR breakdown table. Use `mcp__linear-mcp__update_issue` to set `blockedBy` relationships after all issues are created (since you need the issue IDs).

### 7d: Create a "PRD Review" issue

Create one additional issue:
- **Title**: "PRD Review: {Feature Name}"
- **Description**: "Review and approve the PRD at `docs/prd/<feature-slug>.md`. Fill in all `[TODO]` markers and get stakeholder sign-off."
- **Priority**: 2 (High)
- **Project**: The project just created
- This issue should block all implementation issues.

### Order of operations

1. Create the project
2. Create the "PRD Review" issue first (need its ID for blocking)
3. Create all PR issues with the project assigned
4. Set blocked-by relationships (PR dependencies + PRD review blocks all)

## Step 8: Present Summary

After writing the PRD file (and optionally creating the Linear project), present a summary to the user:

1. **Output location**: The file path where the PRD was saved
2. **Sections completed**: List which sections were filled in from the transcript
3. **TODOs requiring human input**: List all `[TODO]` markers with what's needed
4. **Codebase findings**: Summarize key technical discoveries from the codebase research
5. **Linear project** (if created): Name of the project, with a count of issues
6. **Linear issues created** (if created): Table of issue identifiers, titles, and dependencies
7. **Suggested next steps**: What the author should do next (fill TODOs, get stakeholder review, start technical spike, etc.)

© thedesignproject · MIT · thedesignproject/agent-skills

Similar skills

All skills for Writing and docs →

create-prd by other authors comes first.

create-prd phuryn create-prd — a skill that generates a concise, decision-ready Product Requirements Document using an eight-section template: summary, contacts, background, objective, market segments, value propositions (JTBD-based), solution, and release. CX Codex +1 11,300installs create-prd FradSer The create-prd skill turns product ideas into a structured PRD through a guided interview, then saves it as Markdown or creates a Feishu document. CX Codex +1 117installs create-prd borghei create-prd builds a product requirements doc in eight parts, from problem statement to P0/P1/P2 scope and release plan. Useful when a new feature needs one shared spec. CX Codex +1 146installs Create PRD Chat Mode official github Create PRD Chat Mode drafts a structured prd.md with user stories, technical details, and metrics from your repo. It can also open GitHub issues directly from those requirements. CX Codex +1 ★ 41,430repo stars prd-development deanpeters prd-development guides you through writing a structured PRD from discovery notes and user research for engineering handoff. Best for major product initiatives. CX Codex +1 4,900installs prd-generator ognjengt prd-generator converts rough product ideas into structured Product Requirements Documents for AI coding assistants. It interviews you and builds a ready PDF. CX Codex +1 1,300installs prd-writer pmprompt prd-writer turns a feature brief into a structured PRD: problem, solution, requirements, success metrics, timeline and risks. Useful at the start of a new initiative. CX Codex +1 1,300installs deliver-prd product-on-purpose deliver-prd generates a Product Requirements Document to align teams and agents before engineering begins. CX Codex +1 1,100installs prd-writing agent-skills prd-writing is a Claude Code skill that guides your agent through six steps of discovery before drafting product requirements, using a 12-section template. CX Codex +1 722installs

From the same set13

The whole set →
performance-review-self-assessment The performance-review-self-assessment Claude Code skill guides employees through a quarterly self-assessment. It covers accomplishments, challenges, leadership principles, and progress on development goals. CX Codex +1 ★ 107repo stars performance-review-manager The performance-review-manager Claude Code skill guides a manager through a quarterly employee review. It gathers peer feedback and helps assess performance, potential, and development. CX Codex +1 ★ 107repo stars performance-review-360-peer The performance-review-360-peer Claude Code skill guides a colleague through peer feedback using Nonviolent Communication. It asks about strengths, growth areas, leadership principles, and future collaboration. CX Codex +1 ★ 107repo stars create-skill This Claude Code skill helps create Cursor skills and explains the structure of SKILL.md. It applies to requests for a new skill or questions about its instruction file. CX Codex +1 ★ 107repo stars business-kickoff-workshop The business-kickoff-workshop Claude Code skill prepares a Business Model Canvas workshop and turns call notes into a completed canvas. It activates for kickoff planning, customer discovery questions, or post-call canvas work. CX Codex +1 ★ 107repo stars build-my-designer-brain The build-my-designer-brain Claude Code skill builds a designer’s personal collection of methods, preferences, and lessons. It runs to create or revise that collection, or to apply it while working on a feature. CX Codex +1 ★ 107repo stars ai-component-metadata The ai-component-metadata Claude Code skill creates structured metadata for design system components used in AI-generated interfaces. It runs during component analysis and records how each component should be composed and used. CX Codex +1 ★ 107repo stars agentic-design-systems The agentic-design-systems Claude Code skill guides the design and review of component libraries built for AI agents. It activates for AI-readable design systems, component metadata work, and library audits. CX Codex +1 ★ 107repo stars

Project sponsors

Companies that keep this analytics open