Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Defines product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical planning.
Install Planning Products
$ npx skills add rileyhilliard/claude-essentials --skill planning-products -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rileyhilliard/claude-essentials planning-products --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/rileyhilliard/claude-essentials.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ce/skills/planning-products .claude/skills/planning-products && 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 "planning-products" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/planning-products into .claude/skills/planning-products/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-products", 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/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/planning-productsType 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 rileyhilliard/claude-essentials --skill planning-products -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rileyhilliard/claude-essentials planning-products --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ce/skills/planning-products .agents/skills/planning-products && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planning-products" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/planning-products into .agents/skills/planning-products/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-products", 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 rileyhilliard/claude-essentials --skill planning-products -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rileyhilliard/claude-essentials planning-products --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ce/skills/planning-products .cursor/skills/planning-products && 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 "planning-products" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/planning-products into .cursor/skills/planning-products/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-products", 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/rileyhilliard/claude-essentials.git --path plugins/ce/skills/planning-products--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 rileyhilliard/claude-essentials --skill planning-products -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rileyhilliard/claude-essentials planning-products --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ce/skills/planning-products .gemini/skills/planning-products && 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 "planning-products" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/planning-products into .gemini/skills/planning-products/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-products", 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 rileyhilliard/claude-essentials planning-productsInstalls 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 rileyhilliard/claude-essentials --skill planning-products -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ce/skills/planning-products .github/skills/planning-products && 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 "planning-products" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/planning-products into .github/skills/planning-products/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-products", 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 rileyhilliard/claude-essentials --skill planning-products -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rileyhilliard/claude-essentials planning-products --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ce/skills/planning-products .opencode/skills/planning-products && 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 "planning-products" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/planning-products into .opencode/skills/planning-products/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-products", 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
planning-products- GitHub stars
- 130
- Token cost
- ~1.4k tokens
- SKILL.md length
- 615 words
- Files
- 6 (incl. references)
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Defines product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical planning.
- Scoping features
- SKILL.md covers Planning Phase, The Planning Sequence, Product Type Adjustments and Universal Principles, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Writing product specs
What it does
Planning Products is an agent skill from rileyhilliard/claude-essentials. Defines product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical planning. Use when scoping features, writing product specs, defining user problems, or choosing what to build.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/definition.md`, `references/discovery.md` and `references/experience.md`).
It sits in Product & Project Management, covering PRD writing and User stories. The licence is MIT.
When your agent uses it
- Scoping features
- Writing product specs
- Defining user problems
- Choosing what to build
Example prompts
- “Use the planning-products skill to define product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical…”
- “/planning-products”
What it can do on your machine
Read from SKILL.md and the folder at commit 3a67a01. 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
Planning Products loads about 1.4k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 615 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 rileyhilliard/claude-essentials at commit 3a67a01, republished under its MIT licence (© rileyhilliard). 615 words, ~1,354 tokens.
Download SKILL.mdSave it as
.claude/skills/planning-products/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- planning-products
- description
- Defines product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical planning. Use when scoping features, writing product specs, defining user problems, or choosing what to build.
Planning Products
Core principle: Define the problem worth solving and the experience worth building before deciding how to build it. Research what exists, understand who needs it, scope what matters.
Planning Phase
Load the relevant reference based on where you are in the planning process:
| Phase | Load | File |
|---|---|---|
| Researching market, competitors, existing patterns | Discovery | references/discovery.md |
| Framing the problem, users, and jobs to be done | Definition | references/definition.md |
| Defining how the feature should feel (UX or DX) | Experience | references/experience.md |
| Drawing scope boundaries, MVP, phasing | Scoping | references/scoping.md |
| Writing the actual product spec document | Template | references/feature-spec-template.md |
Start with Discovery when beginning from scratch. Start with Definition when the problem is already understood. Load Experience alongside either when the feature has significant interaction design. Load Scoping when you need to cut.
The Planning Sequence
Discovery → Definition → Experience → Scoping → [Hand off]
↓ ↓ ↓ ↓
Research Problem How it What's in
& patterns & users feels & what's outNot always linear. Discovery can reframe the problem. Experience constraints can force scope changes. Scoping can send you back to discovery. But this is the default order.
Product Type Adjustments
Different products need different emphasis. Adjust the planning weight:
| Product type | Heavy on | Light on | Key question |
|---|---|---|---|
| Consumer (B2C) | Experience, discovery | Formal definition | "Would I use this?" |
| B2B / Enterprise | Definition, scoping | Visual polish | "Does this solve a workflow?" |
| Developer tools | DX experience, API ergonomics | Marketing polish | "Is this the obvious API?" |
| Internal tools | Scoping, definition | Discovery | "Does this save time?" |
| Platform / API | Definition, experience (DX) | Consumer UX | "Is this composable?" |
Universal Principles
Start with the customer's problem, not your solution
You are not designing features. You are solving problems for specific people. If you can't name the person and their frustration, you're not ready to plan.
Research before inventing
Before designing something new, find out what already exists. Users have expectations shaped by other products. Meeting those expectations is usually better than surprising people with novelty. Novelty costs learning; familiarity is free.
Hypothesis-driven, not conviction-driven
Frame decisions as hypotheses that could be wrong. "We believe [user] will [behavior] because [evidence]." If you can't state the evidence, it's a guess. Guesses are fine as long as you know they're guesses.
Type 1 vs Type 2 decisions
| Decision type | Characteristics | Planning rigor |
|---|---|---|
| Type 1 (one-way door) | Hard to reverse, high switching cost | Full discovery + definition |
| Type 2 (two-way door) | Easy to change, low cost to undo | Lightweight spec, ship and learn |
Most product decisions are Type 2. Don't over-plan reversible choices.
Show full SKILL.md (227 more words)Show less
Define success before building
Every feature needs measurable success criteria before work begins. Not vanity metrics. Outcomes tied to the user problem you're solving.
| Bad metric | Good metric |
|---|---|
| "Page views" | "% of users who complete the core task" |
| "API calls" | "Time to first successful integration" |
| "DAU" | "Users who return within 7 days" |
Anti-Patterns
| Pattern | Problem |
|---|---|
| Solution-first planning ("Let's build X") | Skips problem validation, builds the wrong thing |
| Feature lists without user stories | No context for why, impossible to prioritize |
| Copying competitors without understanding why | Imports their problems along with their solutions |
| "Users" as a monolith (no persona distinction) | Different users need different things |
| Scope that only grows, never shrinks | Ship date slides, value dilutes |
| Planning without research | Invents patterns users already know differently |
| Perfecting the spec before testing assumptions | Spec fiction, not product planning |
| DX as afterthought ("devs will figure it out") | Developers are users too, bad DX kills adoption |
Handoff Points
This skill's output feeds into other skills:
- Technical implementation: Use Claude's built-in plan mode to produce task breakdowns from the product spec
- UI/UX craft:
Skill(design)takes the experience requirements and produces the visual implementation - Architecture decisions:
Skill(architecting-systems)takes the technical constraints from the spec and produces system design - Strategy context:
Skill(strategy-writer)operates upstream, informing the "why this, why now" that feeds into discovery
Writing tone for specs and product docs: Use Skill(writer) with The PM persona.
© rileyhilliard, 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 5 other files (references) in plugins/ce/skills/planning-products of rileyhilliard/claude-essentials.
- SKILL.md
- references/definition.md
- references/discovery.md
- references/experience.md
- references/feature-spec-template.md
- references/scoping.md
Open the folder on GitHubat commit 3a67a01
Compare with similar skills
Planning Products 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 |
|---|---|---|---|---|---|---|
| Planning Products this skillrileyhilliard/claude-essentials | 130 | — | ~1.4k | 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 | |
| To Prdywwynm/EverythingDone | 144 | 11 repos | ~777 | Automated safety check: Pass | GPL-3.0 | |
| Use Case Writerphucnt-bazone-vietnam/use-case-writer | 143 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
To Prd
ywwynm/EverythingDone
Turn the current conversation context into a PRD and publish it to the project issue tracker.
Use Case Writer
phucnt-bazone-vietnam/use-case-writer
Generate Use Case specifications in English Markdown following the IT BA standard 13-field template (Karl Wiegers / IIBA).
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
More from rileyhilliard/claude-essentials
All 17 skills in this repoHandling Errors
rileyhilliard/claude-essentials
Prevents silent failures and context loss in error handling.
Writing Tests
rileyhilliard/claude-essentials
Writes behavior-focused tests using Testing Trophy model with real dependencies.
Optimizing Performance
rileyhilliard/claude-essentials
Measure-first performance optimization that balances gains against complexity.
Architecting Systems
rileyhilliard/claude-essentials
Guides clean, scalable system architecture during the build phase.
Design
rileyhilliard/claude-essentials
Enforces precise, minimal design for dashboards and admin interfaces.
Fixing Flaky Tests
rileyhilliard/claude-essentials
Diagnose and fix tests that pass in isolation but fail when run concurrently.
Related
Categories
Questions about Planning Products
What does Planning Products do?
Defines product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical planning. Planning Products is an agent skill from rileyhilliard/claude-essentials. Defines product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical planning.
When should I use Planning Products?
Planning Products fits situations like: scoping features; writing product specs; defining user problems; choosing what to build.
How do I install Planning Products in Claude Code?
Run `npx skills add rileyhilliard/claude-essentials --skill planning-products -a claude-code`. Or copy the skill folder (plugins/ce/skills/planning-products in rileyhilliard/claude-essentials) into .claude/skills/planning-products in your project. Claude Code loads it when a task matches its description.
How do I install Planning Products in Codex?
Run `npx skills add rileyhilliard/claude-essentials --skill planning-products -a codex`. Or copy the skill folder (plugins/ce/skills/planning-products in rileyhilliard/claude-essentials) into .agents/skills/planning-products in your project. Codex loads it when a task matches its description.
Can I use Planning Products 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 rileyhilliard/claude-essentials --skill planning-products -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-products, .gemini/skills/planning-products, .github/skills/planning-products and .opencode/skills/planning-products in your project.
What does Planning Products need to run?
SKILL.md names no scripts, command-line tools or credentials: Planning Products is instructions for the agent only.
Does Planning Products 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 Planning Products 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 Planning Products use?
Planning Products 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 Planning Products use?
About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.6k tokens, read only when the agent opens those files.
What are the alternatives to Planning Products?
Skills that share tags, products or a category with Planning Products: Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Ralph Tui Create JSON (subsy/ralph-tui, 2.5k stars) and To Prd (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Planning Products?
rileyhilliard (a GitHub user) maintains it in rileyhilliard/claude-essentials, which has 130 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on August 18, 2026.
Source: rileyhilliard/claude-essentials on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.