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.
npx skills add smallnest/goal-workflow --skill prd-to-specgit clone --depth 1 https://github.com/smallnest/goal-workflowWrote 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.
[](https://agentmods.dev/skills/smallnest/goal-workflow/prd-to-spec)<a href="https://agentmods.dev/skills/smallnest/goal-workflow/prd-to-spec"><img src="https://agentmods.dev/badge/skills/smallnest/goal-workflow/prd-to-spec.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00077 | $0.03035 |
| Opus 5 | $0.00039 | $0.01517 |
| Sonnet 5 | $0.00015 | $0.00607 |
| Haiku 4.5 | $0.00008 | $0.00303 |
Grade A, and why
prd-to-spec 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 8d 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.
This is a copy
100% identical to prd-to-spec — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prd-to-spec — PRD to Technical Specification
Transform a Product Requirements Document (PRD) into a detailed technical SPEC that an engineer or AI agent can implement against. The PRD says what to build; the SPEC says how to build it.
When to Use
- A
/prdhas been generated and you need to bridge the gap to implementation - You want architecture decisions documented before coding starts
- Multiple developers/agents will implement the feature and need a shared contract
- You need to validate technical feasibility before committing to a PRD
- You want to catch design issues early — before code is written
The Job
- Locate PRD — find or receive the PRD document
- Analyze context (optional) — if a codebase exists, scan it to understand current architecture, patterns, and constraints
- Ask clarifying questions — resolve technical ambiguities (max 3-5 questions)
- Generate SPEC — produce a structured technical specification
- Review — present to user for feedback and iteration
- Save — write final SPEC to agreed location
Step 1: Locate PRD
Find the input PRD in one of these ways:
Provide the PRD to convert:
A. File path (e.g., tasks/prd-priority-system.md)
B. GitHub Issue URL
C. Paste PRD content directly
D. Auto-detect: scan tasks/ directory for recent PRDs
If auto-detecting, list available PRDs and let the user choose:
Found PRDs in tasks/:
1. tasks/prd-priority-system.md (2024-03-15)
2. tasks/prd-user-auth.md (2024-03-10)
Which PRD should I convert? [1/2]
Step 2: Analyze Context (Optional)
Skip this step if no codebase exists yet (greenfield project). In that case, the SPEC will propose architecture from scratch based on the PRD requirements and clarifying questions.
If a codebase exists, scan it to understand:
- Existing architecture — how the current system is structured
- Tech stack — languages, frameworks, libraries already in use
- Patterns — naming conventions, file organization, error handling approach
- Database — current schema, migration tool, ORM
- API style — REST/GraphQL/gRPC, authentication method, response format
- Testing — test framework, coverage patterns, test utilities
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.
- 8d ago First seen · 410 lines · 77 tokens per session scan A 18874c8970d0
prd-to-spec is a skill published in the GitHub repository smallnest/goal-workflow (278 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 3,035 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to prd-to-spec, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
contradiction-analysis
A structured way to analyze difficult problems by identifying competing forces, finding the main conflict, and deciding which side or issue has the greatest effect.
mass-line
A method for collecting feedback and facts from multiple people or sources, turning them into a plan, and checking the plan with those affected.
concentrate-forces
A decision-making method for situations where several tasks compete for limited time, attention, computing power, or budget.
practice-cognition
A method for testing ideas in practice, learning from the results, and improving the next attempt through repeated cycles.
protracted-strategy
A long-term planning method for difficult work that cannot be completed quickly, divided into stages with steady progress over time.
workflows
A workflow guide for tasks that need several kinds of reasoning in sequence, such as research, finding the main conflict, choosing a small starting point, and planning sustained work.