AgentStack
SKILL verified MIT Self-run

Vibe Requirements Validator

skill-ash1794-vibe-engineering-requirements-validator · by ash1794

Validates PRD, user stories, or feature requirements against SMART criteria. Use when reviewing requirements to catch vagueness before it causes expensive rework.

No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-ash1794-vibe-engineering-requirements-validator

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Vibe Requirements Validator? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

  1. List all requirements from the document
  2. Score each on SMART (1-5 per dimension)
  3. Flag issues:
  • Score = 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

  1. Measurability crisis — X requirements have M < 3
  2. Near-duplicates — [list pairs]
  3. Not requirements — [positioning statements]

Recommended Revisions

| ID | Current | Suggested | |----|---------|-----------| | FR-3 | "Improve load time" | "Reduce initial page load to <2s on 3G" |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.