CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
A skill your agent uses when the user wants to create a Product Requirements Document (PRD) for a new app, feature, or project.
Install Bm Prd Creator
$ npx skills add buildermethods/bm-skills --skill bm-prd-creator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install buildermethods/bm-skills bm-prd-creator --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/buildermethods/bm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bm-prd-creator .claude/skills/bm-prd-creator && 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 "bm-prd-creator" agent skill from https://github.com/buildermethods/bm-skills/tree/main/skills/bm-prd-creator into .claude/skills/bm-prd-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bm-prd-creator", 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/buildermethods/bm-skills/tree/main/skills/bm-prd-creatorType 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 buildermethods/bm-skills --skill bm-prd-creator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install buildermethods/bm-skills bm-prd-creator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/buildermethods/bm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/bm-prd-creator .agents/skills/bm-prd-creator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bm-prd-creator" agent skill from https://github.com/buildermethods/bm-skills/tree/main/skills/bm-prd-creator into .agents/skills/bm-prd-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bm-prd-creator", 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 buildermethods/bm-skills --skill bm-prd-creator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install buildermethods/bm-skills bm-prd-creator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/buildermethods/bm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/bm-prd-creator .cursor/skills/bm-prd-creator && 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 "bm-prd-creator" agent skill from https://github.com/buildermethods/bm-skills/tree/main/skills/bm-prd-creator into .cursor/skills/bm-prd-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bm-prd-creator", 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/buildermethods/bm-skills.git --path skills/bm-prd-creator--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 buildermethods/bm-skills --skill bm-prd-creator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install buildermethods/bm-skills bm-prd-creator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/buildermethods/bm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/bm-prd-creator .gemini/skills/bm-prd-creator && 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 "bm-prd-creator" agent skill from https://github.com/buildermethods/bm-skills/tree/main/skills/bm-prd-creator into .gemini/skills/bm-prd-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bm-prd-creator", 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 buildermethods/bm-skills bm-prd-creatorInstalls 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 buildermethods/bm-skills --skill bm-prd-creator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/buildermethods/bm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/bm-prd-creator .github/skills/bm-prd-creator && 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 "bm-prd-creator" agent skill from https://github.com/buildermethods/bm-skills/tree/main/skills/bm-prd-creator into .github/skills/bm-prd-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bm-prd-creator", 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 buildermethods/bm-skills --skill bm-prd-creator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install buildermethods/bm-skills bm-prd-creator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/buildermethods/bm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/bm-prd-creator .opencode/skills/bm-prd-creator && 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 "bm-prd-creator" agent skill from https://github.com/buildermethods/bm-skills/tree/main/skills/bm-prd-creator into .opencode/skills/bm-prd-creator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bm-prd-creator", 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.
Facts
- Skill name
bm-prd-creator- GitHub stars
- 146
- Token cost
- ~1.5k tokens
- SKILL.md length
- 864 words
- Files
- 13
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the user wants to create a Product Requirements Document (PRD) for a new app, feature, or project.
- Works in 7 steps: Always propose a default with reasoning,… → Use the AskUserQuestion tool for… → One decision at a time, in sequence.… → …
- The user wants to create a Product Requirements Document (PRD) for a new app
- SKILL.md covers Audience assumption, Core interaction principles, Phases and Final note on user energy
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Bm Prd Creator is an agent skill from buildermethods/bm-skills. Use when the user wants to create a Product Requirements Document (PRD) for a new app, feature, or project. Guides the user through a structured interview and produces a complete PRD (as a visual single-file HTML page, a markdown file, or both) along with ready-to-build milestones.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files (for example `steps/brain-dump.md`, `steps/core-purpose.md` and `steps/data-model.md`).
It sits in Product & Project Management, covering PRD writing. The repository describes itself as: A collection of public open-source tools for builders, by Brian Casel @ Builder Methods (buildermethods.com). The licence is MIT.
When your agent uses it
- The user wants to create a Product Requirements Document (PRD) for a new app
- Tasks that involve PRD writing
Example prompts
- “/bm-prd-creator”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Always propose a default with reasoning, then ask to confirm or change. Never ask open-ended "what do you want?" questions when you can…
- Use the AskUserQuestion tool for decisions with discrete options. For free-form input (the initial brain dump, naming the app, describing…
- One decision at a time, in sequence. Don't ask three unrelated questions at once. Walk through phases in order. Lock each phase before…
- Adapt depth to the idea. The default interview is balanced (~10–15 decisions). For very simple ideas, compress; for complex ideas with…
- The PRD is a what document, not a how document. The PRD describes user functionality, user flows, UI/UX behavior, scope boundaries…
- Keep your prose tight. Short framings, no preamble. The user is making decisions, not reading essays.
- HTML is the default output. Early in the interview the user picks a format (HTML / Markdown / Both). HTML is recommended because it's…
What it can do on your machine
Read from SKILL.md and the folder at commit b6b6a72. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Bm Prd Creator loads about 1.5k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 864 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from buildermethods/bm-skills at commit b6b6a72, republished under its MIT licence (© buildermethods). 864 words, ~1,541 tokens.
Download SKILL.mdSave it as
.claude/skills/bm-prd-creator/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.- name
- bm-prd-creator
- description
- Use when the user wants to create a Product Requirements Document (PRD) for a new app, feature, or project. Guides the user through a structured interview and produces a complete PRD (as a visual single-file HTML page, a markdown file, or both) along with ready-to-build milestones.
- user_invocable
- true
PRD Creator
You are guiding a non-technical business builder through turning a raw idea into a structured PRD and a sequence of milestone prompts that they can use to drive a coding agent through implementation.
This skill follows a structured, multi-phase process. Each phase has its own instructions file in the steps/ folder. Read and follow each step file when executing that phase. Do not skip ahead — earlier phases produce the inputs that later phases depend on.
Audience assumption
The user understands product, user experience, and what they want their app to do. They do NOT have a developer's understanding of code, databases, integrations, APIs, background jobs, authentication, or deployment. Whenever a technical concept appears, briefly explain it in plain language before asking the user to make a decision about it. Examples of how to explain things:
- "A background job is just a way for the app to do slow work (like calling an AI) after the user has already moved on, so the user doesn't have to wait."
- "An API token is like a password the app gives out so other tools can talk to it on the user's behalf."
- "A data model is the list of things your app needs to remember — like 'bookmarks' and 'tags' — and how they relate to each other."
Core interaction principles
Always propose a default with reasoning, then ask to confirm or change. Never ask open-ended "what do you want?" questions when you can propose a sensible default and explain why. The user is much better at editing a proposal than generating one.
Use the AskUserQuestion tool for decisions with discrete options. For free-form input (the initial brain dump, naming the app, describing a feature), use a normal chat message. For choosing between defined options, always use AskUserQuestion — the user is much more likely to be on mobile, and tappable options beat typing.
One decision at a time, in sequence. Don't ask three unrelated questions at once. Walk through phases in order. Lock each phase before moving to the next.
Adapt depth to the idea. The default interview is balanced (~10–15 decisions). For very simple ideas, compress; for complex ideas with many features and integrations, expand. The user's initial brain dump tells you how to scope.
The PRD is a what document, not a how document. The PRD describes user functionality, user flows, UI/UX behavior, scope boundaries, integrations, and the data the app needs to remember. It does NOT prescribe technical implementation: no code samples, no specific libraries (beyond the stack itself), no method names, no internal logic, no algorithmic decisions, and no technical patterns like timeouts, retry strategies, parsing approaches, or error-handling structure. Those decisions belong to the agent in plan mode for each milestone. The PRD's tech-stack section names the stack (e.g., Rails, React) and the integrations section names the providers (e.g., OpenAI, Resend) — that's the depth limit. Anything more specific is implementation.
Keep your prose tight. Short framings, no preamble. The user is making decisions, not reading essays.
HTML is the default output. Early in the interview the user picks a format (HTML / Markdown / Both). HTML is recommended because it's visual, scannable, and easier for non-technical users to review. The format choice changes presentation only — the locked scope, voice, and "what vs. how" boundary are identical across formats.
Show full SKILL.md (309 more words)Show less
Phases
Execute the following phases in order. Each phase's full instructions are in its own file under steps/. Read the relevant step file at the start of each phase and follow it. Do not skip ahead — confirm each phase is locked before moving to the next.
Brain dump intake —
steps/brain-dump.mdCapture the user's raw description of the idea, or prompt for it if they haven't given one yet.Format choice —
steps/format-choice.mdLock the PRD output format: HTML (recommended, default), Markdown, or Both.Core purpose —
steps/core-purpose.mdSynthesize the brain dump into a 1–3 sentence "what we're building" statement and confirm it.Top-level features (in scope) —
steps/top-level-features.mdPropose 4–8 core features and lock the headline-level in-scope list.Top-level out-of-scope —
steps/out-of-scope.mdProactively propose likely v1 cuts and confirm what's explicitly out.Tech stack & starter template —
steps/tech-stack.mdDetect the existing stack from the codebase, confirm it, and lock what the starter already provides.External integrations & credentials —
steps/integrations.mdFor each feature that needs an external service, propose a provider and list the credentials the user must obtain.Data model —
steps/data-model.mdPropose entities, fields, and relationships in plain language and confirm.Per-feature scoping —
steps/per-feature-scoping.mdFor each in-scope feature, lock the user-facing in-scope and out-of-scope details one at a time.Milestone breakout —
steps/milestones.mdPropose a default milestone sequence plus alternatives, then lock the names and scopes.Write files —
steps/write-files.mdGenerate the PRD in the chosen format(s) and eachmilestones/N-{slug}/prompt.md. Referencessteps/prd-html-template.mdfor the HTML scaffold. Includes the markdown PRD and prompt file templates and final style notes.
Final note on user energy
This interview can run long. Keep momentum: short framings, fast cadence, defaults that move the conversation forward. If the user shows signs of decision fatigue, batch lower-stakes decisions and offer "use my recommended defaults for the rest of this phase" as an option.
© buildermethods, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 12 other files in skills/bm-prd-creator of buildermethods/bm-skills.
- SKILL.md
- steps/brain-dump.md
- steps/core-purpose.md
- steps/data-model.md
- steps/format-choice.md
- steps/integrations.md
- steps/milestones.md
- steps/out-of-scope.md
- steps/per-feature-scoping.md
- steps/prd-html-template.md
- steps/tech-stack.md
- steps/top-level-features.md
- steps/write-files.md
Open the folder on GitHubat commit b6b6a72
Compare with similar skills
Bm Prd Creator 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 |
|---|---|---|---|---|---|---|
| Bm Prd Creator this skillbuildermethods/bm-skills | 146 | — | ~1.5k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Adversarial Speczscole/adversarial-spec | 556 | 1 repos | ~8.3k | Automated safety check: Notes | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Adversarial Spec
zscole/adversarial-spec
Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
More from buildermethods/bm-skills
Bm Favicon Creator
buildermethods/bm-skills
Generate a complete favicon set (SVG, PNGs, multi-resolution .ico, Apple touch icon) from a Lucide icon (default) or another source SVG, then wire the favicon meta tags into the codebase.
Bm Design System
buildermethods/bm-skills
Guides you through creating and implementing a design system for your application.
Bm Skill Builder
buildermethods/bm-skills
Build a new agent skill (or restructure an existing one) following Builder Methods conventions.
Related
Categories
Questions about Bm Prd Creator
What does Bm Prd Creator do?
A skill your agent uses when the user wants to create a Product Requirements Document (PRD) for a new app, feature, or project. Bm Prd Creator is an agent skill from buildermethods/bm-skills. Use when the user wants to create a Product Requirements Document (PRD) for a new app, feature, or project.
When should I use Bm Prd Creator?
Bm Prd Creator fits situations like: the user wants to create a Product Requirements Document (PRD) for a new app; tasks that involve PRD writing.
How do I install Bm Prd Creator in Claude Code?
Run `npx skills add buildermethods/bm-skills --skill bm-prd-creator -a claude-code`. Or copy the skill folder (skills/bm-prd-creator in buildermethods/bm-skills) into .claude/skills/bm-prd-creator in your project. Claude Code loads it when a task matches its description.
How do I install Bm Prd Creator in Codex?
Run `npx skills add buildermethods/bm-skills --skill bm-prd-creator -a codex`. Or copy the skill folder (skills/bm-prd-creator in buildermethods/bm-skills) into .agents/skills/bm-prd-creator in your project. Codex loads it when a task matches its description.
Can I use Bm Prd Creator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add buildermethods/bm-skills --skill bm-prd-creator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bm-prd-creator, .gemini/skills/bm-prd-creator, .github/skills/bm-prd-creator and .opencode/skills/bm-prd-creator in your project.
What does Bm Prd Creator need to run?
SKILL.md names no scripts, command-line tools or credentials: Bm Prd Creator is instructions for the agent only.
Does Bm Prd Creator access the network?
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.
Is Bm Prd Creator safe to install?
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.
What licence does Bm Prd Creator use?
Bm Prd Creator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Bm Prd Creator use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Bm Prd Creator?
Skills that share tags, products or a category with Bm Prd Creator: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Adversarial Spec (zscole/adversarial-spec, 556 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bm Prd Creator?
buildermethods (a GitHub organization) maintains it in buildermethods/bm-skills, which has 146 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.
Source: buildermethods/bm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.