agentleFS
crgarcia12crgarcia12/Liliput/.github/skills/spec-validator/SKILL.md

spec-validator

Skill4 starsChanged 4 months agoISCView on GitHub

Validate consistency and traceability across the specification chain (PRD → FRD → Gherkin). Detect gaps, orphans, contradictions, and missing coverage. Use at Phase 2 exit (before human gate), Phase 3 entry (before e2e generation), Phase 4 entry (before Gherkin generation), on resume (re-validate specs haven't drifted), or after human edits to any spec file (specs/prd.md, specs/frd-*.md, specs/features/*.feature).

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Spec Validator

Validate that every requirement traces from PRD → FRD → Gherkin with no gaps or orphans.

Steps

  1. Parse PRD — Extract all user stories and requirements from specs/prd.md
  2. Parse FRDs — For each specs/frd-*.md, extract all functional requirements
  3. Trace PRD → FRD — Verify every PRD requirement maps to at least one FRD
  4. Parse Gherkin — For each specs/features/*.feature, extract all scenarios
  5. Trace FRD → Gherkin — Verify every FRD requirement has at least one Gherkin scenario
  6. Detect orphans — Find Gherkin scenarios that don't trace back to any FRD requirement
  7. Detect contradictions — Flag requirements that conflict across FRDs
  8. Report — Generate a coverage summary

Output Format

Coverage: <percentage>% of requirements have Gherkin scenarios
Verdict: PASS | FAIL

Gaps (requirements without scenarios):
- <FRD file>: <requirement description>

Orphans (scenarios without requirements):
- <feature file>: <scenario name>

Contradictions:
- <FRD file A> vs <FRD file B>: <description>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.