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-from-project.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-from-project)<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/auto-from-project"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/auto-from-project.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.00023 | $0.04415 |
| Opus 5 | $0.00012 | $0.02207 |
| Sonnet 5 | $0.00005 | $0.00883 |
| Haiku 4.5 | $0.00002 | $0.00441 |
Grade A, and why
Auto-Generate PRD from All Project Files 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.
How it starts
The opening of the file, as written. The whole thing — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Generate PRD from All Project Markdown Files
Overview
Automatically discover ALL .md files in the project, analyze their content, map to appropriate PRD sections using filename patterns, and generate a comprehensive PRD with fresh YAML frontmatter.
Instructions
Step 1: Discover All Markdown Files
Use glob pattern to find ALL .md files in project:
# Find all markdown files (no exclusions)
**/*.md
List all discovered files to user:
🔍 Discovered Markdown Files:
- README.md
- docs/requirements.md
- docs/features.md
- docs/architecture.md
- features/user-auth.md
- features/dashboard.md
- [... all other .md files]
Total: XX markdown files found
Proceeding to analyze and consolidate...
Step 2: Categorize Files by Pattern
Map each file to PRD section using filename patterns (priority order):
Pattern Matching Rules:
- README.md → Executive Summary + Product Vision (highest priority)
- requirements.md* (case-insensitive) → Requirements section
- features.md* or feature.md* → Features section
- user.md* or persona.md* → Target Users section
- architecture.md* or tech.md* or technical.md* → Technical Architecture
- security.md* or compliance.md* → Security & Compliance section
- api.md* → API Specifications
- design.md* or ui.md* or ux.md* → Design section
- test.md* or qa.md* → Testing Strategy
- deploy.md* or release.md* → Deployment section
- risk.md* → Risks & Mitigation
- timeline.md* or roadmap.md* or schedule.md* → Timeline/Roadmap
- metric.md* or kpi.md* or success.md* → Success Metrics
- glossary.md* or terms.md* → Glossary/Appendices
- Others → Categorized by directory name or Appendices
Directory-based fallback categorization:
- Files in
/features/or/feature/→ Features - Files in
/docs/requirements/→ Requirements - Files in
/architecture/or/arch/→ Technical Architecture - Files in
/api/→ API Specifications - Files in
/design/→ Design - Files in
/compliance/or/security/→ Security & Compliance - Unknown → Appendices (preserve as-is)
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 · 530 lines · 23 tokens per session scan A 2fa4828f9f60
Auto-Generate PRD from All Project Files is a command published in the GitHub repository Kandil7/prprompts-flutter-generator (11 stars, last pushed 9mo ago), licensed MIT. It adds 23 tokens to every session and 4,415 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.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.entity
Create Zorphy entities with fields.
speckit.zuraffa.generate-commands
Regenerate all extension command files from zfa manifest.