Prd To Plan

Name: Prd To Plan
Author: Asymmetric-al

ASecurity

Legacy router from PRD/spec intent to the current Matt Pocock spec and ticket flow. Prefer to-spec and to-tickets.

383 stars
0 votes
0 copies
2 views
Added September 3, 2026

code-qualitycode-reviewgit

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 3, 2026

npx -y skills add Asymmetric-al/core --skill prd-to-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prd To Plan?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/asymmetric-al-prd-to-plan-core/badge)](https://www.skillsdirectory.com/skills/asymmetric-al-prd-to-plan-core)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: prd-to-plan
description: Legacy router from PRD/spec intent to the current Matt Pocock spec and ticket flow. Prefer to-spec and to-tickets.
---

There is **no** `prd-to-plan` skill in
[mattpocock/skills](https://github.com/mattpocock/skills). Use the current
spec/ticket flow instead:

1. **`to-spec`** - `docs/ai/skills/to-spec/SKILL.md` - produce the spec
   (align with **OpenSpec**: `openspec/specs/**`, `openspec/changes/**`).
2. **`to-tickets`** - `docs/ai/skills/to-tickets/SKILL.md` - break the spec
   into tracer-bullet tickets with blocking edges.
3. Use **`implement`**, **`code-review`**, **`domain-modeling`**, and
   **`improve-codebase-architecture`** as the work moves from tickets to code.

See **`references/upstream.md`**.