infer-quality-vision-from-code

name	infer-quality-vision-from-code
description	Synthesize a quality-vision proposal for a brownfield codebase by merging the already-inferred nfr-spec, quality-profile, physical-architecture, and logical-architecture proposals, then attaching scan-index signals (ADRs, CI/lint/test config files, commit cadence) to the relevant ISO 25010 characteristics. Produces a Tier 1 proposal at architecture/quality-vision.yaml. Used exclusively by tech-architect during /codify.
version	0.1.0
user-invocable	false
model	sonnet
allowed-tools	Read, Write, Grep, Glob
deprecated	true
deprecated_note	#434 ProductOS realignment — superseded by the command model; retained for Phase E reference, not installed

infer-quality-vision-from-code

Called by tech-architect during the /codify play, AFTER infer-nfr-spec-from-code, infer-quality-profile-from-code (test-engineer output), infer-physical-architecture-from-code, and infer-logical-architecture-from-code have already written their proposals. Produces architecture/quality-vision.yaml at {stm_base}/{issue}/evidence/codify/proposals/architecture/quality-vision.yaml, plus a companion decision manifest and resolution trace.

Purpose

By the time this skill runs, four upstream proposals already describe what the codebase does for quality: quality-profile.yaml (ISO 25010 relevance + target levels), nfr-spec.yaml (per-NFR mechanisms + verification methods), physical-architecture.yaml (specific named products), logical-architecture.yaml (component IDs + responsibilities).

This skill does synthesis, not fresh inference. The primary source for every vision field is the upstream proposals; scan-index is used only to attach ADR references and CI/lint/test config files to the right characteristic, and to read commit cadence for the reliability narrative. It does NOT re-pick tools, re-set thresholds, or re-target levels. Re-inference across boundaries is a discipline violation (see Boundaries).

Output is a Tier 1 proposal — learning_category: quality, sub_category: architecture. Per DSD, high-confidence tier-1 entries flow through the batch-confirm surfacing stream at the /codify checkpoint; knowledge gaps flow through the 1-by-1 stream.

Input

Receive from the /codify play orchestrator via JSON contract. All paths absolute.

Field	Required	Description
scan_index_path	yes	Path to scan-index.json produced by scan.py. Secondary input — used only for ADRs, config_files, and git.commits_analyzed.
stm_base	yes	STM root, resolved from stm.base-path in .garura/core/config.yaml.
issue	yes	Issue number (STM namespace).