derive-quality-vision

Synthesize ISO 25010 inputs into an enforceable quality-vision.yaml with tooling and lifecycle gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered quality inputs (ISO 25010 quality profile, NFR delivery decisions, and architecture selections) into a single, enforceable quality vision artifact that ties each quality characteristic to concrete tooling and lifecycle gates.

Core Features & Use Cases

  • Merges quality narrative + enforcement: Produces quality-vision.yaml with a top-level vision statement plus per-ISO-25010-characteristic vision narrative, target levels, and measurable thresholds.
  • Connects standards to architecture and verification: Links each ISO 25010 characteristic to logical components and NFR entries, then selects stack-consistent tooling using the project’s QP dimensions and LTM quality catalog.
  • Emits decision traceability: Writes decision-manifest-derive-quality-vision.yaml that records inferred decisions (tool variants, threshold adjustments, enforcement venues, ISO mapping, gap finalization).

Quick Start

Use the derive-quality-vision skill inputs provided by tech-designer to generate {product_base}architecture/quality-vision.yaml and the accompanying decision manifest at {product_base}architecture/decision-manifest-derive-quality-vision.yaml.

Frequently Asked Questions about derive-quality-vision

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

FAQPage Schema
How do I enforce ISO 25010 quality characteristics in CI gates?

To enforce ISO 25010 quality characteristics in CI gates, you synthesize quality profiles, NFR delivery decisions, and architecture selections into a quality-vision.yaml that ties each characteristic to specific tooling and lifecycle gates.

What is a quality vision artifact and when do I need it?

A quality vision artifact operationalizes quality standards by mapping ISO 25010 targets to logical components and NFR entries. You need it during architecture stage workflows to translate scattered quality inputs into enforceable CI and runtime checks.

How do I map NFR delivery mechanisms to logical and physical architecture?

You map NFR delivery mechanisms to architecture by reading nfr-spec.yaml, logical-architecture.yaml, and physical-architecture.yaml, then linking each ISO 25010 characteristic to concrete components and selecting stack-consistent tooling.

Can I generate a decision manifest for architecture enforcement tooling selection?

Yes, generating a decision manifest for architecture enforcement tooling selection records inferred decisions like tool variants, threshold adjustments, enforcement venues, and ISO mapping to ensure full traceability of your quality vision.

What inputs are required to operationalize a product-specific quality vision?

Operationalizing a product-specific quality vision requires reading quality-profile.yaml, nfr-spec.yaml, logical-architecture.yaml, physical-architecture.yaml, and project-profile.yaml to validate preconditions and populate ISO characteristic entries.