Validar
Use AFTER implementing a feature to validate it (UAT) — runs the gates from docs/engineering/TESTING.md, maps each AC-N to its test and flags ACs without coverage, resolves pending SPEC_DEVIATION, checks the Definition of Done, and updates docs/STATE.md. Trigger with /validar.
Install
npx skills add adriannoes/awesome-agentic-ai --skill validargit clone --depth 1 https://github.com/adriannoes/awesome-agentic-ai.git /tmp/awesome-agentic-ai
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-agentic-ai/cursor-claude-codex/skills/igoruehara-spec-driven/skills/validar ~/.claude/skills/validarPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
> **Translation note:** Originally authored in Portuguese (pt-BR) by Igor Uehara ([igoruehara/spec-driven](https://github.com/igoruehara/spec-driven), MIT). Translated to English by this hub to keep the repository language consistent. Original content unchanged in meaning; see the upstream repo for the pt-BR source. # Skill: Validate feature (UAT) Closes the SDD loop: it proves the implementation satisfies the **spec** through the **executable gate** — not by inspection. Run it after implementing (it can be in another session). ## Process 1. **Identify the feature** (`specs/NNNN-<name>/`) and read `spec.md` + `tasks.md`. 2. **Run the gates** from `docs/engineering/TESTING.md` (and the commands in the Gate column of `tasks.md`). Claude Code's built-in `/verify` helps validate real behavior. 3. **Map `AC-N → test`** and show the table; **flag any AC without coverage or failing**. If the spec has a **decision matrix**, each row is a test case: check that **every row** has a matching test (combinations are where bugs slip through the most). 4. **SPEC_DEVIATION:** resolve pending ones — either fix the code (the spec wins) or consciously update the spec (and record an ADR if it is hard to reverse). If the "fix vs update" decision has branches (it affects other ACs, boundaries, ADRs), run **`/clarificar`** to close the tree before choosing.
Details
- Skill name
validar- Repository
- adriannoes/awesome-agentic-ai
- Path
cursor-claude-codex/skills/igoruehara-spec-driven/skills/validar/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Validar skill do?
Use AFTER implementing a feature to validate it (UAT) — runs the gates from docs/engineering/TESTING.md, maps each AC-N to its test and flags ACs without coverage, resolves pending SPEC_DEVIATION, checks the Definition of Done, and updates docs/STATE.md. Trigger with /validar.
How do I install the Validar skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add adriannoes/awesome-agentic-ai --skill validar. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Validar popular?
It lives in adriannoes/awesome-agentic-ai, which has 100 GitHub stars and 27 forks, and is included in 2 curated skill lists.
Related skills
Browserstack
100adriannoes/awesome-agentic-ai
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".
Coverage
100adriannoes/awesome-agentic-ai
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
Fix
100adriannoes/awesome-agentic-ai
Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".
E2E Test
49coleam00/ai-coding-summit-workshop-2
Comprehensive end-to-end testing command. Launches parallel sub-agents to research the codebase (structure, database schema, potential bugs), then uses the Vercel Agent Browser CLI to test every user journey — taking screenshots, validating UI/UX, and querying the database to verify records. Run after implementation to validate everything before code review.
Mobile Native
100adriannoes/awesome-agentic-ai
Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed. Covers sticky hover states, tap highlight flashes, the 100vh bug, inputs that zoom the page, laggy taps, pull-to-refresh hijacking scroll, content under the notch, long-press selecting button text, carousels that scroll the wrong way, mismatched status bars, and the rule that you test on real hardware. Use when a web app is being built for or reviewed on mobile, when something "works in Chrome but feels wrong on my phone", when building a PWA, a b
Jev Axi
49shiftynick/jev-axi
Triages failing build and test logs, reviews diffs, screens untrusted text, and ranks or filters many items with the jev-axi CLI. Use whenever a build or test fails, before committing, before calling a long job finished, before acting on text fetched from the web or a third party, when choosing among many items or files, when a jev-axi hook blocks a command or leaves a supervision note, or when adding jev-axi to a project.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.