Feature Forge
Jeffallan/claude-skills
Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.
Builds a structured PRD that ties problem, users, solution and success criteria together, turning discovery notes into a document engineers can act on.
$ npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills prd-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/prd-development .claude/skills/prd-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "prd-development" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development into .claude/skills/prd-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills prd-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/prd-development .agents/skills/prd-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prd-development" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development into .agents/skills/prd-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills prd-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/prd-development .cursor/skills/prd-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prd-development" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development into .cursor/skills/prd-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/deanpeters/Product-Manager-Skills.git --path skills/prd-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills prd-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/prd-development .gemini/skills/prd-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prd-development" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development into .gemini/skills/prd-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install deanpeters/Product-Manager-Skills prd-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/prd-development .github/skills/prd-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prd-development" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development into .github/skills/prd-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deanpeters/Product-Manager-Skills prd-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/prd-development .opencode/skills/prd-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prd-development" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/prd-development into .opencode/skills/prd-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
prd-developmentBuilds a structured PRD that ties problem, users, solution and success criteria together, turning discovery notes into a document engineers can act on.
The skill orchestrates problem framing, user research synthesis, solution definition and success criteria into one document, so scattered notes and Slack threads become a PRD that aligns stakeholders and gives engineering context. The standard structure answers what problem is solved, for whom, why now, what is being built, how success is measured, what the requirements are, including user stories and acceptance criteria, and what is out of scope.
It treats the PRD as a living document rather than a waterfall spec. You name the feature or initiative and paste whatever exists, such as discovery notes, problem statements, research, metrics and constraints; the workflow slots that material into the right phases and skips what is already answered, and with nothing provided it starts at problem definition. A template and two examples, one of them industrial, are included.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1b5a524. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
PRD Development loads about 6.2k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 1,889 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,889 words (~6,194 tokens).
“Guide product managers through structured PRD (Product Requirements Document) creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document. Use this to move from scattered notes and Slack threads to a clear, comprehensive…”
SKILL.md and 3 other files in skills/prd-development of deanpeters/Product-Manager-Skills.
Open the folder on GitHubat commit 1b5a524
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in deanpeters/Product-Manager-Skills, which our catalogue first saw on October 7, 2026.
PRD Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PRD Development this skilldeanpeters/Product-Manager-Skills | 7.2k | 3 repos | ~6.2k | Automated safety check: Pass | Custom licence | |
| Feature ForgeJeffallan/claude-skills | 12k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ambiguity Detectormajiayu000/claude-skill-registry | 666 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Jeffallan/claude-skills
Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.
majiayu000/claude-skill-registry
Detects and analyzes ambiguous language in software requirements and user stories.
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
ywwynm/EverythingDone
Turn the current conversation context into a PRD and publish it to the project issue tracker.
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
deanpeters/Product-Manager-Skills
Calculates total, serviceable available and serviceable obtainable market size for a product idea with explicit assumptions, methods and caveats.
deanpeters/Product-Manager-Skills
Builds a company research brief covering executive quotes, product strategy, transformation efforts and org context, tailored to interview prep, competitor or partnership work.
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
deanpeters/Product-Manager-Skills
Scans political, economic, social, technological, environmental, and legal forces that could threaten or favor a product strategy.
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Categories
Builds a structured PRD that ties problem, users, solution and success criteria together, turning discovery notes into a document engineers can act on. The skill orchestrates problem framing, user research synthesis, solution definition and success criteria into one document, so scattered notes and Slack threads become a PRD that aligns stakeholders and gives engineering context. The standard structure answers what problem is solved, for whom, why now, what is being built, how success is measured, what the requirements are, including user stories and acceptance criteria, and what is out of scope.
PRD Development fits situations like: writing a PRD for a major initiative from scattered discovery notes; documenting scope, out-of-scope items and acceptance criteria for engineering; aligning stakeholders around a single source of truth for a feature.
Run `npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a claude-code`. Or copy the skill folder (skills/prd-development in deanpeters/Product-Manager-Skills) into .claude/skills/prd-development in your project. Claude Code loads it when a task matches its description.
Run `npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a codex`. Or copy the skill folder (skills/prd-development in deanpeters/Product-Manager-Skills) into .agents/skills/prd-development in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deanpeters/Product-Manager-Skills --skill prd-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-development, .gemini/skills/prd-development, .github/skills/prd-development and .opencode/skills/prd-development in your project.
SKILL.md names no scripts, command-line tools or credentials: PRD Development is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
PRD Development has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 6.2k tokens (SKILL.md is roughly 25k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with PRD Development: Feature Forge (Jeffallan/claude-skills, 12k stars), Ambiguity Detector (majiayu000/claude-skill-registry, 666 stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,181 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 1, 2026.
Source: deanpeters/Product-Manager-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.