draft-verification-scenarios

Transform a features.yaml specification into grouped, traceable verification scenarios.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill draft-verification-scenarios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft-verification-scenarios
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/draft-verification-scenarios
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill draft-verification-scenarios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a features specification into a complete set of verification scenarios so every feature behavior is traceable and ready for validator use.

Core Features & Use Cases

  • Scenario traceability from features: Produces scenarios.yaml where each feature behavior maps to at least one scenario, preserving back-links to features.
  • Validator-ready coverage and gates: Generates feature_gates with required scenario IDs per feature plus a coverage summary (including automated vs hybrid counts).
  • Deterministic artifact creation: Writes a scenarios.yaml artifact at the requested output location without validating, executing, or deciding next steps.

Quick Start

Use the draft-verification-scenarios skill to create a scenarios.yaml artifact for your features specification at features_yaml_path and write it under output_base.

Frequently Asked Questions about draft-verification-scenarios

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

FAQPage Schema
How do I generate traceable verification scenarios from a features specification?▼

You generate verification scenarios by transforming a features.yaml specification into a grouped, traceable scenarios.yaml file. This maps every feature behavior to executable scenario definitions with unique IDs and back-links for full requirements traceability.

What is requirements traceability in YAML scenario generation?▼

Requirements traceability in YAML scenario generation ensures every feature behavior maps to at least one verification scenario. It preserves back-links to features and produces feature gates with required scenario IDs for quality validation and coverage.

How do I create feature gates and coverage summaries for test planning?▼

You create feature gates and coverage summaries by drafting a scenarios.yaml artifact from your features specification. The output includes required scenario IDs per feature and automated versus hybrid counts for test planning.

Can I use this to generate acceptance and e2e test scenarios from features.yaml?▼

Yes, you can generate acceptance and e2e test scenarios from features.yaml. The process maps feature behaviors to executable unit, integration, e2e, and acceptance scenario definitions for enterprise intent-driven development workflows.

Does the generated scenarios.yaml validate or execute the verification scenarios?▼

No, the generated scenarios.yaml does not validate, execute, or decide next steps. It deterministically writes a validator-ready YAML artifact with full field presence and empty uncovered features lists for downstream execution tools.