generate-rfcs SKILL.md skillA

generate-rfcs from nurettincoban/ai-prd-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add nurettincoban/ai-prd-workflow/generate-rfcs@v3.1.0

Pins v3.1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
nurettincoban/ai-prd-workflow
Path
skills/generate-rfcs/SKILL.md
Versions recorded
2
Latest version
v3.1.0, committed Nov 15, 2026
First version recorded
Oct 1, 2026
Size
11,261 bytes
Repository stars
310
License
MIT

Break the PRD into sequenced implementation RFCs under RFCs/ with an RFCS.md index, then cold-read each RFC for gaps.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

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 PRD-REVIEW.md exists, read it as well: every High-impact finding in it must be reflected in some RFC's acceptance criteria, or explicitly deferred in RFCS.md.

## WHEN A QUESTION HAS NO ANSWER
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_uechn4s4dtzfi7oo/052cb2c35fd5910c2ec1d28522bc48a0ad636afbfb6ac6343304ab0c62ac19e3.json

Then /plugin install generate-rfcs@markdownregistry-uechn4s4dtzfi7oo in Claude Code. It installs v3.1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add nurettincoban/ai-prd-workflow/generate-rfcs@sha256:052cb2c35fd5910c

The line at the top of this page pins the label v3.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_uechn4s4dtzfi7oo.svg)](https://markdownregistry.com/a/art_uechn4s4dtzfi7oo)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in nurettincoban/ai-prd-workflow/generate-rfcs since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of generate-rfcs from somewhere else? Ask it: where did my generate-rfcs come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Oct 1, 2026 and Nov 15, 2026, about one every 45 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
v3.1.0 latest2026-11-15 82696b3 11,261 BA view · diff
v3.0.02026-10-01 0aeccc5 8,211 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (11261 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

nurettincoban/ai-prd-workflow · 310 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_uechn4s4dtzfi7oo
GET https://markdownregistry.com/api/v1/resolve?ref=nurettincoban/ai-prd-workflow/generate-rfcs
GET https://markdownregistry.com/api/v1/blob/052cb2c35fd5910c2ec1d28522bc48a0ad636afbfb6ac6343304ab0c62ac19e3

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from nurettincoban/ai-prd-workflow

AGENTS.md AGENTS.md file
nurettincoban/ai-prd-workflow · AGENTS.md
git:20261001.5338e51 · audit A · 310 stars
CLAUDE.md CLAUDE.md file
nurettincoban/ai-prd-workflow · CLAUDE.md
git:20261001.5fd94dd · audit B · 310 stars
AGENTS.md@examples/todo-cli AGENTS.md file
nurettincoban/ai-prd-workflow · examples/todo-cli/AGENTS.md
git:20261115.82696b3 · audit B · 310 stars
CLAUDE.md@examples/todo-cli CLAUDE.md file
nurettincoban/ai-prd-workflow · examples/todo-cli/CLAUDE.md
git:20261115.82696b3 · audit B · 310 stars
create-prd SKILL.md skill
nurettincoban/ai-prd-workflow · skills/create-prd/SKILL.md · Interview the user about a product idea and write PRD.md. Use at the start of a new project, before features, rules or…
v3.1.0 · audit A · 310 stars
document-existing SKILL.md skill
nurettincoban/ai-prd-workflow · skills/document-existing/SKILL.md · Document an existing codebase as PRD.md, FEATURES.md and RULES.md, so new work is planned against the code as it is…
v3.1.0 · audit A · 310 stars
extract-features SKILL.md skill
nurettincoban/ai-prd-workflow · skills/extract-features/SKILL.md · Turn PRD.md into FEATURES.md: permanent feature IDs, MoSCoW priorities, acceptance criteria and the PRD requirement…
v3.1.0 · audit A · 310 stars
generate-rules SKILL.md skill
nurettincoban/ai-prd-workflow · skills/generate-rules/SKILL.md · Write RULES.md, the project standards the AI must follow, with registry-verified dependency versions and permanent rule…
v3.1.0 · audit A · 310 stars
implement-rfc SKILL.md skill
nurettincoban/ai-prd-workflow · skills/implement-rfc/SKILL.md · Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every…
v3.1.0 · audit A · 310 stars
manage-changes SKILL.md skill
nurettincoban/ai-prd-workflow · skills/manage-changes/SKILL.md · Assess a requirement change mid-project against the rules and past decisions, then update every affected artifact…
v3.1.0 · audit A · 310 stars
review-rfc SKILL.md skill
nurettincoban/ai-prd-workflow · skills/review-rfc/SKILL.md · Review an implemented RFC in a fresh context against its acceptance criteria, RULES.md and the test plan, and save the…
v3.1.0 · audit A · 310 stars
test-strategy SKILL.md skill
nurettincoban/ai-prd-workflow · skills/test-strategy/SKILL.md · Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.
v3.1.0 · audit A · 310 stars

Every file in nurettincoban/ai-prd-workflow

Browse by kind, by grade A, or by owner.