Refining Requirements
Turn a vague app idea or an incomplete spec into a signed-off, implementation-ready requirements document through repeated rounds of structured questioning, acting as the PdM while the user plays the client. Each round also scrutinizes the draft — contradictions, missing flows, unstated edge cases, MVP bloat, conflicts with the template or stack — and turns what it finds into the next questions, until the user signs off. Produces features with concrete values, an explicit MVP / Later / Non-goals split, and cross-cutting rules. Use when asked to refine or detail a spec, PRD, or app idea, when s
Install
/plugin marketplace add tomada1114/tomada-claude-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tomada1114/tomada-claude-plugins --skill refining-requirementsgit clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/refining-requirements ~/.claude/skills/refining-requirementsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Refining Requirements
**Next:** `designing-wireframes` for screens and flows, `ui-ux-designing` for app-wide UX
policy, then `planning-tickets` for issues — or all of it through `kicking-off-apps`.
## Modes and output
- **Hearing** — the input is an idea in the user's words ("an app that…"). Build the
document from nothing; the user answers as a client who knows the problem but not
the spec.
- **Refinement** — the input is an existing document. Ask only what it leaves unclear.
Write to the path the caller names (`--out`, or the path `kicking-off-apps` passes);
otherwise update an existing requirements document in place; otherwise create
`docs/product/requirements.md`. Structure: [templates/requirements-document.md](templates/requirements-document.md),
one section per feature from [templates/requirements-section.md](templates/requirements-section.md).
## Before the first question
Read what already constrains the answer: the repository's or template's `AGENTS.md` /
`CLAUDE.md` and `README.md`. A template fixes the platform and stack, and its sample
shows what the app is built from — do not ask about anything they settle, and keep the
constraints in mind as scrutiny material ("this feature needs a server; the template is
local-only").
Classify the platform — desktop (macOS), web, mobile, API/backend, CLI — because it
decides which question rounds apply ([references/question-bank.md](references/question-bank.md)).
## The loop
Repeat until the user signs off:Details
- Skill name
refining-requirements- Repository
- tomada1114/tomada-claude-plugins
- Path
tomada-kit/skills/refining-requirements/SKILL.md- Repo updated
- 12 November 2026
FAQ
What does the Refining Requirements skill do?
Turn a vague app idea or an incomplete spec into a signed-off, implementation-ready requirements document through repeated rounds of structured questioning, acting as the PdM while the user plays the client. Each round also scrutinizes the draft — contradictions, missing flows, unstated edge cases, MVP bloat, conflicts with the template or stack — and turns what it finds into the next questions, until the user signs off. Produces features with concrete values, an explicit MVP / Later / Non-goals split, and cross-cutting rules. Use when asked to refine or detail a spec, PRD, or app idea, when s
How do I install the Refining Requirements skill?
Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Refining Requirements popular?
It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.
Related skills
Auditing Prompt Docs
5tomada1114/tomada-claude-plugins
Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m
Auditing Repositories
5tomada1114/tomada-claude-plugins
Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst
Authoring Goal Prompts
5tomada1114/tomada-claude-plugins
Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de
Add to Cart
9Lord1Egypt/RA-Skills
Find a product on kmart.com.au by natural-language query, navigate to the product detail page, capture title/price/SKU/availability, and drive the read-only pre-checkout flow up to the bag (/checkout/bag). Never submits an order — stops at the bag review screen. Documents the …
Presentify
5Magnus-Gille/claude-skills
Create a self-contained HTML one-page briefing from supplied material.
Amazon Global Prices
9Lord1Egypt/RA-Skills
Compare an Amazon product price across multiple country storefronts by routing each Browserbase session through that country's geolocation proxy, then extract country, currency, price, title, and URL with a Stagehand/Zod schema. Read-only.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.