Borrowing it
Nothing to install: this file belongs to Kandil7/prprompts-flutter-generator. 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/Kandil7/prprompts-flutter-generator/master/.claude/commands/prd/auto-generate.mdgit clone --depth 1 https://github.com/Kandil7/prprompts-flutter-generatorWrote 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/kandil7/prprompts-flutter-generator/auto-generate)<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/auto-generate"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/auto-generate.svg" alt="Measured on agentmods" 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.00017 | $0.02340 |
| Opus 5 | $0.00009 | $0.01170 |
| Sonnet 5 | $0.00003 | $0.00468 |
| Haiku 4.5 | $0.00002 | $0.00234 |
Grade A, and why
Auto Generate 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 7d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Generate PRD from Project Description
Overview
Automatically generate a complete Product Requirements Document from a simple project description file. No user interaction required - full AI inference.
Input File Detection
Look for description files in this order:
- File specified by user:
--file path/to/description.md project_description.md(root directory)docs/project_description.mdPROJECT_DESCRIPTION.mdREADME.md(if contains project description)
Inference Rules
Step 1: Read Description File
Extract:
- App name and purpose
- Target users
- Key features (3-10)
- Special requirements (compliance, offline, etc.)
Step 2: Infer Project Type
Keywords → Type:
- "patient", "doctor", "medical", "health", "HIPAA", "telemedicine" → healthcare
- "payment", "bank", "transaction", "credit card", "financial", "PCI" → fintech
- "student", "teacher", "course", "learning", "education", "FERPA" → education
- "delivery", "tracking", "shipping", "logistics", "fleet" → logistics
- "shopping", "cart", "checkout", "ecommerce", "marketplace" → ecommerce
- "business", "workflow", "productivity", "SaaS", "enterprise" → saas
- None of above → generic
Step 3: Infer Compliance Requirements
Keywords → Compliance:
- "HIPAA", "PHI", "protected health information" → Add "hipaa"
- "PCI-DSS", "PCI", "credit card", "payment card" → Add "pci-dss"
- "GDPR", "European", "EU users", "data protection" → Add "gdpr"
- "SOX", "Sarbanes-Oxley" → Add "sox"
- "COPPA", "children under 13", "parental consent" → Add "coppa"
- "FERPA", "student records" → Add "ferpa"
- "FDA", "medical device" → Add "fda"
Step 4: Infer Platforms
Default: ["ios", "android"] (if not mentioned)
Keywords → Platforms:
- "iOS", "iPhone", "iPad" → Add "ios"
- "Android", "Play Store" → Add "android"
- "web", "website", "browser" → Add "web"
- "desktop", "Windows", "macOS" → Add respective platform
Step 5: Infer Authentication Method
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.
- 7d ago First seen · 317 lines · 17 tokens per session scan A 64fea6f0f629
Auto Generate PRD is a command published in the GitHub repository Kandil7/prprompts-flutter-generator (11 stars, last pushed 9mo ago), licensed MIT. It adds 17 tokens to every session and 2,340 once invoked, about $0.0001 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.
Other commands, from other repositories
speckit.chore.fetch
Load an existing GitHub issue into the chore workflow and seed a triage draft.
speckit.gh-triage.feature
Create a GitHub issue describing a new feature, label it with the configured feature label, and optionally auto-run speckit.specify to turn it into a spec.
speckit.bug.pr
Open a pull request for the applied bug fix, linking the tracked issue.
speckit.tdd.verify
Audit TDD discipline by delegating to zfa tdd verify (mutation testing, evidence integrity); the LLM interprets the verdict and drives remediation.
speckit.spec-stats.open
On-demand view of everything not complete: what stage each is stuck at, what the immediate next artifact/command is, oldest-untouched first, stale warnings past staleafterdays.
speckit.zuraffa.generate-commands
Regenerate all extension command files from zfa manifest.