validate
Validate specification against schema and quality rules.
What this skill does
# Validate Specification Validate a specification against the canonical schema and quality rules. ## Workflow 1. **Load Specification** - Read the specification file - Parse YAML frontmatter and content 2. **Schema Validation** - Spawn `spec-reviewer validate` agent - Check required fields present - Validate field formats - Check requirement ID patterns 3. **EARS Pattern Validation** - Verify all requirements use EARS format - Check pattern syntax correctness - Identify malformed requirements 4. **Acceptance Criteria Validation** - Verify all requirements have acceptance criteria - Check Given/When/Then format - Identify missing or incomplete criteria 5. **Quality Assessment** - Calculate INVEST scores per requirement - Check for ambiguous language - Identify missing sections 6. **Report Results** - Show validation status (PASS/FAIL) - List issues by severity - Provide remediation guidance ## Arguments - `$ARGUMENTS` - Path to specification file ## Examples ```bash # Validate specific specification /spec-driven-development:validate .specs/user-auth/spec.md # Validate all specifications /spec-driven-development:validate --all ``` ## Validation Report ```markdown # Validation Report: user-auth **Status:** ⚠️ PASS WITH WARNINGS **Timestamp:** 2024-01-15T10:30:00Z ## Schema Compliance ✓ All required fields present ✓ Valid frontmatter format ✓ Requirement IDs follow pattern ## EARS Format ✓ FR-1: Valid Event-Driven pattern ✓ FR-2: Valid State-Driven pattern ⚠️ FR-3: Missing SHALL keyword ## Acceptance Criteria ✓ All requirements have criteria ✓ Given/When/Then format correct ⚠️ FR-2.AC-3: Vague "then" clause ## INVEST Scores | Req | I | N | V | E | S | T | Total | | --- | - | - | - | - | - | - | ----- | | FR-1 | 2 | 2 | 2 | 2 | 2 | 2 | 12/12 | | FR-2 | 2 | 2 | 2 | 1 | 2 | 1 | 10/12 | | FR-3 | 2 | 2 | 2 | 2 | 1 | 2 | 11/12 | ## Recommendations 1. FR-3: Add SHALL keyword for EARS compliance 2. FR-2.AC-3: Make outcome more specific ``` ## Related Commands - `/spec-driven-development:audit` - Full quality audit with scoring - `/spec-driven-development:refine` - AI-assisted refinement - `/spec-driven-development:specify` - Generate new specification
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.