Enrichment
eser/stack
Interviews the user about a plan, decision or idea in rounds, level by level down a decision tree, until both share one understanding; facts are researched by sub-agents, decisions stay with the user.
A skill your agent uses when designing, drafting, refining, or stress-testing an RFC for an approved PRD, including requests for a design doc, solution design, or how to build it.
Install Rfc Modeling
$ npx skills add mirumee/nimara-ecommerce --skill rfc-modeling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mirumee/nimara-ecommerce rfc-modeling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .claude/skills && cp -r skills-src/llm-wiki/.claude/skills/rfc-modeling .claude/skills/rfc-modeling && rm -rf skills-srcUse ~/.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/
Install the "rfc-modeling" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/llm-wiki/.claude/skills/rfc-modeling into .claude/skills/rfc-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfc-modeling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mirumee/nimara-ecommerce/tree/main/llm-wiki/.claude/skills/rfc-modelingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mirumee/nimara-ecommerce --skill rfc-modeling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mirumee/nimara-ecommerce rfc-modeling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .agents/skills && cp -r skills-src/llm-wiki/.claude/skills/rfc-modeling .agents/skills/rfc-modeling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rfc-modeling" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/llm-wiki/.claude/skills/rfc-modeling into .agents/skills/rfc-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfc-modeling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mirumee/nimara-ecommerce --skill rfc-modeling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mirumee/nimara-ecommerce rfc-modeling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/llm-wiki/.claude/skills/rfc-modeling .cursor/skills/rfc-modeling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rfc-modeling" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/llm-wiki/.claude/skills/rfc-modeling into .cursor/skills/rfc-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfc-modeling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mirumee/nimara-ecommerce.git --path llm-wiki/.claude/skills/rfc-modeling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mirumee/nimara-ecommerce --skill rfc-modeling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mirumee/nimara-ecommerce rfc-modeling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/llm-wiki/.claude/skills/rfc-modeling .gemini/skills/rfc-modeling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rfc-modeling" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/llm-wiki/.claude/skills/rfc-modeling into .gemini/skills/rfc-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfc-modeling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mirumee/nimara-ecommerce rfc-modelingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mirumee/nimara-ecommerce --skill rfc-modeling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .github/skills && cp -r skills-src/llm-wiki/.claude/skills/rfc-modeling .github/skills/rfc-modeling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rfc-modeling" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/llm-wiki/.claude/skills/rfc-modeling into .github/skills/rfc-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfc-modeling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mirumee/nimara-ecommerce --skill rfc-modeling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mirumee/nimara-ecommerce rfc-modeling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mirumee/nimara-ecommerce.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/llm-wiki/.claude/skills/rfc-modeling .opencode/skills/rfc-modeling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rfc-modeling" agent skill from https://github.com/mirumee/nimara-ecommerce/tree/main/llm-wiki/.claude/skills/rfc-modeling into .opencode/skills/rfc-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfc-modeling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rfc-modeling- GitHub stars
- 129
- Token cost
- ~920 tokens
- SKILL.md length
- 524 words
- Files
- 4 (incl. references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
A skill your agent uses when designing, drafting, refining, or stress-testing an RFC for an approved PRD, including requests for a design doc, solution design, or how to build it.
- Works in 5 steps: Resolve the PRD and pull context → Run technical grilling - use proper… → Draft the RFC → …
- Stress-testing an RFC for an approved PRD
- SKILL.md covers Altitude: a proposal, not an…, Stage 1 - Resolve the PRD and…, Stage 2 - Run technical… and Stage 3 — Draft the RFC, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rfc Modeling is an agent skill from mirumee/nimara-ecommerce. Use when designing, drafting, refining, or stress-testing an RFC for an approved PRD, including requests for a design doc, solution design, or how to build it.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/quality-checklist.md`, `references/rfc-template.md` and `references/technical-protocol.md`).
It sits in Product & Project Management, covering PRD writing, Architecture decision records and Load testing. It works with shadcn/ui. The repository describes itself as: Headless, composable ecommerce storefront built with Next.js, Typescript, and shadcn/ui. The licence is BSD-3-Clause.
When your agent uses it
- Stress-testing an RFC for an approved PRD
- Including requests for a design doc
- Solution design
- How to build it
Example prompts
- “/rfc-modeling”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c2ad30b. 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
Rfc Modeling loads about 920 tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 43 tokens; SKILL.md has 524 words of instructions outside code blocks.
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 mirumee/nimara-ecommerce at commit c2ad30b, republished under its BSD-3-Clause licence (© mirumee). 524 words, ~920 tokens.
Download SKILL.mdSave it as
.claude/skills/rfc-modeling/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- rfc-modeling
- description
- Use when designing, drafting, refining, or stress-testing an RFC for an approved PRD, including requests for a design doc, solution design, or how to build it.
RFC modeling
Follow these stages in order. The technical grilling, and the self-lint are mandatory.
Altitude: a proposal, not an implementation plan
An RFC proposes a solution. It is not an implementation plan.
Describe the shape of the solution:
- the architectural principles that hold the design up: what layers over what, which boundaries are swappable, and the dependency direction.
- the key decisions.
- the implementation gotchas and the risks that can sink the design.
Do not specify exact package or folder paths, file or function names, type signatures, or line-level structure. Those belong in implementation tickets and pull requests. Package placement can appear once, as a one-line suggestion that does not bind the implementer.
If a detail is doubtful, ask one question: does a reviewer need this detail to judge the approach? If the answer is no, the detail sits too low. It constrains the implementer and it earns nothing.
Stage 1 - Resolve the PRD and pull context
An RFC is always anchored to one PRD. Resolve it first.
- If the user named a PRD, load it.
- If the user named no PRD, list the PRDs under
llm-wiki/prd/and ask the user to pick one. Do not invent a PRD. Do not design against a loose feature idea, because an RFC without a PRD has nothing to be falsified against.
Then read the following, before you question the user:
- the PRD, and especially its business bet, its deferred technical decisions, and its open questions.
- the relevant personas, strategy notes, and market notes.
- the existing ADRs and RFCs that overlap or constrain this design.
- the code and the infrastructure the design touches: packages, layers, services, schema, and config.
Use repository and source exploration to answer factual questions. Facts belong to exploration. Decisions belong to the user. Never invent a constraint, a current behavior, or a capability.
Completion criterion: the PRD is fixed, the deferred technical branches are collected, and you understand the affected code and infrastructure before research begins.
Show full SKILL.md (197 more words)Show less
Stage 2 - Run technical grilling - use proper languages
Run a /llm-wiki:grilling session that which does not go beyond the scope of the RFC definition.
If a problem is complex use /llm-wiki:show-me skill so that the questions are easy for the user to understand. A diagram with a description settles a structural question faster than a paragraph.
Read references/technical-protocol.md and follow it completely.
Adjust your language so that it is as easy to understand as possible for the person you're grilling.
Stage 3 — Draft the RFC
Read references/rfc-template.md. Follow the wiki's local schema and link convention.
Stage 4 - Self-lint
Run every check in references/quality-checklist.md. Fix the issues that need no new decision. Put the genuine unknowns in the deferred items. Report every failed check instead of hiding it.
Completion criterion: every checklist item passes, or it is reported as an explicit gap with an owner.
Stage 5 - Gate
A new RFC starts as status: draft. A rewritten RFC changes status only when the user approves the transition explicitly: draft to in_review to final.
References
references/technical-protocol.md- the mandatory sequential design interview and its completion gate.references/quality-checklist.md- the Definition of Ready for an RFC.references/rfc-template.mdthe canonical RFC template structure.
© mirumee, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in llm-wiki/.claude/skills/rfc-modeling of mirumee/nimara-ecommerce.
- SKILL.md
- references/quality-checklist.md
- references/rfc-template.md
- references/technical-protocol.md
Open the folder on GitHubat commit c2ad30b
Compare with similar skills
Rfc Modeling 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rfc Modeling this skillmirumee/nimara-ecommerce | 129 | — | ~920 | Automated safety check: Pass | BSD-3-Clause | |
| Enrichmenteser/stack | 128 | — | ~642 | Automated safety check: Pass | Custom licence | |
| Write Update Tidb Docspingcap/docs | 615 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Req Change Workflowyunshu0909/yunshu_skillshub | 767 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Schematicblader/schematic | 240 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Shep Workstreamsshep-ai/shep | 264 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Write Update Tidb Docs
pingcap/docs
Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.
Req Change Workflow
yunshu0909/yunshu_skillshub
已有功能的需求变更闭环（门禁式七步）。触发硬条件：要改的功能已经实现并跑起来了。当用户说"改需求""需求变更""调整交互""改功能""重构流程"，或改动容易散到多个文件、碰到鉴权/存储/配置/权限、需要可靠验证 + 回滚方案时使用。流程：锁 scope 写 change brief → 从代码确认当前行为（不靠记忆和假设）→ 影响面与风险评估 + 回滚计划 →…
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
Shep Workstreams
shep-ai/shep
A skill your agent uses when a large body of work (a version milestone, an epic, a roadmap, a set of PRDs/design docs) needs to be broken into parallel workstreams and executed with the shep CLI.
Grilling Ideas
opsmill/infrahub
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written.
More from mirumee/nimara-ecommerce
All 12 skills in this repoProject Guidelines
mirumee/nimara-ecommerce
Guide for working with Nimara's layered monorepo architecture.
Prd Modeling
mirumee/nimara-ecommerce
A skill your agent uses when creating, rewriting, refining, or stress-testing a Product Requirements Document (PRD), including turning an initiative or feature brief into product requirements.
Ucp Agent
mirumee/nimara-ecommerce
Operate Nimara's UCP REST commerce API. An agent skill from mirumee/nimara-ecommerce.
Show Me
mirumee/nimara-ecommerce
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
Bug Retest Triage
mirumee/nimara-ecommerce
Retest a reported defect on the live Nimara board (Jira project MS, board 74) and give it an evidence-backed verdict — still reproduces → Open, fixed → Done, blocked → leave In testing and ask.
Explore
mirumee/nimara-ecommerce
Ways to explore llm-wiki and answer from it. An agent skill from mirumee/nimara-ecommerce.
Related
Works with
Categories
Questions about Rfc Modeling
What does Rfc Modeling do?
A skill your agent uses when designing, drafting, refining, or stress-testing an RFC for an approved PRD, including requests for a design doc, solution design, or how to build it. Rfc Modeling is an agent skill from mirumee/nimara-ecommerce. Use when designing, drafting, refining, or stress-testing an RFC for an approved PRD, including requests for a design doc, solution design, or how to build it.
When should I use Rfc Modeling?
Rfc Modeling fits situations like: stress-testing an RFC for an approved PRD; including requests for a design doc; solution design; how to build it.
How do I install Rfc Modeling in Claude Code?
Run `npx skills add mirumee/nimara-ecommerce --skill rfc-modeling -a claude-code`. Or copy the skill folder (llm-wiki/.claude/skills/rfc-modeling in mirumee/nimara-ecommerce) into .claude/skills/rfc-modeling in your project. Claude Code loads it when a task matches its description.
How do I install Rfc Modeling in Codex?
Run `npx skills add mirumee/nimara-ecommerce --skill rfc-modeling -a codex`. Or copy the skill folder (llm-wiki/.claude/skills/rfc-modeling in mirumee/nimara-ecommerce) into .agents/skills/rfc-modeling in your project. Codex loads it when a task matches its description.
Can I use Rfc Modeling 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 mirumee/nimara-ecommerce --skill rfc-modeling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rfc-modeling, .gemini/skills/rfc-modeling, .github/skills/rfc-modeling and .opencode/skills/rfc-modeling in your project.
What does Rfc Modeling need to run?
SKILL.md names no scripts, command-line tools or credentials: Rfc Modeling is instructions for the agent only.
Does Rfc Modeling 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 Rfc Modeling 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 Rfc Modeling use?
Rfc Modeling is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rfc Modeling use?
About 920 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.5k tokens, read only when the agent opens those files.
What are the alternatives to Rfc Modeling?
Skills that share tags, products or a category with Rfc Modeling: Enrichment (eser/stack, 128 stars), Write Update Tidb Docs (pingcap/docs, 615 stars), Req Change Workflow (yunshu0909/yunshu_skillshub, 767 stars) and Schematic (blader/schematic, 240 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rfc Modeling?
mirumee (a GitHub organization) maintains it in mirumee/nimara-ecommerce, which has 129 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.
Source: mirumee/nimara-ecommerce on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.