Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
Clarify ambiguous requirements through focused dialogue before implementation.
Install Requirements Clarity
$ npx skills add pedronauck/skills --skill requirements-clarity -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pedronauck/skills requirements-clarity --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/pedronauck/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/curated/requirements-clarity .claude/skills/requirements-clarity && 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 "requirements-clarity" agent skill from https://github.com/pedronauck/skills/tree/main/skills/curated/requirements-clarity into .claude/skills/requirements-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarity", 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/pedronauck/skills/tree/main/skills/curated/requirements-clarityType 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 pedronauck/skills --skill requirements-clarity -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pedronauck/skills requirements-clarity --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/curated/requirements-clarity .agents/skills/requirements-clarity && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "requirements-clarity" agent skill from https://github.com/pedronauck/skills/tree/main/skills/curated/requirements-clarity into .agents/skills/requirements-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarity", 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 pedronauck/skills --skill requirements-clarity -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pedronauck/skills requirements-clarity --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/curated/requirements-clarity .cursor/skills/requirements-clarity && 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 "requirements-clarity" agent skill from https://github.com/pedronauck/skills/tree/main/skills/curated/requirements-clarity into .cursor/skills/requirements-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarity", 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/pedronauck/skills.git --path skills/curated/requirements-clarity--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 pedronauck/skills --skill requirements-clarity -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pedronauck/skills requirements-clarity --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/curated/requirements-clarity .gemini/skills/requirements-clarity && 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 "requirements-clarity" agent skill from https://github.com/pedronauck/skills/tree/main/skills/curated/requirements-clarity into .gemini/skills/requirements-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarity", 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 pedronauck/skills requirements-clarityInstalls 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 pedronauck/skills --skill requirements-clarity -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/curated/requirements-clarity .github/skills/requirements-clarity && 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 "requirements-clarity" agent skill from https://github.com/pedronauck/skills/tree/main/skills/curated/requirements-clarity into .github/skills/requirements-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarity", 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 pedronauck/skills --skill requirements-clarity -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pedronauck/skills requirements-clarity --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pedronauck/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/curated/requirements-clarity .opencode/skills/requirements-clarity && 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 "requirements-clarity" agent skill from https://github.com/pedronauck/skills/tree/main/skills/curated/requirements-clarity into .opencode/skills/requirements-clarity/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "requirements-clarity", 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
requirements-clarity- GitHub stars
- 634
- Used in
- 2 other repos
- Token cost
- ~2.3k tokens
- SKILL.md length
- 530 words
- Files
- 2
- Skills in repo
- 65
- Repo updated
- First seen
- Licence
- None found
At a glance
Clarify ambiguous requirements through focused dialogue before implementation.
- Works in 4 steps: Initial Requirement Analysis → Gap Analysis → Interactive Clarification → …
- Requirements are unclear
- SKILL.md covers Description, Instructions, Core Principles and Clarification Process, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Requirements Clarity is an agent skill from pedronauck/skills. Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Product & Project Management, covering Requirements gathering and PRD writing. The repository describes itself as: My personal favorite skills.
When your agent uses it
- Requirements are unclear
- Features are complex (2 days)
- Involve cross-team coordination
Example prompts
- “/requirements-clarity”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Initial Requirement Analysis
- Gap Analysis
- Interactive Clarification
- PRD Generation
What it can do on your machine
Read from SKILL.md and the folder at commit 0422940. 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 (its code samples are markdown).
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
Requirements Clarity loads about 2.3k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 530 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 530 words (~2,325 tokens).
“Automatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system.”
- name
- requirements-clarity
Files
SKILL.md and 1 other file in skills/curated/requirements-clarity of pedronauck/skills.
- SKILL.md
- README.md
Open the folder on GitHubat commit 0422940
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in pedronauck/skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Requirements Clarity 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 |
|---|---|---|---|---|---|---|
| Requirements Clarity this skillpedronauck/skills | 634 | 2 repos | ~2.3k | Automated safety check: Pass | None | |
| Ouroboros PM InterviewQ00/ouroboros | 6.2k | — | ~5.7k | Automated safety check: Pass | MIT | |
| User Alignment and Agent-Ready PRDstryproduck/produck-skills | 511 | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| Creating Issuesopsmill/infrahub | 534 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Grilling Ideasopsmill/infrahub | 534 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Feature ForgeJeffallan/claude-skills | 12k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
User Alignment and Agent-Ready PRDs
tryproduck/produck-skills
Turns a vague feature request into a written spec with scope, phases, acceptance criteria and do-not-do limits that a coding agent can follow without guessing.
Creating Issues
opsmill/infrahub
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.
Grilling Ideas
opsmill/infrahub
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written.
Feature Forge
Jeffallan/claude-skills
Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.
Tech Design
open-octo/octo-agent
Produce a complete backend technical design document from a PRD or feature description — understand, explore the codebase, grill on decisions, write, and self-review.
More from pedronauck/skills
All 65 skills in this repoDeep Review
pedronauck/skills
Review branch diffs, working trees, or PRs in depth with defect, polish and cross-contract coverage.
Yc Apply
pedronauck/skills
Prepare, review, and package Y Combinator application answers and founder-video notes using the live form and verified founder facts.
Professional Communication
pedronauck/skills
Guide technical communication for software developers. An agent skill from pedronauck/skills.
Tauri V2
pedronauck/skills
Tauri v2+ cross-platform app development with Rust backend. An agent skill from pedronauck/skills.
Hormozi Ad Factory
pedronauck/skills
Generates 150-750+ ad variations using Alex Hormozi's combinatorial Hook x Meat x CTA framework.
Yt Master
pedronauck/skills
Plans and improves YouTube ideas, titles, thumbnail concepts, scripts, retention, channel strategy, and metric-based diagnosis.
Related
Questions about Requirements Clarity
What does Requirements Clarity do?
Clarify ambiguous requirements through focused dialogue before implementation. Requirements Clarity is an agent skill from pedronauck/skills. Clarify ambiguous requirements through focused dialogue before implementation.
When should I use Requirements Clarity?
Requirements Clarity fits situations like: requirements are unclear; features are complex (2 days); involve cross-team coordination.
How do I install Requirements Clarity in Claude Code?
Run `npx skills add pedronauck/skills --skill requirements-clarity -a claude-code`. Or copy the skill folder (skills/curated/requirements-clarity in pedronauck/skills) into .claude/skills/requirements-clarity in your project. Claude Code loads it when a task matches its description.
How do I install Requirements Clarity in Codex?
Run `npx skills add pedronauck/skills --skill requirements-clarity -a codex`. Or copy the skill folder (skills/curated/requirements-clarity in pedronauck/skills) into .agents/skills/requirements-clarity in your project. Codex loads it when a task matches its description.
Can I use Requirements Clarity 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 pedronauck/skills --skill requirements-clarity -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/requirements-clarity, .gemini/skills/requirements-clarity, .github/skills/requirements-clarity and .opencode/skills/requirements-clarity in your project.
What does Requirements Clarity need to run?
SKILL.md names no scripts, command-line tools or credentials: Requirements Clarity is instructions for the agent only.
Does Requirements Clarity 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 Requirements Clarity 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 Requirements Clarity use?
No licence was found for Requirements Clarity or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Requirements Clarity use?
About 2.3k tokens (SKILL.md is roughly 9.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 Requirements Clarity?
Skills that share tags, products or a category with Requirements Clarity: Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), User Alignment and Agent-Ready PRDs (tryproduck/produck-skills, 511 stars), Creating Issues (opsmill/infrahub, 534 stars) and Grilling Ideas (opsmill/infrahub, 534 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Requirements Clarity?
pedronauck (a GitHub user) maintains it in pedronauck/skills, which has 634 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on September 14, 2026.
Source: pedronauck/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.