New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Implement Rfc

by nurettincoban in nurettincoban/ai-prd-workflow

Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every acceptance criterion.

MITAuto-check passedProduct & Project Management

Install Implement Rfc

skills CLI
$ npx skills add nurettincoban/ai-prd-workflow --skill implement-rfc -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nurettincoban/ai-prd-workflow implement-rfc --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nurettincoban/ai-prd-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implement-rfc .claude/skills/implement-rfc && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
implement-rfc
GitHub stars
298
Token cost
~1.3k tokens
SKILL.md length
711 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every acceptance criterion.

  • Works in 2 steps: Planning (No Code) → Implementation (After Approval Only)
  • Tasks that involve PRD writing
  • SKILL.md covers Role and Mindset, Context, WHEN ARTIFACTS CONFLICT and Two-Phase Approach, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Implement Rfc is an agent skill from nurettincoban/ai-prd-workflow. Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every acceptance criterion.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. The repository describes itself as: RFC-driven development for AI coding agents: idea or existing codebase → verified PRD → features → rules → sequenced RFCs → reviewed code. Agent Skills for Claude Code, Codex… The licence is MIT.

When your agent uses it

  • Tasks that involve PRD writing

Example prompts

  • “/implement-rfc”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Planning (No Code)
  2. Implementation (After Approval Only)

What it can do on your machine

Read from SKILL.md and the folder at commit 2bc8b29. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implement Rfc loads about 1.3k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 711 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nurettincoban/ai-prd-workflow at commit 2bc8b29, republished under its MIT licence (© nurettincoban). 711 words, ~1,316 tokens.

Download SKILL.mdSave it as .claude/skills/implement-rfc/SKILL.md (or your agent's skills folder).
name
implement-rfc
description
Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every acceptance criterion.
argument-hint
<rfc-id>
metadata.source
https://github.com/nurettincoban/ai-prd-workflow
metadata.version
3.0.0
metadata.checksum
sha256:dc0f22ae8eebf9590cb4b8fd781b9583f32d58b34477aefa1bc8bba13fa214f7

Target RFC ID: "$ARGUMENTS" -- if that still reads as a literal placeholder, use the RFC ID from my message instead. Substitute it for [ID] everywhere below. If no ID was given, ask which RFC to work on before doing anything else.

Implement RFC-[ID]

Role and Mindset

You are a senior software developer. Approach this implementation with:

  1. Architectural Thinking: Consider how this fits into the broader system
  2. Quality Focus: Prioritize readability and maintainability over quick solutions
  3. Pragmatism: Balance best practices with practical considerations
  4. Defensive Programming: Anticipate edge cases and potential failures

Context

This implementation covers RFC-[ID]. Refer to:

  • PRD.md for overall product requirements
  • FEATURES.md for detailed feature specifications
  • RULES.md for project guidelines and standards
  • The RFC itself, RFCs/RFC-[ID]-*.md, for the specific requirements being implemented
  • RFCS.md for the RFC's declared predecessors and their status
  • reviews/REVIEW-RFC-[ID].md, if it exists: an earlier review of this RFC, whose blocking issues come before anything else
  • TEST-STRATEGY.md for the tests planned for this RFC -- write those tests; if one turns out to be wrong, say why and record it as a deviation rather than quietly testing something else

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.

Two-Phase Approach

Phase 1: Planning (No Code)
  1. Check the RFC's declared predecessors. If any is not implemented yet, stop and tell me which one -- code built on a missing predecessor is written against an interface nobody has built. Continue only if I explicitly tell you to
  2. Analyze the requirements and existing codebase
  3. Present a comprehensive implementation plan covering:
    • Files to create or modify
    • Key components, data structures, and APIs
    • Proposed implementation sequence
    • Technical decisions and trade-offs
    • Potential impacts on existing functionality
  4. Wait for explicit user approval before proceeding
  5. Address any feedback or modifications from the user
Phase 2: Implementation (After Approval Only)

Set this RFC's Status in RFCS.md to In progress when you start.

  1. Follow the approved plan. Record every deviation from the RFC or the plan in the RFC file itself, under a final ## Implementation Notes section: what changed, why, and whether I approved it. The reviewer works in a fresh session from the files alone -- a deviation explained only in chat is indistinguishable from a bug
  2. Implement in logical segments as outlined
  3. Explain your approach for complex sections
  4. Self-review before finalizing
Show full SKILL.md (278 more words)Show less

Implementation Standards

  1. Follow all conventions in RULES.md
  2. Do not create workarounds. If you encounter a challenge: a. Explain the challenge clearly b. Propose a proper architectural solution c. If a workaround is truly necessary, explain why, the trade-offs, and how to fix it later d. Flag workarounds with WORKAROUND: [explanation] in comments e. Never implement a workaround without user approval
  3. Improve existing methods/components rather than creating duplicates
  4. Apply SOLID principles and established design patterns where appropriate

Problem Solving

When making design decisions on complex problems:

  1. Explain alternative approaches considered with pros/cons
  2. Make recommendations based on best practices, not expediency
  3. Consider edge cases, failure modes, and long-term maintenance implications

Scope Limitation

Only implement features in this RFC. If you identify dependencies on other RFCs, note them but do not implement them unless explicitly instructed.

Final Deliverables

  1. All code changes necessary to implement the RFC
  2. Necessary tests per the project's testing standards
  3. Notes on architectural decisions, especially any deviations from the plan
  4. Potential improvements or scaling considerations for the future
  5. STATUS -- set this RFC's Status in RFCS.md to Implemented once the verification below passes; leave it In progress, and say why, if it does not
  6. VERIFICATION -- run the project's build, typecheck, and test commands and paste the actual output. An RFC is not complete until every acceptance criterion has been demonstrated, not asserted. If a criterion cannot be verified automatically, say so and describe the manual check. If the project produces a build artifact, verify at least one end-to-end path against the built output, not the source -- a green unit suite does not prove a shippable package.

© nurettincoban, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/implement-rfc of nurettincoban/ai-prd-workflow.

Open the folder on GitHubat commit 2bc8b29

Compare with similar skills

Implement Rfc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Implement Rfc compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implement Rfc this skillnurettincoban/ai-prd-workflow298—~1.3kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Trellis Brainstormanjiemo/SunnyBeach1787 repos~4kAutomated safety check: PassApache-2.0
Adversarial Speczscole/adversarial-spec5561 repos~8.3kAutomated safety check: NotesMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Trellis Brainstorm

    anjiemo/SunnyBeach

    Guides collaborative requirements discovery before implementation.

    178 GitHub starsUsed in 7 repos~4k tokens
    Product & Project ManagementAuto-check passed

  • Adversarial Spec

    zscole/adversarial-spec

    Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree.

    556 GitHub starsUsed in 1 repo~8.3k tokens
    Product & Project ManagementAuto-check: notes

  • Ralph Tui Create Beads Rust

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub starsUsed in 1 repo~5.7k tokens
    Product & Project ManagementAuto-check passed

More from nurettincoban/ai-prd-workflow

All 11 skills in this repo

  • Generate Rfcs

    nurettincoban/ai-prd-workflow

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

    298 GitHub stars~2.1k tokensUpdated 7 days ago
    Auto-check passed

  • Workflow Status

    nurettincoban/ai-prd-workflow

    Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.

    298 GitHub stars~994 tokensUpdated 7 days ago
    Auto-check passed

  • Document Existing

    nurettincoban/ai-prd-workflow

    Document an existing codebase as PRD.md, FEATURES.md and RULES.md, so new work is planned against the code as it is.

    298 GitHub stars~1.6k tokensUpdated 7 days ago
    Auto-check passed

  • Generate Rules

    nurettincoban/ai-prd-workflow

    Write RULES.md, the project standards the AI must follow, with registry-verified dependency versions and permanent rule IDs.

    298 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed

  • Test Strategy

    nurettincoban/ai-prd-workflow

    Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.

    298 GitHub stars~1.4k tokensUpdated 7 days ago
    Auto-check passed

  • Verify Prd

    nurettincoban/ai-prd-workflow

    Review PRD.md for gaps, contradictions and unverifiable claims, write an improved PRD.md and record the findings in PRD-REVIEW.md.

    298 GitHub stars~1.9k tokensUpdated 7 days ago
    Auto-check passed

Categories

Questions about Implement Rfc

What does Implement Rfc do?

Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every acceptance criterion. Implement Rfc is an agent skill from nurettincoban/ai-prd-workflow. Implement one RFC: check its predecessors, present a plan for approval, write the code, then demonstrate every acceptance criterion.

When should I use Implement Rfc?

Implement Rfc fits situations like: tasks that involve PRD writing.

How do I install Implement Rfc in Claude Code?

Run `npx skills add nurettincoban/ai-prd-workflow --skill implement-rfc -a claude-code`. Or copy the skill folder (skills/implement-rfc in nurettincoban/ai-prd-workflow) into .claude/skills/implement-rfc in your project. Claude Code loads it when a task matches its description.

How do I install Implement Rfc in Codex?

Run `npx skills add nurettincoban/ai-prd-workflow --skill implement-rfc -a codex`. Or copy the skill folder (skills/implement-rfc in nurettincoban/ai-prd-workflow) into .agents/skills/implement-rfc in your project. Codex loads it when a task matches its description.

Can I use Implement Rfc in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nurettincoban/ai-prd-workflow --skill implement-rfc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implement-rfc, .gemini/skills/implement-rfc, .github/skills/implement-rfc and .opencode/skills/implement-rfc in your project.

What does Implement Rfc need to run?

SKILL.md names no scripts, command-line tools or credentials: Implement Rfc is instructions for the agent only.

Does Implement Rfc access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Implement Rfc safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Implement Rfc use?

Implement Rfc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implement Rfc use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Implement Rfc?

Skills that share tags, products or a category with Implement Rfc: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Adversarial Spec (zscole/adversarial-spec, 556 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implement Rfc?

nurettincoban (a GitHub user) maintains it in nurettincoban/ai-prd-workflow, which has 298 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 1, 2026.

Source: nurettincoban/ai-prd-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.