prd-to-plan

prd-to-plan is a skill for Claude Code, Codex from Asymmetric-al/core. It costs 30 tokens per session (223 once invoked), scanned A, original, AGPL-3.0.

A legacy route from a product requirements document or specification to a newer specification and ticket workflow. A product requirements document describes what a product or feature should do.

In plain words
What is it for?
Use it when turning PRD or specification intent into the current specification and ticket flow.
Why use it?
It helps direct older planning requests into the project’s current process instead of leaving them in an outdated workflow.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it when turning PRD or specification intent into the current specification and ticket flow.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asymmetric-al/core/prd-to-plan
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Asymmetric-al/core --skill prd-to-plan
Clone the repo
git clone --depth 1 https://github.com/Asymmetric-al/core

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for prd-to-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/asymmetric-al/core/prd-to-plan/github.svg)](https://agentmods.dev/skills/asymmetric-al/core/prd-to-plan)
Your own site
<a href="https://agentmods.dev/skills/asymmetric-al/core/prd-to-plan"><img src="https://agentmods.dev/badge/skills/asymmetric-al/core/prd-to-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for prd-to-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/asymmetric-al/core/prd-to-plan"><img src="https://agentmods.dev/badge/skills/asymmetric-al/core/prd-to-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00223
Opus 5 $0.00015 $0.00112
Sonnet 5 $0.00006 $0.00045
Haiku 4.5 $0.00003 $0.00022

Measured 9d ago against content hash 93d6e072d2a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

prd-to-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/prd-to-plan/SKILL.md · 18 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 18 lines · 30 tokens per session scan A 93d6e072d2a7

Subscribe to this mod's changes

prd-to-plan is a skill published in the GitHub repository Asymmetric-al/core (391 stars, last pushed yesterday), licensed AGPL-3.0. It adds 30 tokens to every session and 223 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens