Agent skill

Prd Modeling

by mirumee in 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.

BSD-3-ClauseAuto-check passedProduct & Project Management

Install Prd Modeling

skills CLI
$ npx skills add mirumee/nimara-ecommerce --skill prd-modeling -a claude-code

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

GitHub CLI
$ gh skill install mirumee/nimara-ecommerce prd-modeling --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/mirumee/nimara-ecommerce.git skills-src && mkdir -p .claude/skills && cp -r skills-src/llm-wiki/.claude/skills/prd-modeling .claude/skills/prd-modeling && 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
prd-modeling
GitHub stars
129
Token cost
~824 tokens
SKILL.md length
419 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 creating, rewriting, refining, or stress-testing a Product Requirements Document (PRD), including turning an initiative or feature brief into product requirements.

  • Works in 5 steps: Pull context and facts → Run business grilling - use proper… → Draft the PRD → …
  • Stress-testing a Product Requirements Document (PRD)
  • SKILL.md covers Stage 1 — Pull context and facts, Stage 2 — Run business…, Stage 3 — Draft the PRD and Stage 4 — Self-lint, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prd Modeling is an agent skill from mirumee/nimara-ecommerce. Use when creating, rewriting, refining, or stress-testing a Product Requirements Document (PRD), including turning an initiative or feature brief into product requirements.

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/business-protocol.md`, `references/prd-template.md` and `references/quality-checklist.md`).

It sits in Product & Project Management, covering PRD writing. 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 a Product Requirements Document (PRD)
  • Including turning an initiative
  • Feature brief into product requirements

Example prompts

  • “/prd-modeling”

Workflow steps

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

  1. Pull context and facts
  2. Run business grilling - use proper languages
  3. Draft the PRD
  4. Self-lint
  5. Gate

What it can do on your machine

Read from SKILL.md and the folder at commit b883dec. 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

Prd Modeling loads about 824 tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 419 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~824
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.4k

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 b883dec, republished under its BSD-3-Clause licence (© mirumee). 419 words, ~824 tokens.

Download SKILL.mdSave it as .claude/skills/prd-modeling/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
prd-modeling
description
Use when creating, rewriting, refining, or stress-testing a Product Requirements Document (PRD), including turning an initiative or feature brief into product requirements.

PRD Modeling

Turn an initiative or feature idea into an explicit, falsifiable Product Requirements Document that a human approves before solution design and task breakdown begin.

Follow these stages in order. The business grilling and self-lint are mandatory.

Stage 1 — Pull context and facts

Locate the /llm-wiki root which should contain

  • the current PRD or seeding initiative;
  • relevant personas;
  • market and strategy notes for the problem area;
  • raw sources named by the user;
  • related PRDs that could overlap.

Use repository or source exploration to answer factual questions. Treat sources as evidence, never edit them, and separate what they prove from what is merely inferred. Never invent demand, attribution, metrics, competitor claims, targets, or constraints.

Completion criterion: the known facts, evidence gaps, existing strategic position, and plausible overlap with other PRDs are identified before questioning the user.

Stage 2 — Run business grilling - use proper languages

Run a /llm-wiki:grilling session that which does not go beyond the scope of the PRD definition.

If a problem is complex use /llm-wiki:show-me skill so that the questions are easy for the user to understand

Read references/business-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.

Show full SKILL.md (216 more words)Show less
Completion gate

The grilling is complete only when the shared understanding contains:

  • a specific target segment and personas;
  • a problem statement with evidence separated from assumptions;
  • the PRD's strategic role and urgency;
  • one primary business outcome and its value path;
  • quantified validation evidence or an explicitly accepted lack of a target;
  • leading indicators distinct from business outcomes;
  • a negative falsification result and treatment of insufficient evidence;
  • the smallest learning MVP, rollout, and appetite decision;
  • explicit in-scope and out-of-scope boundaries;
  • business NFRs, ownership, risks, and lifecycle gate;
  • a list of technical decisions deferred to solution design;
  • explicit user confirmation of shared understanding.

Stage 3 — Draft the PRD

Read references/prd-template.md. Follow the schema and link convention.

Stage 4 — Self-lint

Run every check in references/quality-checklist.md. Fix issues that require no new decision. Put genuine unknowns in Open Questions and report any failed checks rather than hiding them.

Completion criterion: every checklist item passes or is reported as an explicit, owned gap.

Stage 5 — Gate

New PRDs start as draft. A rewritten PRD changes status only when the user explicitly approves the transition. Close with the PRD file location, passed checks, open decisions, stale downstream artifacts, and proposed next lifecycle step.

References

  • references/business-protocol.md — mandatory sequential business interview and completion gate.
  • references/prd-template.md — canonical PRD structure.
  • references/quality-checklist.md — Definition of Ready for review.

© 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/prd-modeling of mirumee/nimara-ecommerce.

  • SKILL.md
  • references/business-protocol.md
  • references/prd-template.md
  • references/quality-checklist.md

Open the folder on GitHubat commit b883dec

Compare with similar skills

Prd 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.

Prd Modeling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prd Modeling this skillmirumee/nimara-ecommerce129—~824Automated safety check: PassBSD-3-Clause
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated 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

Similar skills

  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed
  • 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
  • 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

More from mirumee/nimara-ecommerce

All 12 skills in this repo
  • Project Guidelines

    mirumee/nimara-ecommerce

    Guide for working with Nimara's layered monorepo architecture.

    129 GitHub stars~4.8k tokensUpdated 2 days ago
    Auto-check passed
  • Rfc Modeling

    mirumee/nimara-ecommerce

    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.

    129 GitHub stars~920 tokensUpdated 2 days ago
    Auto-check passed
  • Ucp Agent

    mirumee/nimara-ecommerce

    Operate Nimara's UCP REST commerce API. An agent skill from mirumee/nimara-ecommerce.

    129 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed
  • Show Me

    mirumee/nimara-ecommerce

    Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

    129 GitHub starsUsed in 7 repos~809 tokens
    Auto-check passed
  • 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.

    129 GitHub stars~888 tokensUpdated 2 days ago
    Auto-check passed
  • Explore

    mirumee/nimara-ecommerce

    Ways to explore llm-wiki and answer from it. An agent skill from mirumee/nimara-ecommerce.

    129 GitHub stars~436 tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Prd Modeling

What does Prd Modeling do?

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. Prd Modeling is an agent skill from mirumee/nimara-ecommerce. Use when creating, rewriting, refining, or stress-testing a Product Requirements Document (PRD), including turning an initiative or feature brief into product requirements.

When should I use Prd Modeling?

Prd Modeling fits situations like: stress-testing a Product Requirements Document (PRD); including turning an initiative; feature brief into product requirements.

How do I install Prd Modeling in Claude Code?

Run `npx skills add mirumee/nimara-ecommerce --skill prd-modeling -a claude-code`. Or copy the skill folder (llm-wiki/.claude/skills/prd-modeling in mirumee/nimara-ecommerce) into .claude/skills/prd-modeling in your project. Claude Code loads it when a task matches its description.

How do I install Prd Modeling in Codex?

Run `npx skills add mirumee/nimara-ecommerce --skill prd-modeling -a codex`. Or copy the skill folder (llm-wiki/.claude/skills/prd-modeling in mirumee/nimara-ecommerce) into .agents/skills/prd-modeling in your project. Codex loads it when a task matches its description.

Can I use Prd 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 prd-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/prd-modeling, .gemini/skills/prd-modeling, .github/skills/prd-modeling and .opencode/skills/prd-modeling in your project.

What does Prd Modeling need to run?

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

Does Prd 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 Prd 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 Prd Modeling use?

Prd 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 Prd Modeling use?

About 824 tokens (SKILL.md is roughly 3.3k 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 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Prd Modeling?

Skills that share tags, products or a category with Prd Modeling: Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars) and Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd 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 6, 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.