Agent skill

Prd To Plan

Converts PRD into phased plan via tracer-bullet vertical slices.

Apache-2.0Auto-check: notesProduct & Project Management

Install Prd To Plan

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/app/skills/prd-to-plan .claude/skills/prd-to-plan && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "prd-to-plan" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/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

$skill-installer install https://github.com/softspark/ai-toolkit/tree/main/app/skills/prd-to-plan

Type 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.

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-plan -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-plan --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/app/skills/prd-to-plan .agents/skills/prd-to-plan && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "prd-to-plan" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/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.

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-plan -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-plan --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/app/skills/prd-to-plan .cursor/skills/prd-to-plan && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "prd-to-plan" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/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

$ gemini skills install https://github.com/softspark/ai-toolkit.git --path app/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.

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-plan -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-plan --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/app/skills/prd-to-plan .gemini/skills/prd-to-plan && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "prd-to-plan" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/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.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-plan

Installs 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).

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-plan -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/app/skills/prd-to-plan .github/skills/prd-to-plan && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "prd-to-plan" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/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.

skills CLI

$ npx skills add softspark/ai-toolkit --skill prd-to-plan -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install softspark/ai-toolkit prd-to-plan --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/softspark/ai-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/app/skills/prd-to-plan .opencode/skills/prd-to-plan && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "prd-to-plan" agent skill from https://github.com/softspark/ai-toolkit/tree/main/app/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: 179
Token cost: ~1.3k tokens
SKILL.md length: 618 words
Files: 1
Skills in repo: 112
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Converts PRD into phased plan via tracer-bullet vertical slices.

Works in 6 steps: Confirm PRD is in Context → Explore the Codebase → Identify Durable Architectural Decisions → …
Tasks that involve PRD writing
SKILL.md covers Usage, What This Command Does, Process and Plan Template, plus 3 more sections
Calls gh

What it does

Prd To Plan is an agent skill from softspark/ai-toolkit. Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.

Its SKILL.md is about 1.3k 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. The repository describes itself as: Professional-grade AI coding toolkit: 94 skills, 44 agents, multi-platform (Claude, Cursor, Windsurf, Copilot, Gemini, Cline, Roo Code, Aider, Augment, Antigravity, Codex CLI… The licence is Apache-2.0.

When your agent uses it

Tasks that involve PRD writing
Tasks that involve Planning

Example prompts

“Use the prd-to-plan skill to convert PRD into phased plan via tracer-bullet vertical slices”
“/prd-to-plan”

Requirements

Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, Agent

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Confirm PRD is in Context
Explore the Codebase
Identify Durable Architectural Decisions
Draft Vertical Slices
Quiz the User
Write Plan File

What it can do on your machine

Read from SKILL.md and the folder at commit e40ed87. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Grep
- Glob
- Bash
- Agent
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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 1.3k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 618 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~41
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Grep, Glob, Bash, Agent
```

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 softspark/ai-toolkit at commit e40ed87, republished under its Apache-2.0 licence (© softspark). 618 words, ~1,295 tokens.

Download SKILL.mdSave it as .claude/skills/prd-to-plan/SKILL.md (or your agent's skills folder).

name: prd-to-plan
description: Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.
allowed-tools: Read, Grep, Glob, Bash, Agent
user-invocable: true
effort: high
argument-hint: [PRD issue number or paste PRD]

PRD to Plan

$ARGUMENTS

Break a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in ./plans/.

Usage

/prd-to-plan [PRD issue number or description]

What This Command Does

Loads the PRD (from GitHub issue or conversation)
Explores the codebase to understand architecture
Identifies durable architectural decisions
Drafts vertical slices (tracer bullets)
Quizzes user on granularity
Writes plan file to ./plans/

Process

1. Confirm PRD is in Context

If not provided, ask for the PRD GitHub issue number or content. Fetch with gh issue view <number> if needed.

2. Explore the Codebase

Use Agent (subagent_type=Explore) to understand current architecture, existing patterns, and integration layers.

3. Identify Durable Architectural Decisions

Before slicing, identify decisions unlikely to change:

Route structures / URL patterns
Database schema shape
Key data models
Authentication / authorization approach
Third-party service boundaries

4. Draft Vertical Slices

Break PRD into tracer bullet phases. Each phase is a thin vertical slice cutting through ALL layers end-to-end.

Rule	Description
Complete path	Each slice delivers narrow but COMPLETE path through every layer (schema, API, UI, tests)
Demoable	A completed slice is demoable or verifiable on its own
Thin over thick	Prefer many thin slices over few thick ones
Durable	Do NOT include file names, function names, or implementation details likely to change
Include decisions	DO include durable decisions: route paths, schema shapes, data model names

5. Quiz the User

Present breakdown as numbered list. For each phase show:

Title: short descriptive name
User stories covered: which stories from the PRD

Ask:

Does the granularity feel right? (too coarse / too fine)
Should any phases be merged or split?

Iterate until approved.

6. Write Plan File

Create ./plans/ if needed. Write as ./plans/{feature-name}.md.

Plan Template

markdown

# Plan: {Feature Name}

> Source PRD: #{issue-number}

## Architectural Decisions

Durable decisions that apply across all phases:

- **Routes**: ...
- **Schema**: ...
- **Key models**: ...

---

## Phase 1: {Title}

**User stories**: {list from PRD}

### What to build

Concise description of this vertical slice. End-to-end behavior, not layer-by-layer.

### Acceptance criteria

- [ ] Criterion 1
- [ ] Criterion 2

---

## Phase 2: {Title}

(repeat for each phase)

Rules

MUST slice vertically — every phase cuts through all layers (schema, API, UI, tests). Horizontal layer-by-layer phases defer integration risk to the end.
MUST identify Architectural Decisions before slicing — decisions that apply across phases live in their own section, not repeated in each phase
NEVER embed file paths, function names, or implementation details that couple the plan to current code — the plan outlives the code it describes
NEVER write the plan file before the user approves the slicing — drafts burn tokens and invite scope drift
CRITICAL: each phase is independently demoable on its own. If phase N only makes sense in combination with phase N+1, merge them.
MANDATORY: the first phase ships end-to-end (however thin). Deferring any layer to a later phase defeats tracer-bullet discipline.

Show full SKILL.md (208 more words)Show less

Gotchas

Architectural Decisions feel like premature commitment — "we can decide routes later". In practice, every phase needs a route to hit, so postponing them creates conflicting guesses across phases. Decide once, apply everywhere.
PRDs with long lists of user stories tempt the planner to make each story a phase. User stories are requirements, not phases — group several stories into one vertical slice when they share architecture.
"Demoable" means an external stakeholder can watch the feature work, not that a unit test passes. If a phase only ships backend API with no UI to exercise it, it is not demoable.
Fetching the PRD with gh issue view <n> captures the body but not the comments. Crucial clarifications often live in the comments — include --comments or remind the user to paste important threads.
Plans written against a moving PRD (the PRD is still being edited) invalidate on every edit. Freeze the PRD snapshot at plan-write time, reference the snapshot commit or comment ID.

When NOT to Use

For filing GitHub issues from a plan — use /prd-to-issues
For writing the PRD itself — use /write-a-prd
For planning without a PRD — use /plan (general-purpose)
For stress-testing a plan that already exists — use /grill-me
For refactor planning — use /refactor-plan (incremental commits, not tracer bullets)

Files

Just SKILL.md in app/skills/prd-to-plan of softspark/ai-toolkit.

Open the folder on GitHubat commit e40ed87

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.

Prd To Plan compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Prd To Plan this skillsoftspark/ai-toolkit	179	—	~1.3k	Automated safety check: Notes	Apache-2.0	today
Prd To PlanDwlad90/stylex-swc-plugin	112	—	~767	Automated safety check: Pass	MIT	3 days ago
Hybrid RalphTaoidle/plan-cascade	133	—	~4.1k	Automated safety check: Notes	MIT	6 mo ago
AlignmentOvid/paad	131	—	~4.9k	Automated safety check: Pass	MIT	yesterday
Clarification AnalystGulajavaMinistudio/Mayukai-Theme	139	—	~1.1k	Automated safety check: Pass	MIT	3 mo ago
Feature SpecPackmindHub/packmind	317	—	~1.8k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Prd To Plan
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/.
112 GitHub stars~767 tokensUpdated 3 days ago
Product & Project ManagementAuto-check passed
Hybrid Ralph
Taoidle/plan-cascade
Hybrid architecture combining Ralph's PRD format with Planning-with-Files' structured approach.
133 GitHub stars~4.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check: notes
Alignment
Ovid/paad
A skill your agent uses when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope…
131 GitHub stars~4.9k tokensUpdated yesterday
Product & Project ManagementAuto-check passed
Clarification Analyst
GulajavaMinistudio/Mayukai-Theme
Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.
139 GitHub stars~1.1k tokensUpdated 3 mo ago
Product & Project ManagementAuto-check passed
Feature Spec
PackmindHub/packmind
Generate a Packmind feature specification from a GitHub issue, file, URL, or direct description.
317 GitHub stars~1.8k tokensUpdated today
Product & Project ManagementAuto-check passed
Mcaf Feature Spec
managedcode/Storage
Create or update a feature spec under docs/Features/ with business rules, user flows, system behaviour, verification, and Definition of Done.
138 GitHub stars~959 tokensUpdated 2 days ago
Product & Project ManagementAuto-check passed

Questions about Prd To Plan

What does Prd To Plan do?

Converts PRD into phased plan via tracer-bullet vertical slices. Prd To Plan is an agent skill from softspark/ai-toolkit. Converts PRD into phased plan via tracer-bullet vertical slices.

When should I use Prd To Plan?

Prd To Plan fits situations like: tasks that involve PRD writing; tasks that involve Planning.

How do I install Prd To Plan in Claude Code?

Run `npx skills add softspark/ai-toolkit --skill prd-to-plan -a claude-code`. Or copy the skill folder (app/skills/prd-to-plan in softspark/ai-toolkit) 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 softspark/ai-toolkit --skill prd-to-plan -a codex`. Or copy the skill folder (app/skills/prd-to-plan in softspark/ai-toolkit) 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 softspark/ai-toolkit --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?

Going by SKILL.md and its folder, Prd To Plan needs the command-line tools its instructions call (gh). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, Agent.

Does Prd To Plan access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Prd To Plan safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Prd To Plan use?

Prd To Plan is published under the Apache-2.0 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 1.3k tokens (SKILL.md is roughly 5.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 Prd To Plan?

Skills that share tags, products or a category with Prd To Plan: Prd To Plan (Dwlad90/stylex-swc-plugin, 112 stars), Hybrid Ralph (Taoidle/plan-cascade, 133 stars), Alignment (Ovid/paad, 131 stars) and Clarification Analyst (GulajavaMinistudio/Mayukai-Theme, 139 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?

softspark (a GitHub user) maintains it in softspark/ai-toolkit, which has 179 GitHub stars. The repository holds 112 skills in this directory. The repository was last updated on October 8, 2026.

Source: softspark/ai-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Prd To Plan

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

PRD to Plan

Usage

What This Command Does

Process

1. Confirm PRD is in Context

2. Explore the Codebase

3. Identify Durable Architectural Decisions

4. Draft Vertical Slices

5. Quiz the User

6. Write Plan File

Plan Template

Rules

Gotchas

When NOT to Use

Files

Compare with similar skills

Similar skills

More from softspark/ai-toolkit

Related

Questions about Prd To Plan