skills.rest
kapilvirenahuja
kapilvirenahujaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

validate-implementation-design

Validate YAML implementation design artifacts against intent constraints.

3|Updated Jan 25, 2026
Search Tags:#yaml#architecture validation#intent-driven development#deterministic workflows#scenario gating#compartmentalization
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill validate-implementation-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-implementation-design
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/validate-implementation-design
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill validate-implementation-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents implementation design drift by checking YAML artifacts for missing structure, incorrect linkages, and intent-compromising content before anything gets locked or built.

Core Features & Use Cases

  • Cross-validate intent structure: Reads features, architecture, tech, scenarios, and plan YAML files and checks them for internal consistency against intent constraints.
  • Detect compartmentalization breaks: Flags audience collisions (e.g., product/stakeholder content appearing in architect-only artifacts) and other structural issues that make downstream decisions unreliable.
  • Guarantee scenario-to-plan traceability: Ensures scenario IDs are properly referenced, gated, uniquely mapped, and counted consistently across the execution plan.
  • Produce a decision-ready validation result: Returns a structured validation_result containing per-check outcomes and classified issues without modifying any input artifact.

Quick Start

Ask the agent to run validate-implementation-design with the full paths to features.yaml, architecture.yaml, tech.yaml, scenarios.yaml, and plan.yaml to get a validation_result describing any violations.

Frequently Asked Questions about validate-implementation-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate YAML design artifacts for architecture consistency?▼

To validate YAML design artifacts for architecture consistency, you ingest five specified YAML files to check internal structure and intent constraints. This process returns a structured validation result with per-check PASS or FAIL outcomes without modifying any input artifacts.

How does scenario gating work for execution plan traceability?▼

Scenario gating works for execution plan traceability by ensuring scenario IDs are properly referenced, uniquely mapped, and counted consistently across the plan. This mechanism flags missing linkages and intent-compromising content to prevent implementation design drift before anything gets built.

How do I detect compartmentalization breaks in intent-driven development?▼

You detect compartmentalization breaks in intent-driven development by cross-validating YAML artifacts to flag audience collisions. This identifies when product or stakeholder content improperly appears in architect-only artifacts, making downstream decisions unreliable.

Can I use read-only validation for enterprise-grade YAML workflows?▼

Yes, you can use read-only validation for enterprise-grade YAML workflows by ingesting five specified YAML paths without modifying any artifact. This suits design-time workflows that assemble features, architecture, technology, scenarios, and execution plans for deterministic, auditable coverage.

What is the best way to prevent implementation design drift in deterministic workflows?▼

The best way to prevent implementation design drift in deterministic workflows is cross-validating intent structure across YAML artifacts. This approach checks features, architecture, tech, scenarios, and plan files for missing structure, incorrect linkages, and intent-compromising content before locking or building.

Related Skills

Explore More Software Engineering Skills→
jkhowlandjkhowland

plan-eng-review

Identify engineering plan gaps across architecture, data flow, edge cases, tests, and performance.

Community
Advanced
kcleto-aikcleto-ai
41

gos-critic-lp

Validate landing page folders against CRO, Anti-AI, Tailwind, and Footer quality gates.

Community
Advanced
agentic-inagentic-in
577

Writing Plans

Generate milestone-based plans with dependencies, risks, and validation criteria.

Official
Intermediate
M-Abdullah07M-Abdullah07
1

ui-visual-validator

Assess UI visual changes for consistency, accessibility, and design system conformance.

Community
Advanced