agentmods.dev

sdd-prd

sdd-prd is a skill for Claude Code, Codex from felipefontoura/pi-sdd-kit. It costs 71 tokens per session (1,574 once invoked), scanned A, original, MIT.

A requirements-writing workflow for turning an approved idea, plan, or feature request into a `requirements.md` document. It describes who the feature serves, what it must do, why it matters, and how completion will be checked.

In plain words
What is it for?
Use it to write user stories, acceptance criteria, functional requirements, non-functional requirements, and feature boundaries for small or medium projects.
Why use it?
It separates the product promise from implementation details. This gives developers a shared description of the feature and clear acceptance conditions before design or coding begins.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 22repo +1 2mo ago A scan 71 tokens original MIT

Good fit Use it to write user stories, acceptance criteria, functional requirements, non-functional requirements, and feature boundaries for small or medium projects.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/felipefontoura/pi-sdd-kit/sdd-prd
View source ↗ felipefontoura/pi-sdd-kit felipefontoura.com
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 felipefontoura/pi-sdd-kit --skill sdd-prd
Clone the repo
git clone --depth 1 https://github.com/felipefontoura/pi-sdd-kit

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 sdd-prd

README.md
[![agentmods](https://agentmods.dev/badge/skills/felipefontoura/pi-sdd-kit/sdd-prd/github.svg)](https://agentmods.dev/skills/felipefontoura/pi-sdd-kit/sdd-prd)
Your own site
<a href="https://agentmods.dev/skills/felipefontoura/pi-sdd-kit/sdd-prd"><img src="https://agentmods.dev/badge/skills/felipefontoura/pi-sdd-kit/sdd-prd/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 sdd-prd

Your own site · 80×15
<a href="https://agentmods.dev/skills/felipefontoura/pi-sdd-kit/sdd-prd"><img src="https://agentmods.dev/badge/skills/felipefontoura/pi-sdd-kit/sdd-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,574 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 original 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.00071 $0.01574
Opus 5 $0.00036 $0.00787
Sonnet 5 $0.00014 $0.00315
Haiku 4.5 $0.00007 $0.00157

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

Security

Grade A, and why

sdd-prd 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.

skills/sdd-prd/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SDD PRD / Requirements

Create a practical requirements.md artifact for a small or medium project feature.

Purpose

Requirements define the product contract. They explain what the feature must do, who it serves, why it matters, and how the team will know it is done. They must not prescribe implementation details.

Workflow

  1. Load the SDD reference.

    • Read ../_shared/references/sdd-practical.md.
    • Apply the Language Policy: respond and write artifacts in the user's initial chat language while keeping skill instructions and templates in EN-US.
    • Read ../_shared/references/templates.md when drafting the artifact.
    • Use package-level templates/requirements.md as the user-facing template when available.
    • Load relevant .ai/steering/*.md files when present, especially product.md, tech-stack.md, conventions.md, and principles.md.
    • If .ai/strategy/handoff/strategy-brief.md exists, read it as optional upstream context; use it to seed product requirements, but do not require it or let it bypass requirements approval.

  2. Locate or create the feature spec directory.

    • Use .ai/sdd/specs/NNN-feature-name/.
    • If the user names an existing feature, resolve it from actual .ai/sdd/specs/*/ directories and artifact titles.
    • If exactly one existing feature matches, use its directory and validate its .status against the official status values from sdd-practical.md.
    • If an existing feature .status is missing or invalid, stop and ask the user to repair it before updating requirements.
    • If multiple existing features may match, list candidates and ask the user to choose.
    • If creating a new feature, determine the next numeric prefix from the filesystem, not from memory and not from .ai/sdd/INDEX.md.
    • Numbering algorithm: list directories under .ai/sdd/specs/, extract prefixes matching ^([0-9]+)-, use max + 1, zero-pad to at least 3 digits, and preserve wider existing prefix width if present.
    • Generate a safe short slug from the feature name; ask the user if a safe slug is unclear.
    • Before creating a new spec directory, state the resolved path and continue only when it fits the user's intent.
    • Create .status with requirements:draft when starting a new requirements artifact.

Read the full file on GitHub · 114 lines

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 · 114 lines · 71 tokens per session scan A 1f6e9c853a29

Subscribe to this mod's changes

sdd-prd is a skill published in the GitHub repository felipefontoura/pi-sdd-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,574 once invoked, about $0.0004 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-08-30.

Claude CodePlanningWriting and docsai-agentspi-agentpi-devpi-packageskills
Related

Other skills, from other repositories

surf

Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.

w-winter/dot314 · 60 tokens

prose-review

Review prose written for others (e.g., user-facing documentation, prompts for other LLMs, reports, plans, inline comments, docstrings) for local jargon leakage, orphaned references, missing grounding, and audience or genre mismatch. Always run on prose you produce or materially edit, except for routine conversational…

w-winter/dot314 · 84 tokens

text-search

Search indexed text corpora with qmd. For indexed content, prefer qmd over grep.

w-winter/dot314 · 22 tokens

repoprompt-tool-guidance-refresh

Refresh RepoPrompt tool guidance when the CLI/MCP surface changes. Tracks RepoPrompt CE (rpce-cli, the maintained target) across versions, and can diff the frozen Classic CLI (rp-cli) against CE. Uses /.pi/agent/skills/repoprompt-tool-guidance-refresh/scripts/track-rp-version.sh to capture/diff --help and -l (tool…

w-winter/dot314 · 115 tokens

xcodebuildmcp

Build/test Xcode projects via the XcodeBuildMCP MCP server using a local CLI wrapper for pi (no MCP support). Use when the user mentions Xcode, xcodebuild, iOS builds/tests, or XcodeBuildMCP.

w-winter/dot314 · 56 tokens

open-pencil

Work with Figma .fig design files and the running OpenPencil editor — inspect structure, query nodes, analyze design tokens, export PNG/SVG/PDF/JSX, and modify designs programmatically. Use when asked to open, inspect, export, analyze, or edit .fig files, or to control the running OpenPencil app.

open-pencil/skills · 73 tokens