Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.
Install Prd To Plan
$ npx skills add Dwlad90/stylex-swc-plugin --skill prd-to-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Dwlad90/stylex-swc-plugin prd-to-plan --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/Dwlad90/stylex-swc-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prd-to-plan .claude/skills/prd-to-plan && 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-to-plan" agent skill from https://github.com/Dwlad90/stylex-swc-plugin/tree/develop/.agents/skills/prd-to-plan into .claude/skills/prd-to-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-plan", 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/Dwlad90/stylex-swc-plugin/tree/develop/.agents/skills/prd-to-planType 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 Dwlad90/stylex-swc-plugin --skill prd-to-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Dwlad90/stylex-swc-plugin prd-to-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dwlad90/stylex-swc-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/prd-to-plan .agents/skills/prd-to-plan && 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-to-plan" agent skill from https://github.com/Dwlad90/stylex-swc-plugin/tree/develop/.agents/skills/prd-to-plan into .agents/skills/prd-to-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-plan", 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 Dwlad90/stylex-swc-plugin --skill prd-to-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Dwlad90/stylex-swc-plugin prd-to-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dwlad90/stylex-swc-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/prd-to-plan .cursor/skills/prd-to-plan && 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-to-plan" agent skill from https://github.com/Dwlad90/stylex-swc-plugin/tree/develop/.agents/skills/prd-to-plan into .cursor/skills/prd-to-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-plan", 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/Dwlad90/stylex-swc-plugin.git --path .agents/skills/prd-to-plan--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 Dwlad90/stylex-swc-plugin --skill prd-to-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Dwlad90/stylex-swc-plugin prd-to-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dwlad90/stylex-swc-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/prd-to-plan .gemini/skills/prd-to-plan && 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-to-plan" agent skill from https://github.com/Dwlad90/stylex-swc-plugin/tree/develop/.agents/skills/prd-to-plan into .gemini/skills/prd-to-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-plan", 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 Dwlad90/stylex-swc-plugin prd-to-planInstalls 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 Dwlad90/stylex-swc-plugin --skill prd-to-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Dwlad90/stylex-swc-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/prd-to-plan .github/skills/prd-to-plan && 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-to-plan" agent skill from https://github.com/Dwlad90/stylex-swc-plugin/tree/develop/.agents/skills/prd-to-plan into .github/skills/prd-to-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-plan", 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 Dwlad90/stylex-swc-plugin --skill prd-to-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Dwlad90/stylex-swc-plugin prd-to-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dwlad90/stylex-swc-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/prd-to-plan .opencode/skills/prd-to-plan && 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-to-plan" agent skill from https://github.com/Dwlad90/stylex-swc-plugin/tree/develop/.agents/skills/prd-to-plan into .opencode/skills/prd-to-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prd-to-plan", 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
prd-to-plan- GitHub stars
- 112
- Token cost
- ~767 tokens
- SKILL.md length
- 382 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.
- Works in 6 steps: Confirm the PRD is in context → Explore the codebase → Identify durable architectural decisions → …
- User wants to break down a PRD
- SKILL.md covers Process, Architectural decisions, Phase 1: and Phase 2:
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Prd To Plan is an agent skill from Dwlad90/stylex-swc-plugin. Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering PRD writing and Planning. It works with Turborepo, Vite, webpack and Next.js. The repository describes itself as: Rust/NAPI-RS/SWC compiler for StyleX CSS-in-JS — a faster, Babel-free replacement for @stylexjs/babel-plugin with plugins for Next.js, Vite, webpack, Rspack, Rollup, Turbopack… The licence is MIT.
When your agent uses it
- User wants to break down a PRD
- Create an implementation plan
- Plan phases from a PRD
- Mentions tracer bullets
Example prompts
- “tracer bullets”
- “/prd-to-plan”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 03ad760. 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
Prd To Plan loads about 767 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 382 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 Dwlad90/stylex-swc-plugin at commit 03ad760, republished under its MIT licence (© Dwlad90). 382 words, ~767 tokens.
Download SKILL.mdSave it as
.claude/skills/prd-to-plan/SKILL.md (or your agent's skills folder).- name
- prd-to-plan
- description
- Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
PRD to Plan
Break a PRD into a phased implementation plan using vertical slices (tracer
bullets). Output is a Markdown file in ./plans/.
Process
1. Confirm the PRD is in context
The PRD should already be in the conversation. If it isn't, ask the user to paste it or point you to the file.
2. Explore the codebase
If you have not already explored the codebase, do so to understand the current architecture, existing patterns, and integration layers.
3. Identify durable architectural decisions
Before slicing, identify high-level decisions that are unlikely to change throughout implementation:
- Route structures / URL patterns
- Database schema shape
- Key data models
- Authentication / authorization approach
- Third-party service boundaries
These go in the plan header so every phase can reference them.
4. Draft vertical slices
Break the PRD into tracer bullet phases. Each phase is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
<vertical-slice-rules>
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
- A completed slice is demoable or verifiable on its own
- Prefer many thin slices over few thick ones
- Do NOT include specific file names, function names, or implementation details that are likely to change as later phases are built
- DO include durable decisions: route paths, schema shapes, data model names
</vertical-slice-rules>Show full SKILL.md (164 more words)Show less
5. Quiz the user
Present the proposed breakdown as a numbered list. For each phase show:
- Title: short descriptive name
- User stories covered: which user stories from the PRD this addresses
Ask the user:
- Does the granularity feel right? (too coarse / too fine)
- Should any phases be merged or split further?
Iterate until the user approves the breakdown.
6. Write the plan file
Create ./plans/ if it doesn't exist. Write the plan as a Markdown file named
after the feature (e.g. ./plans/user-onboarding.md). Use the template below.
<plan-template>
# Plan: <Feature Name>Source PRD:
<brief identifier or link>
Architectural decisions
Durable decisions that apply across all phases:
- Routes: ...
- Schema: ...
- Key models: ...
- (add/remove sections as appropriate)
Phase 1: <Title>
User stories: <list from PRD>
What to build
A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
Acceptance criteria
- Criterion 1
- Criterion 2
- Criterion 3
Phase 2: <Title>
User stories: <list from PRD>
What to build
...
Acceptance criteria
- ...
<!-- Repeat for each phase --></plan-template>© Dwlad90, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/prd-to-plan of Dwlad90/stylex-swc-plugin.
Open the folder on GitHubat commit 03ad760
Compare with similar skills
Prd To Plan 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 To Plan this skillDwlad90/stylex-swc-plugin | 112 | — | ~767 | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Runtime Debugvercel/next.js | 143k | 1 repos | ~618 | Automated safety check: Pass | MIT | |
| Code to PRDalirezarezvani/claude-skills | 28k | 1 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Hybrid RalphTaoidle/plan-cascade | 133 | — | ~4.1k | Automated safety check: Notes | MIT | |
| Next Rspackvercel/next.js | 143k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Runtime Debug
vercel/next.js
Debug and verification workflow for runtime-bundle and module-resolution regressions.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Hybrid Ralph
Taoidle/plan-cascade
Hybrid architecture combining Ralph's PRD format with Planning-with-Files' structured approach.
- Official
Next Rspack
vercel/next.js
Maintain @next/rspack-core and @next/rspack-binding packages.
NEAR dApp Builder
internet-court/internet-court-skill
Scaffolds new NEAR dApps with create-near-app or adds NEAR wallet sign-in, contract calls and transaction signing to an existing React or plain JavaScript app.
Related
Categories
Questions about Prd To Plan
What does Prd To Plan do?
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Prd To Plan is an agent skill from Dwlad90/stylex-swc-plugin./plans/.
When should I use Prd To Plan?
Prd To Plan fits situations like: user wants to break down a PRD; create an implementation plan; plan phases from a PRD; mentions tracer bullets.
How do I install Prd To Plan in Claude Code?
Run `npx skills add Dwlad90/stylex-swc-plugin --skill prd-to-plan -a claude-code`. Or copy the skill folder (.agents/skills/prd-to-plan in Dwlad90/stylex-swc-plugin) into .claude/skills/prd-to-plan in your project. Claude Code loads it when a task matches its description.
How do I install Prd To Plan in Codex?
Run `npx skills add Dwlad90/stylex-swc-plugin --skill prd-to-plan -a codex`. Or copy the skill folder (.agents/skills/prd-to-plan in Dwlad90/stylex-swc-plugin) into .agents/skills/prd-to-plan in your project. Codex loads it when a task matches its description.
Can I use Prd To Plan 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 Dwlad90/stylex-swc-plugin --skill prd-to-plan -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-to-plan, .gemini/skills/prd-to-plan, .github/skills/prd-to-plan and .opencode/skills/prd-to-plan in your project.
What does Prd To Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Prd To Plan is instructions for the agent only.
Does Prd To Plan 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 Prd To Plan 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 Prd To Plan use?
Prd To Plan 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 Prd To Plan use?
About 767 tokens (SKILL.md is roughly 3.1k 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 Prd To Plan?
Skills that share tags, products or a category with Prd To Plan: Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Runtime Debug (vercel/next.js, 143k stars), Code to PRD (alirezarezvani/claude-skills, 28k stars) and Hybrid Ralph (Taoidle/plan-cascade, 133 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prd To Plan?
Dwlad90 (a GitHub user) maintains it in Dwlad90/stylex-swc-plugin, which has 112 GitHub stars. The repository was last updated on October 9, 2026.
Source: Dwlad90/stylex-swc-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.