refine-quality-profile

Refine intent-authored quality profiles into ISO 25010 NFR targets with delta logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a first-cut quality profile into an architecturally grounded set of NFR targets by tightening (and only tightening) them against inventory constraints, project-profile pins, epic constraints, and regulatory requirements.

Core Features & Use Cases

  • Refines NFR targets without naming mechanisms: Produces an ISO 25010-based target profile that describes what must be achieved, leaving delivery mechanisms to physical architecture.
  • Produces traceable refinement evidence: Writes a delta_log capturing every adjustment with a specific architectural driver and rationale.
  • Enforces a security “ratchet up only” rule: Guarantees security characteristics can never be loosened, halting with a structural failure when that would occur.
  • Surfaces decisions for orchestration: Emits a decision-manifest that tiers each refinement and records user response state for downstream orchestration.

Quick Start

Ask the tech-designer stage 2 orchestrator to run refine-quality-profile to generate architecture/quality-profile.yaml and architecture/decision-manifest-refine-quality-profile.yaml from the specified /specify inputs.

Frequently Asked Questions about refine-quality-profile

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

FAQPage Schema
How do I refine non-functional requirements against architecture constraints?

To refine non-functional requirements, evaluate specify-level quality profile assumptions against system inventory ceilings, project-profile pins, and regulatory floors, producing tightened ISO 25010 NFR targets with a full delta log.

What is the security ratchet rule for ISO 25010 quality profiles?

The security ratchet rule enforces that security characteristics in an ISO 25010 quality profile can never be loosened during refinement, halting with a structural failure if an adjustment attempts to weaken security targets.

How do I trace NFR target adjustments to architectural drivers?

Trace NFR target adjustments by generating a delta log that captures every refinement, requiring non-empty driver.kind and driver.reference fields to record the specific architectural constraint and rationale for each change.

Does the quality profile refinement process define physical architecture mechanisms?

No, quality profile refinement produces an ISO 25010-based target profile describing what must be achieved, intentionally leaving the naming of delivery mechanisms to the physical architecture stage.

Can I use architectural constraints to tighten existing NFR targets without breaking compliance?

Yes, you can tighten NFR targets by reconciling intent-authored quality profiles against epic constraints and regulatory floors, ensuring compliance while emitting a decision manifest to record user response state for orchestration.

Why does quality profile refinement halt when security targets are adjusted?

Quality profile refinement halts because the security ratchet rule strictly prohibits loosening security characteristics, triggering a structural failure to prevent any architectural constraint from degrading required security floors.