Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheSmokeDev/taskchad-os/master/.claude/commands/create-prd.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/commands/thesmokedev/taskchad-os/create-prd)<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/create-prd"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/create-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.
<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/create-prd"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/create-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00007 | $0.05741 |
| Opus 5.5 | $0.00003 | $0.02296 |
| Sonnet 5.5 | $0.00001 | $0.01148 |
| Haiku 4.5 | $0.00001 | $0.00574 |
Grade A, and why
create-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 647 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PRD: Generate Product Requirements Document
Overview
Generate a comprehensive Product Requirements Document (PRD) based on the current conversation context and requirements discussed. Use the structure and sections defined below to create a thorough, professional PRD.
Output File
Write the PRD to: $ARGUMENTS (default: PRD.md)
PRD Structure
Create a well-structured PRD with the following sections. Adapt depth and detail based on available information:
Required Sections
1. Intent Statement (50-100 words)
- One sentence: the actual user need or operator goal
- One sentence: why it matters (business impact, pain point, blocking issue)
2. Success Hypothesis (RIGHT Condition)
- Assertive, measurable, binary outcome when the solution works correctly
- Use assertive verbs: "must", "will", "produces", "creates", "returns"
- Must be testable by a machine or a human following a script
3. WRONG-Condition (Falsifiable Failure) ⚠️ MANDATORY — SEE VALIDATION GATE BELOW
- Explicit binary conditions that define failure
- When ANY condition is true, the solution has FAILED
- Each entry must be observable (evidence exists: log, test, screenshot, metric)
- Each entry must be binary (it happened or it didn't — no gradients)
- At least 3 entries required
- At least one must describe a silent failure (ships unnoticed)
- No aspirational language, no implementation prescriptions
- Format:
- {concrete failure description}
4. Non-Goals (Anti-Scope)
- What this solution explicitly does NOT address
- Each entry has a one-line rationale:
- **{Thing}** — {Why} - At least 1 entry required
5. Executive Summary
- Concise product overview (2-3 paragraphs)
- Core value proposition
- MVP goal statement
6. Target Users
- Primary user personas
- Technical comfort level
- Key user needs and pain points
7. Scope (Positive Deliverables)
- Numbered list of concrete artifacts or behaviors
- Each deliverable is verifiable (noun or verb phrase)
- Avoid vague verbs: "improve", "enhance" — use "add", "create", "implement", "expose"
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.
- 1mo ago First seen · 647 lines · 7 tokens per session scan A 7497a633ee22
create-prd is a command published in the GitHub repository TheSmokeDev/taskchad-os (28 stars, last pushed 23d ago), licensed MIT. It adds 7 tokens to every session and 5,741 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
second-brain-mapping
Map your vault: extract structured metadata from every typed file, surface cross-doc insights, optionally build a knowledge graph.
cierre
A sales call just ended: turn its transcript into the full follow-up (CRM, tasks, email draft, reminder, coaching).
daily-journal
Daily journal interview and entry creator with emotional floor tagging.
deconstruct
First-principles analyst: surface hidden assumptions, find foundational truths, rebuild from scratch.
diagnose
Run a self-check on your AI Brain Starter install (CLAUDE.md, Meta folder, skills, hooks, MCPs).
evolve
Cluster hardened instincts into a proposed Command / Skill / Agent (Instinct Engine).