Borrowing it
Nothing to install: this file belongs to nurettincoban/ai-prd-workflow. 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/nurettincoban/ai-prd-workflow/main/.claude/commands/generate-rfcs.mdgit clone --depth 1 https://github.com/nurettincoban/ai-prd-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/commands/nurettincoban/ai-prd-workflow/generate-rfcs)<a href="https://agentmods.dev/commands/nurettincoban/ai-prd-workflow/generate-rfcs"><img src="https://agentmods.dev/badge/commands/nurettincoban/ai-prd-workflow/generate-rfcs/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/nurettincoban/ai-prd-workflow/generate-rfcs"><img src="https://agentmods.dev/badge/commands/nurettincoban/ai-prd-workflow/generate-rfcs.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.00009 | $0.01493 |
| Opus 5 | $0.00005 | $0.00746 |
| Sonnet 5 | $0.00002 | $0.00299 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
generate-rfcs 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert software architect and project manager tasked with breaking down the Product Requirements Document (PRD.md), features list (FEATURES.md), and project rules (RULES.md) — or the documents provided in the conversation — into manageable Request for Comments (RFC) documents for implementation.
Create a set of well-structured RFC documents that divide the project into logical, implementable units of work. Each RFC should represent a cohesive, reasonably-sized portion of the application that can be implemented as a unit.
IMPORTANT: RFCs are numbered in a valid implementation order, and the ordering is critical. Each RFC must be fully implementable once its declared predecessors are complete.
If any critical information is missing or unclear, ask specific questions before proceeding.
SCOPE THE CHECKLIST TO THE PRODUCT TYPE
First classify the product: web app · mobile app · library/SDK · CLI · service/API · data pipeline · game.
Apply only the sections and checks that fit that type. For a library/SDK, skip infrastructure, scalability, regulatory, business-model, accessibility, responsive-design, state-management, and auth concerns -- instead probe: public API surface and consistency, semver/deprecation policy, peer-dependency ranges, bundle size, tree-shaking, types quality, the public/internal boundary, and mutation of caller-owned data. Every other product type has its own equivalents; work them out before applying the generic list below.
State which product type you classified and which checks you skipped. Skipping must be visible and auditable, never silent -- a generated "no SQL injection vectors identified" in a library that has no SQL manufactures false confidence.
This applies per RFC as well as to the set: do not emit a "Database Schema Changes" or "State Management" section in every RFC of a product that has neither.
WHEN ARTIFACTS CONFLICT
Order of authority: PRD.md > FEATURES.md > RULES.md > RFCs > generated plans. Where this prompt's generic guidance conflicts with RULES.md, RULES.md wins -- it was written for this project and this prompt was not. Never resolve a contradiction between two artifacts silently: state it, say which one you followed and why, and flag the other for correction.
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.
- 9d ago First seen · 106 lines · 9 tokens per session scan A 4b8c837afec1
generate-rfcs is a command published in the GitHub repository nurettincoban/ai-prd-workflow (285 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 1,493 once invoked, about $0.0000 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
enhance-prompt
Command "enhance-prompt" from VoDaiLocz/Enhance-Prompt, covering enhance prompt workflow, 1. intake and scoring (enhance-prompt/skill.md), 5. ambiguity check and 8. iteration (enhance-prompt/references/iteration-mode.md).
camp-init
Create a new camp with the standard directory structure. A camp was previously called a campaign; camp init is the same command either way.
fest-commit
Commit changes with festival traceability metadata.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
fest-list
List all festivals with their status and completion percentage.
lfe-session
You are acting as a senior framework architect helping improve the Library-First Engineering (LFE) framework. This is a META session — you are working ON the framework, not WITH it. Do NOT run the LFE pipeline (/lfe-boot, /lfe-architect, etc.) — those are for product repos that use LFE as a template.