Skip to content
Back to skills

Sdd Create Prd

ASecurity

SDD PRD when asked to create or update product requirements; does not define architecture or tasks.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 19, 2026
ai-agentsgit

Security analysis

A100/100

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

Scanned September 29, 2026

npx -y skills add dougcunha/TokenHound --skill sdd-create-prd --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sdd Create Prd?

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

Security grade badge for Sdd Create Prd
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dougcunha-sdd-create-prd/badge)](https://www.skillsdirectory.com/skills/dougcunha-sdd-create-prd)

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: sdd-create-prd
description: SDD PRD when asked to create or update product requirements; does not define architecture or tasks.
argument-hint: --prompt "feature description" [--update]
disable-model-invocation: true
---

# Create SDD PRD

1. Extract the problem, outcome, and feature name from the request. Resolve `tasks/prd-[slug]/prd.md`; a new slug is `[NN]-[name]`, where `[NN]` is the next two-digit number after the existing folders, in implementation order, and `[name]` is kebab-case. If the PRD exists, reuse it without overwriting. Update only when authorized; preserve unchanged IDs. When `tasks/prd-[slug]/context-snapshot.md` exists, load it through the Load branch of `.agents/skills/sdd-snapshot/SKILL.md` before reading sources.
   **Output:** unambiguous destination and operation; request only missing information that prevents identifying them.
2. Inventory users, journeys, metrics, FR, NFR, constraints, dependencies, accessibility, and out-of-scope items. Consult local evidence, including `docs/specs/`, before researching public rules or integrations in primary sources; send read-only explorers only when the local evidence spans many files. Record origin and distinguish fact, assumption, and product decision; ask only about gaps that change scope or acceptance.
   **Output:** every obligation has evidence or an explicit assumption; blocking decisions are identified.
3. When drafting, read [assets/prd.template.md](assets/prd.template.md) in full. Use stable IDs `OBJ-01`, `US-01`, `FR-01`, and `NFR-01`, each with observable acceptance. Keep architecture and sequencing in the TechSpec. Record supplied stack and platform constraints.
   **Output:** all applicable sections filled; unique IDs; no requirement without acceptance.
4. Write only the PRD and report path, pending items, and obligations added, changed, or removed. Point out derived artifacts to revalidate without editing them. In the orchestrated flow, return the artifact for product HIL; previous authorization applies to the scope it covers. In standalone use, run the session pause from that reference with `sdd-create-techspec` as next step.
   **Output:** reviewable PRD on disk; source divergences and conflicting IDs resolved or explicitly pending.

Read each source once per version; use links for extensive evidence. On updates, preserve unchanged sections to reduce diff and context.

Files in this skill

  • SKILL.md1.8 KB
  • agents/openai.yaml43 B
  • assets/prd.template.md1.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.