How do I install the Specs Validating Structure skill?

Run npx skillmds add wahidyankf/specs-validating-structure in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Specs Validating Structure safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Specs Validating Structure?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Specs Validating Structure free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Specs Validating Structure?

wahidyankf (@wahidyankf) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Specs Validating Structure by wahidyankf

Name: Specs Validating Structure
Rating: 4.5 (4 reviews)
Author: wahidyankf

Specs Validating Structure

Validation methodology for specs/ folders — nine categories covering README/feature-file structural completeness, Gherkin format compliance, cross-folder consistency, C4 diagrams, cross-references, spec-to-implementation alignment, tree-shape compliance, and BDD/contracts adoption gaps. Used by specs-checker and specs-fixer.

wahidyankf e170574 8 files · 17.6 KB Updated Sep 10, 2026

File contents

Validating Specs Structure

Methodology for validating explicitly-listed specs/ folders (and their subfolders) for structural completeness, content accuracy, internal consistency, and cross-folder coherence.

Scope Rule

Validate only explicitly listed folders and their subfolders — never implicit discovery. Cross-folder consistency (Category 4) runs only when 2+ folders are listed; it's skipped for a single folder. Subfolders are always included automatically.

Lifecycle Delegation

Quality-gate invocations may pass exact delegated-gate-ids under Lifecycle Validation Ownership. Do not run, re-derive, report, or fix the matching predicates: governance-readme-index owns README existence/index membership; md-links owns internal path/fragment resolution; specs-structure owns adoption, tree shape, and registered counts. Keep Gherkin journey coherence, semantic, and cross-folder judgment. Omitted delegation preserves standalone full behaviour. Accept lifecycle-evidence: checkers preserve it; fixers scope-intersect changed files and return updated-lifecycle-evidence.

The Nine Validation Categories

See reference/validation-categories-1-4.md for Structural Completeness (README coverage), Feature File Inventory Accuracy, Gherkin Format Compliance, and Cross-Folder Consistency, and reference/validation-categories-5-9.md for C4 Diagram Consistency, Cross-Reference Integrity, Spec-to-Implementation Alignment, Spec Tree Shape Compliance and Adoption Gaps (deterministic via rhino-cli specs structure validate).

Drift Detection, Execution Pattern, and Report Format

See reference/drift-detection-and-reporting.md for current deterministic commands, lifecycle filtering, the six-step execution pattern, and the full audit report template.

Fixer Mechanics

See reference/fixer-disposition.md for how specs-fixer maps each of the nine categories to a fix disposition (auto-fixable / requires review / skip), and reference/fixer-execution-and-safety.md for its execution pattern, fix report format, safety rules, and changed-file capture.

What This Methodology Does NOT Cover

Test bindings and semantic implementation (use the gherkin-implementation-review), governance docs (rules-checker), or runtime tests (CI). This methodology is read-only.

Conventions: App README vs Specs Convention, Specs Directory Structure Convention.

Agents: specs-checker (implements this methodology), specs-fixer, specs-maker.

---name: specs-validating-structuredescription: Validation methodology for specs/ folders — nine categories covering README/feature-file structural completeness, Gherkin format compliance, cross-folder consistency, C4 diagrams, cross-references, spec-to-implementation alignment, tree-shape compliance, and BDD/contracts adoption gaps. Used by specs-checker and specs-fixer.---# Validating Specs StructureMethodology for validating explicitly-listed `specs/` folders (and their subfolders) forstructural completeness, content accuracy, internal consistency, and cross-folder coherence.## Scope RuleValidate **only** explicitly listed folders and their subfolders — never implicit discovery.Cross-folder consistency (Category 4) runs only when 2+ folders are listed; it's skipped for asingle folder. Subfolders are always included automatically.## Lifecycle DelegationQuality-gate invocations may pass exact `delegated-gate-ids` under[Lifecycle Validation Ownership](../../../repo-governance/workflows/meta/workflow-identifier/check-fix-lifecycle-validation-ownership.md).Do not run, re-derive, report, or fix the matching predicates: `governance-readme-index` ownsREADME existence/index membership; `md-links` owns internal path/fragment resolution;`specs-structure` owns adoption, tree shape, and registered counts. Keep Gherkin journey coherence,semantic, and cross-folder judgment. Omitted delegationpreserves standalone full behaviour. Accept `lifecycle-evidence`: checkers preserve it; fixersscope-intersect changed files and return `updated-lifecycle-evidence`.## The Nine Validation CategoriesSee [reference/validation-categories-1-4.md](reference/validation-categories-1-4.md) forStructural Completeness (README coverage), Feature File Inventory Accuracy, Gherkin FormatCompliance, and Cross-Folder Consistency, and[reference/validation-categories-5-9.md](reference/validation-categories-5-9.md) for C4Diagram Consistency, Cross-Reference Integrity, Spec-to-Implementation Alignment, Spec Tree ShapeCompliance and Adoption Gaps (deterministic via `rhino-cli specs structure validate`).## Drift Detection, Execution Pattern, and Report FormatSee [reference/drift-detection-and-reporting.md](reference/drift-detection-and-reporting.md)for current deterministic commands, lifecycle filtering, the six-step executionpattern, and the full audit report template.## Fixer MechanicsSee [reference/fixer-disposition.md](reference/fixer-disposition.md) for how `specs-fixer`maps each of the nine categories to a fix disposition (auto-fixable / requires review / skip), and[reference/fixer-execution-and-safety.md](reference/fixer-execution-and-safety.md) for itsexecution pattern, fix report format, safety rules, and changed-file capture.## What This Methodology Does NOT CoverTest bindings and semantic implementation (use the[`gherkin-implementation-review`](../../../repo-governance/workflows/gherkin-implementation-review.md)),governance docs (`rules-checker`), or runtime tests (CI). This methodology is read-only.## Related**Conventions**: [App README vs Specs Convention](../../../repo-governance/conventions/structure/app-readme-vs-specs.md),[Specs Directory Structure Convention](../../../repo-governance/conventions/structure/specs-directory-structure.md).**Agents**: `specs-checker` (implements this methodology), `specs-fixer`, `specs-maker`.

Frequently asked questions