dredozubov

PRD Generator — Git skill for Claude Code

Git community intermediate

by Denis Redozubov - A Claude Code plugin that generates comprehensive Product Requirements Documents (PRDs) from conversation context.

How to install PRD Generator

This entry records only its repository, not the path inside it, so there is no exact command to give. Open dredozubov/prd-generator and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What PRD Generator does

A Claude Code plugin that generates comprehensive Product Requirements Documents (PRDs) from conversation context.

Alternatives in Git

  • Maintainers — Jarrod Watts (https://github.com/jarrodwatts) If you are interested in becoming a maintainer, open an issue to 10.9k ★
  • Gen Commit Msg — Generate intelligent commit messages based on staged changes 5.7k ★
  • PR Artifact — Creates one polished, self-contained HTML artifact that explains a pull request or code change for reviewers 652 ★

README

PRD Generator

A Claude Code plugin that generates comprehensive Product Requirements Documents (PRDs) from conversation context.

Installation

Option 1: Clone and Enable

git clone https://github.com/dredozubov/prd-generator ~/.claude/plugins/prd-generator

Then enable in Claude Code settings or via `/plugins enable prd-generator`.

Option 2: Add to Project

Clone into your project directory and reference in your Claude Code settings.

Commands

`/create-prd [output_file]`

Generate a comprehensive Product Requirements Document based on the current conversation context.

**Usage:**

/create-prd              # Creates PRD.md (default)
/create-prd docs/PRD.md  # Creates PRD at specified path

**Generated PRD includes:**

  • Executive Summary
  • Mission & Core Principles
  • Target Users & Personas
  • MVP Scope (In/Out of scope)
  • User Stories with examples
  • Core Architecture & Patterns
  • Tools/Features specification
  • Technology Stack
  • Security & Configuration
  • API Specification (if applicable)
  • Success Criteria
  • Implementation Phases
  • Future Considerations
  • Risks & Mitigations

When to Use

  • Starting a new project or feature
  • Documenting requirements from a planning conversation
  • Creating formal specifications from informal discussions
  • Onboarding team members with structured documentation

Author

Denis Redozubov ([@dredozubov](https://github.com/dredozubov))

License

MIT