Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Validates PRD, user stories, or feature requirements against SMART criteria.
Install Vibe Requirements Validator
$ npx skills add ash1794/vibe-engineering --skill vibe-requirements-validator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ash1794/vibe-engineering vibe-requirements-validator --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/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-requirements-validator .claude/skills/vibe-requirements-validator && 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 "vibe-requirements-validator" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-requirements-validator into .claude/skills/vibe-requirements-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-requirements-validator", 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/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-requirements-validatorType 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 ash1794/vibe-engineering --skill vibe-requirements-validator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ash1794/vibe-engineering vibe-requirements-validator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-requirements-validator .agents/skills/vibe-requirements-validator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-requirements-validator" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-requirements-validator into .agents/skills/vibe-requirements-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-requirements-validator", 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 ash1794/vibe-engineering --skill vibe-requirements-validator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ash1794/vibe-engineering vibe-requirements-validator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-requirements-validator .cursor/skills/vibe-requirements-validator && 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 "vibe-requirements-validator" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-requirements-validator into .cursor/skills/vibe-requirements-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-requirements-validator", 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/ash1794/vibe-engineering.git --path plugins/vibe-engineering/skills/vibe-requirements-validator--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 ash1794/vibe-engineering --skill vibe-requirements-validator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ash1794/vibe-engineering vibe-requirements-validator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-requirements-validator .gemini/skills/vibe-requirements-validator && 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 "vibe-requirements-validator" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-requirements-validator into .gemini/skills/vibe-requirements-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-requirements-validator", 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 ash1794/vibe-engineering vibe-requirements-validatorInstalls 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 ash1794/vibe-engineering --skill vibe-requirements-validator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-requirements-validator .github/skills/vibe-requirements-validator && 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 "vibe-requirements-validator" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-requirements-validator into .github/skills/vibe-requirements-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-requirements-validator", 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 ash1794/vibe-engineering --skill vibe-requirements-validator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ash1794/vibe-engineering vibe-requirements-validator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-requirements-validator .opencode/skills/vibe-requirements-validator && 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 "vibe-requirements-validator" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-requirements-validator into .opencode/skills/vibe-requirements-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-requirements-validator", 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
vibe-requirements-validator- GitHub stars
- 163
- Token cost
- ~558 tokens
- SKILL.md length
- 257 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Validates PRD, user stories, or feature requirements against SMART criteria.
- Works in 4 steps: List all requirements from the document → Score each on SMART (1-5 per dimension) → Flag issues → …
- Reviewing requirements to catch vagueness before it causes expensive rework
- SKILL.md covers When to Use This Skill, When NOT to Use This Skill, SMART Criteria and Steps, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vibe Requirements Validator is an agent skill from ash1794/vibe-engineering. Validates PRD, user stories, or feature requirements against SMART criteria. Use when reviewing requirements to catch vagueness before it causes expensive rework.
Its SKILL.md is about 560 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 User stories and PRD writing. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.
When your agent uses it
- Reviewing requirements to catch vagueness before it causes expensive rework
- Tasks that involve User stories
- Tasks that involve PRD writing
Example prompts
- “Use the vibe-requirements-validator skill to validate PRD, user stories, or feature requirements against SMART criteria”
- “/vibe-requirements-validator”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- List all requirements from the document
- Score each on SMART (1-5 per dimension)
- Flag issues
- Report
What it can do on your machine
Read from SKILL.md and the folder at commit 8f1d71b. 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
Vibe Requirements Validator loads about 558 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 257 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 ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 257 words, ~558 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-requirements-validator/SKILL.md (or your agent's skills folder).- name
- vibe-requirements-validator
- description
- Validates PRD, user stories, or feature requirements against SMART criteria. Use when reviewing requirements to catch vagueness before it causes expensive rework.
- user-invocable
- true
vibe-requirements-validator
Vague requirements cause expensive rework. Catch them early.
When to Use This Skill
- Reviewing a PRD or feature spec before implementation
- Writing acceptance criteria for user stories
- When you notice requirements like "make it fast" or "improve UX"
- Before estimating effort for a feature
When NOT to Use This Skill
- Internal technical tasks with clear scope
- Bug fixes (the bug IS the requirement)
- When requirements are already validated and approved
SMART Criteria
Score each requirement 1-5 on:
- Specific — Is it clear what exactly needs to be built? (Not "improve performance" but "reduce P95 latency to <200ms")
- Measurable — Can you objectively verify it's done? (Not "users like it" but "NPS score >40")
- Achievable — Can it be built with available resources and constraints?
- Relevant — Does it align with project goals and user needs?
- Time-bound — Is there a clear scope boundary? (Not "eventually" but "in v1.0")
Steps
List all requirements from the document
Score each on SMART (1-5 per dimension)
Flag issues:
- Score < 3 on any dimension → needs revision
- Measurability < 3 → most common failure, flag prominently
- Near-duplicates → consolidate
- Positioning statements masquerading as requirements → remove
Report:
Output Format
Requirements Validation: [Document Name]
Total Requirements: X Passing (avg >= 3.5): Y (Z%) Flagged: W
| ID | Requirement | S | M | A | R | T | Avg | Issue |
|---|---|---|---|---|---|---|---|---|
| FR-1 | "..." | 4 | 2 | 5 | 4 | 3 | 3.6 | Low measurability |
Top Issues
- Measurability crisis — X requirements have M < 3
- Near-duplicates — [list pairs]
- Not requirements — [positioning statements]
Recommended Revisions
| ID | Current | Suggested |
|---|---|---|
| FR-3 | "Improve load time" | "Reduce initial page load to <2s on 3G" |
© ash1794, 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 plugins/vibe-engineering/skills/vibe-requirements-validator of ash1794/vibe-engineering.
Open the folder on GitHubat commit 8f1d71b
Compare with similar skills
Vibe Requirements Validator 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 |
|---|---|---|---|---|---|---|
| Vibe Requirements Validator this skillash1794/vibe-engineering | 163 | — | ~558 | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| To Prdywwynm/EverythingDone | 144 | 11 repos | ~777 | Automated safety check: Pass | GPL-3.0 | |
| Use Case Writerphucnt-bazone-vietnam/use-case-writer | 143 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
To Prd
ywwynm/EverythingDone
Turn the current conversation context into a PRD and publish it to the project issue tracker.
Use Case Writer
phucnt-bazone-vietnam/use-case-writer
Generate Use Case specifications in English Markdown following the IT BA standard 13-field template (Karl Wiegers / IIBA).
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
More from ash1794/vibe-engineering
All 33 skills in this repoVibe Concurrent Test Safety
ash1794/vibe-engineering
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.
Vibe Fuzz Parser Inputs
ash1794/vibe-engineering
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).
Vibe Golden File Testing
ash1794/vibe-engineering
Implements snapshot/golden file tests with temporal normalization so tests don't break daily.
Vibe Parallel Task Decomposition
ash1794/vibe-engineering
Analyzes large tasks for independent subtasks that can be safely parallelized.
Vibe Slop Filter
ash1794/vibe-engineering
Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).
Vibe Spec Sync
ash1794/vibe-engineering
Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.
Related
Categories
Questions about Vibe Requirements Validator
What does Vibe Requirements Validator do?
Validates PRD, user stories, or feature requirements against SMART criteria. Vibe Requirements Validator is an agent skill from ash1794/vibe-engineering. Validates PRD, user stories, or feature requirements against SMART criteria.
When should I use Vibe Requirements Validator?
Vibe Requirements Validator fits situations like: reviewing requirements to catch vagueness before it causes expensive rework; tasks that involve User stories; tasks that involve PRD writing.
How do I install Vibe Requirements Validator in Claude Code?
Run `npx skills add ash1794/vibe-engineering --skill vibe-requirements-validator -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-requirements-validator in ash1794/vibe-engineering) into .claude/skills/vibe-requirements-validator in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Requirements Validator in Codex?
Run `npx skills add ash1794/vibe-engineering --skill vibe-requirements-validator -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-requirements-validator in ash1794/vibe-engineering) into .agents/skills/vibe-requirements-validator in your project. Codex loads it when a task matches its description.
Can I use Vibe Requirements Validator 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 ash1794/vibe-engineering --skill vibe-requirements-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-requirements-validator, .gemini/skills/vibe-requirements-validator, .github/skills/vibe-requirements-validator and .opencode/skills/vibe-requirements-validator in your project.
What does Vibe Requirements Validator need to run?
SKILL.md names no scripts, command-line tools or credentials: Vibe Requirements Validator is instructions for the agent only.
Does Vibe Requirements Validator 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 Vibe Requirements Validator 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 Vibe Requirements Validator use?
Vibe Requirements Validator 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 Vibe Requirements Validator use?
About 558 tokens (SKILL.md is roughly 2.2k 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 Vibe Requirements Validator?
Skills that share tags, products or a category with Vibe Requirements Validator: Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Ralph Tui Create JSON (subsy/ralph-tui, 2.5k stars) and To Prd (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Requirements Validator?
ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.