qfai 1.7.2 → 1.7.4

package/README.md

@@ -123,8 +123,8 @@ QFAI includes a small set of custom skills (stored under `.qfai/assistant/skills
 - **qfai-sdd**: Unified SDD entrypoint with discussion-pack preflight guard (missing/incomplete/blocking OQ causes stop + next action guidance).
 - **qfai-prototyping**: Build an all-spec contract-aligned skeleton and prove runtime coverage before deep coding.
 - **qfai-atdd**: Implement acceptance tests driven by specs/scenarios.
-- **qfai-implement**: Unified TDD micro-cycle (Red/Green/Refactor) one test at a time using `test-list.md` as the execution ledger.
-- **qfai-verify**: Run/interpret the local quality gates and produce a release-ready summary.
+- **qfai-implement**: Unified TDD micro-cycle (Red/Green/Refactor) one test at a time using `test-list.md` as the execution ledger, including ledger status updates and exception closure.
+- **qfai-verify**: Run full-scan local quality gates (`validate --fail-on error`, `report`, repo gates) and produce reviewer-approved evidence under `.qfai/evidence/`.
 
 ### Workflow sequence (example)
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/SKILL.md

@@ -109,7 +109,11 @@ Every major artifact in this stage MUST include this table schema:
 - `03_Story-Workshop.md` MUST contain at least one Mermaid diagram in ` ```mermaid ` fences.
 - If UI requirements exist, include an HTML+CSS visual mock in `03_Story-Workshop.md`.
 - **UI-bearing Authoring Requirements**:
-  - A pack is UI-bearing if `03_Story-Workshop.md` contains HTML tags (`<style>`, `<div>`, etc.) or Mermaid screen flow diagrams.
+  - UI-bearing detection is based on **surface type classification**
+    (see `## UI-bearing Detection` below).
+  - Content signals in `03_Story-Workshop.md`
+    (HTML tags, Mermaid screen flows) serve as supplementary detection hints,
+    not the primary SSOT.
   - UI-bearing packs MUST include a `## Design Direction Summary` section in `03_Story-Workshop.md` with all 6 subsections:
     1. `### Option Comparison` — 2+ distinct design options (QFAI-DDP-020)
     2. `### Anchor Screen Selection` — explicit selection referencing a compared option (QFAI-DDP-021)
@@ -135,6 +139,61 @@ Every major artifact in this stage MUST include this table schema:
 - OQ Register must include all mandatory columns: OQ-ID, Title, Gate, Disposition, Owner, Rationale, Options, Recommendation, Next-Decision-Point, Due, Evidence.
 - Deferred table must include all mandatory columns: OQ-ID, Title, Gate, Deferred-Reason, Deferred-Until, Owner, Due, Severity, Impact, Mitigation, Evidence.
 
+## UI-bearing Detection
+
+### Surface Classification
+
+Classify the project's surface type to determine whether UI/UX sidecar artifacts are required.
+Classification is based on **surface type only**, not interaction complexity (DR-0057).
+
+| Surface Type | UI-bearing | Sidecar Generation                       | Example                                  |
+| ------------ | ---------- | ---------------------------------------- | ---------------------------------------- |
+| web-ui       | Yes        | Full 11-file uiux/ sidecar               | Web application with user-facing screens |
+| mobile-ui    | Yes        | Full 11-file uiux/ sidecar               | Mobile app with touch interactions       |
+| desktop-ui   | Yes        | Full 11-file uiux/ sidecar               | Desktop application with GUI             |
+| mixed        | Yes        | Full 11-file uiux/ sidecar               | Cross-platform with UI components        |
+| non-ui       | No         | No uiux/ directory, no sidecar generated | CLI tool, API service, library           |
+
+### Detection Signals
+
+- Check `01_Context.md` for explicit surface type declarations
+- Check `03_Story-Workshop.md` for HTML tags, screen flows, or UI-related user stories
+- When ambiguous (e.g., web endpoint without UI components), classify by surface type, not by interaction complexity
+
+### Sidecar Generation Flow
+
+When UI-bearing is detected:
+
+1. Generate all 11 uiux/ sidecar files (partial generation is not permitted)
+2. Apply UX intent cross-references to core templates
+3. Add UI-bearing completion conditions
+
+When non-ui is detected:
+
+- Skip uiux/ sidecar generation entirely — no uiux/ directory, no errors
+- Core 15-file pack is generated as before
+- No additional UI/UX completion conditions apply
+
+### UI-bearing Completion Conditions
+
+For UI-bearing projects, the following conditions must ALL be satisfied before discussion completion:
+
+1. **Strategy selected**: `uiux/10_strategy.md` is populated with a chosen implementation approach
+2. **Scoring axes defined**:
+   `uiux/20_eval_axis_usability.md`,
+   `uiux/21_eval_axis_consistency.md`,
+   `uiux/22_eval_axis_accessibility.md`,
+   `uiux/23_eval_axis_delight.md`
+   have evaluation criteria and measurement approaches
+3. **Anchor screen chosen**: `uiux/31_anchor.md` documents the selected anchor screen with rationale
+4. **Contracts drafted**: `uiux/40_contracts.md` contains interaction contracts for the anchor screen
+
+Completion is blocked until all 4 conditions are met. Skipping any condition prevents the discussion from being marked as complete.
+
+### Non-UI Completion
+
+For non-ui projects, completion conditions remain unchanged from prior versions. No additional UI/UX conditions apply; no sidecar artifacts are required.
+
 ## Goal
 
 Produce a unified 15-file discussion pack with explicit decisions, requirements, OQ states, and rationale so `/qfai-sdd` starts without unresolved blockers.

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/01_Context.md

@@ -1,5 +1,7 @@
 # 01 Context
 
+<!-- UX-INTENT: If UI-bearing, see uiux/10_strategy.md for implementation strategy context -->
+
 ## Metadata
 
 | Key           | Value                        |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/02_Inception-Deck.md

@@ -43,6 +43,8 @@ flowchart LR
     App --> Data["Data Store"]
 ```
 
+<!-- UX-INTENT: If UI-bearing, reference uiux/30_comparison.md for design option alignment -->
+
 ## 7. What Keeps Us Up at Night (Risks)
 
 | Risk | Probability | Impact | Mitigation |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/03_Story-Workshop.md

@@ -43,10 +43,36 @@ flowchart TD
   - Steps:
   - Exit point:
 
-## Screen Mock (HTML+CSS)
+## Behavior Obligations
 
-- Use this section when UI requirements exist.
+<!-- Primary focus for UI-bearing packs. Define behavioral requirements before visual mockups. -->
+
+### State Coverage
+
+| State     | Trigger   | Display   | Transitions   |
+| --------- | --------- | --------- | ------------- |
+| empty     | [trigger] | [display] | [transitions] |
+| loading   | [trigger] | [display] | [transitions] |
+| error     | [trigger] | [display] | [transitions] |
+| populated | [trigger] | [display] | [transitions] |
+
+### Interaction Contracts
+
+| Element   | Action   | Expected Result | Error Handling |
+| --------- | -------- | --------------- | -------------- |
+| [element] | [action] | [result]        | [error case]   |
+
+### Error Handling
+
+- Input validation: [approach]
+- Network failure: [approach]
+- Timeout: [approach]
+
+## Screen Mock — Fallback (HTML+CSS)
+
+- Secondary: required when UI requirements exist, but subordinate to Behavior Obligations above.
 - Visual mock only; do not include JavaScript behavior.
+- This HTML/CSS mock is a fallback visual aid that supplements (not replaces) the behavioral definitions.
 
 ```html
 <section class="screen-mock">
@@ -99,11 +125,12 @@ See 04_Sources.md for full competitive reference registry.
 ### State Coverage
 
 <!-- Define all 4 required states. (QFAI-DDP-024) -->
+<!-- SSOT for state details: Behavior Obligations > State Coverage table above. Keep these bullets for validator compliance; fill display-level details or reference the table. -->
 
-- empty: [Empty state display]
-- loading: [Loading state display]
-- error: [Error state display]
-- populated: [Populated state display]
+- empty: [Empty state display — see Behavior Obligations table for triggers/transitions]
+- loading: [Loading state display — see Behavior Obligations table for triggers/transitions]
+- error: [Error state display — see Behavior Obligations table for triggers/transitions]
+- populated: [Populated state display — see Behavior Obligations table for triggers/transitions]
 
 ### Design Anti-goals
 

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/05_Scope.md

@@ -1,5 +1,7 @@
 # 05 Scope
 
+<!-- UX-INTENT: If UI-bearing, see uiux/00_index.md for sidecar scope inventory -->
+
 ## In Scope
 
 - Capability 1:

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/06_REQ.md

@@ -1,5 +1,7 @@
 # 06 REQ (Functional Requirements)
 
+<!-- UX-INTENT: If UI-bearing, see uiux/40_contracts.md for screen interaction requirements -->
+
 ## Requirements Table
 
 | REQ-ID   | Title | Description | Source   | Priority | Status |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/07_NFR.md

@@ -1,5 +1,7 @@
 # 07 NFR (Non-Functional Requirements)
 
+<!-- UX-INTENT: If UI-bearing, see uiux/20_eval_axis_usability.md for usability measurement targets -->
+
 ## Requirements Table
 
 | NFR-ID   | Category    | Title | Target         | Measurement | Source   | Priority |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/08_Glossary.md

@@ -1,5 +1,7 @@
 # 08 Glossary
 
+<!-- UX-INTENT: If UI-bearing, include terms from uiux/00_index.md sidecar vocabulary -->
+
 ## Term Definitions
 
 | Term     | Definition | Context | Source   |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/09_Constraints.md

@@ -1,5 +1,7 @@
 # 09 Constraints
 
+<!-- UX-INTENT: If UI-bearing, see uiux/22_eval_axis_accessibility.md for accessibility constraints -->
+
 ## Technical Constraints
 
 | ID   | Constraint | Rationale | Impact |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/10_Policy.md

@@ -1,5 +1,7 @@
 # 10 Policy
 
+<!-- UX-INTENT: If UI-bearing, see uiux/10_strategy.md for design policy alignment -->
+
 ## Security Policy
 
 - Authentication:

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/11_OQ-Register.md

@@ -1,5 +1,7 @@
 # 11 OQ Register
 
+<!-- UX-INTENT: If UI-bearing, track design direction OQs from uiux/60_critique_loop.md -->
+
 ## OQ Table
 
 | OQ-ID   | Title | Gate       | Disposition | Owner | Rationale | Options                              | Recommendation | Next-Decision-Point  | Due        | Evidence         |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/12_OQ-Resolution-Log.md

@@ -1,5 +1,7 @@
 # 12 OQ Resolution Log
 
+<!-- UX-INTENT: If UI-bearing, log design critique resolutions from uiux/60_critique_loop.md -->
+
 ## Resolution Timeline
 
 | Date       | OQ-ID   | Action   | Summary | Evidence |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/13_Deferred.md

@@ -1,5 +1,7 @@
 # 13 Deferred
 
+<!-- UX-INTENT: If UI-bearing, track deferred design decisions from uiux/50_review_bundle.md -->
+
 ## Deferred Items
 
 | OQ-ID   | Title | Gate       | Deferred-Reason | Deferred-Until | Owner | Due        | Severity | Impact                                         | Mitigation           | Evidence         |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/14_Review-Request.md

@@ -48,6 +48,17 @@
 - Rejection rationale: [Why other options were not selected]
 - Adopted competitive references: [Key references adopted from 04_Sources.md]
 
+## Sidecar Artifact Review Scope
+
+<!-- Required for UI-bearing packs. Reviews uiux/ sidecar artifacts. -->
+
+- Verify all 11 uiux/ sidecar files are present (when UI-bearing)
+- Verify uiux/10_strategy.md YAML schema conforms to version `"0.1"`
+- Verify scoring axes have evaluation criteria and measurement approaches
+- Verify option comparison covers 2+ options against all scoring axes
+- Verify anchor screen selection references a compared option
+- Verify screen contracts define all 4 required states (empty/loading/error/populated)
+
 ## Required Reviewers
 
 - Load all reviewers from `.qfai/assistant/steering/review-roster.yml`.

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/99_delta.md

@@ -1,5 +1,7 @@
 # 99 Delta
 
+<!-- UX-INTENT: If UI-bearing, record design direction changes from uiux/31_anchor.md -->
+
 ## Change History
 
 | Date       | Change Type | Section    | Summary | Rationale |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/00_index.md

@@ -0,0 +1,25 @@
+# uiux/ Sidecar Index
+
+## Purpose
+
+Manifest of all UI/UX sidecar artifacts produced during a UI-bearing discussion.
+
+## File Inventory
+
+| File                          | Purpose                                | Required |
+| ----------------------------- | -------------------------------------- | -------- |
+| 00_index.md                   | This manifest                          | Yes      |
+| 10_strategy.md                | Implementation strategy (YAML)         | Yes      |
+| 20_eval_axis_usability.md     | Usability evaluation axis              | Yes      |
+| 21_eval_axis_consistency.md   | Consistency evaluation axis            | Yes      |
+| 22_eval_axis_accessibility.md | Accessibility evaluation axis          | Yes      |
+| 23_eval_axis_delight.md       | Delight evaluation axis                | Yes      |
+| 30_comparison.md              | Option comparison against scoring axes | Yes      |
+| 31_anchor.md                  | Anchor screen selection rationale      | Yes      |
+| 40_contracts.md               | Screen interaction contracts           | Yes      |
+| 50_review_bundle.md           | Review input bundle                    | Yes      |
+| 60_critique_loop.md           | Critique loop tracking                 | Yes      |
+
+## Completeness Rule
+
+All 11 files MUST be present for a UI-bearing pack. Partial generation is not permitted (BR-0026-0002).

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/10_strategy.md

@@ -0,0 +1,28 @@
+# Implementation Strategy
+
+## YAML Strategy Definition
+
+```yaml
+version: "0.1"
+surface_type: "<web-ui|mobile-ui|desktop-ui|mixed>"
+strategy:
+  approach: "<description of the chosen implementation approach>"
+  rationale: "<why this approach was selected>"
+  constraints:
+    - "<constraint 1>"
+  risks:
+    - risk: "<risk description>"
+      mitigation: "<mitigation approach>"
+```
+
+## Strategy Selection Guidance
+
+- Select one implementation approach based on project constraints and surface type.
+- Reference scoring axes (20-23) for evaluation criteria.
+- One complete strategy definition per project; avoid verbose alternatives here.
+
+## Cross-references
+
+- Surface classification: see SKILL.md `## UI-bearing Detection`
+- Scoring axes: see `20_eval_axis_usability.md`, `21_eval_axis_consistency.md`, `22_eval_axis_accessibility.md`, `23_eval_axis_delight.md`
+- Option comparison: see `30_comparison.md`

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/20_eval_axis_usability.md

@@ -0,0 +1,26 @@
+# Evaluation Axis: Usability
+
+## Evaluation Criteria
+
+| Criterion        | Description                                      | Weight |
+| ---------------- | ------------------------------------------------ | ------ |
+| Learnability     | Time to complete core tasks for first-time users | High   |
+| Efficiency       | Steps required for frequent operations           | High   |
+| Error prevention | Safeguards against user mistakes                 | Medium |
+| Recovery         | Ease of recovering from errors                   | Medium |
+
+## Measurement Approach
+
+| Metric               | Method                   | Target             |
+| -------------------- | ------------------------ | ------------------ |
+| Task completion rate | Usability test (5 users) | >= 90%             |
+| Error rate           | Observation during tasks | <= 10%             |
+| Time on task         | Stopwatch measurement    | <= baseline \* 1.2 |
+
+## Scoring Guide
+
+- 5: Exceeds all targets with measurable margin
+- 4: Meets all targets
+- 3: Meets most targets with minor gaps
+- 2: Significant gaps in multiple criteria
+- 1: Fails most criteria

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/21_eval_axis_consistency.md

@@ -0,0 +1,26 @@
+# Evaluation Axis: Consistency
+
+## Evaluation Criteria
+
+| Criterion               | Description                                   | Weight |
+| ----------------------- | --------------------------------------------- | ------ |
+| Visual consistency      | Adherence to design tokens and spacing system | High   |
+| Interaction consistency | Similar actions produce similar results       | High   |
+| Terminology consistency | Same concepts use same labels throughout      | Medium |
+| Platform conventions    | Follows platform-specific patterns            | Medium |
+
+## Measurement Approach
+
+| Metric            | Method                                   | Target                    |
+| ----------------- | ---------------------------------------- | ------------------------- |
+| Token compliance  | Automated audit (design token drift)     | 0 raw values              |
+| Label audit       | Manual review of all user-facing strings | 0 inconsistencies         |
+| Pattern deviation | Component usage review                   | <= 2 justified deviations |
+
+## Scoring Guide
+
+- 5: Zero deviations from design system
+- 4: Minor deviations with documented rationale
+- 3: Some deviations, all justified
+- 2: Multiple unjustified deviations
+- 1: No consistent design system applied

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/22_eval_axis_accessibility.md

@@ -0,0 +1,26 @@
+# Evaluation Axis: Accessibility
+
+## Evaluation Criteria
+
+| Criterion             | Description                             | Weight |
+| --------------------- | --------------------------------------- | ------ |
+| WCAG compliance       | Meets WCAG 2.1 AA requirements          | High   |
+| Keyboard navigation   | All interactions reachable via keyboard | High   |
+| Screen reader support | Semantic HTML and ARIA labels           | High   |
+| Color contrast        | Meets minimum contrast ratios           | Medium |
+
+## Measurement Approach
+
+| Metric            | Method                  | Target                    |
+| ----------------- | ----------------------- | ------------------------- |
+| WCAG violations   | Automated axe-core scan | 0 critical/serious        |
+| Keyboard coverage | Manual tab-through test | 100% interactive elements |
+| Contrast ratio    | Automated check         | >= 4.5:1 (normal text)    |
+
+## Scoring Guide
+
+- 5: WCAG 2.1 AAA compliant
+- 4: WCAG 2.1 AA compliant, zero automated violations
+- 3: AA compliant with minor manual-only findings
+- 2: Critical accessibility gaps
+- 1: Not accessibility-tested

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/23_eval_axis_delight.md

@@ -0,0 +1,34 @@
+# Evaluation Axis: Delight
+
+## Evaluation Criteria
+
+| Criterion              | Description                              | Weight |
+| ---------------------- | ---------------------------------------- | ------ |
+| Perceived performance  | UI feels responsive and snappy           | High   |
+| Feedback quality       | Clear, helpful feedback for user actions | Medium |
+| Progressive disclosure | Information revealed at the right moment | Medium |
+| Aesthetic quality      | Visual polish and attention to detail    | Low    |
+
+## Measurement Approach
+
+| Metric              | Method                     | Target                       |
+| ------------------- | -------------------------- | ---------------------------- |
+| Perceived load time | User perception survey     | "fast" or "very fast" >= 80% |
+| Feedback coverage   | Audit of state transitions | 100% have feedback           |
+| Satisfaction score  | Post-task survey (1-5)     | >= 4.0                       |
+
+## Scoring Guide
+
+- 5: Users report delight; exceeds expectations
+- 4: Smooth experience; meets expectations
+- 3: Functional but unremarkable
+- 2: Friction points noticed by users
+- 1: Frustrating experience reported
+
+## Product-specific Axes
+
+<!-- Add project-specific delight criteria below. These are trend-derived or product-specific axes. -->
+
+| Criterion          | Description   | Weight   |
+| ------------------ | ------------- | -------- |
+| (project-specific) | (description) | (weight) |

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/30_comparison.md

@@ -0,0 +1,30 @@
+# Option Comparison
+
+## Purpose
+
+Compare 2+ design options against scoring axes to support anchor screen selection.
+
+## Comparison Matrix
+
+| Axis               | Option A: [Name] | Option B: [Name] | Notes       |
+| ------------------ | ---------------- | ---------------- | ----------- |
+| Usability (20)     | [score 1-5]      | [score 1-5]      | [rationale] |
+| Consistency (21)   | [score 1-5]      | [score 1-5]      | [rationale] |
+| Accessibility (22) | [score 1-5]      | [score 1-5]      | [rationale] |
+| Delight (23)       | [score 1-5]      | [score 1-5]      | [rationale] |
+
+## Aggregate Scoring
+
+| Option   | Weighted Total | Rank   |
+| -------- | -------------- | ------ |
+| Option A | [total]        | [rank] |
+| Option B | [total]        | [rank] |
+
+## Recommendation
+
+Selected: [Option X] — [rationale for selection based on scores and constraints]
+
+## Cross-references
+
+- Scoring axes: `20_eval_axis_usability.md`, `21_eval_axis_consistency.md`, `22_eval_axis_accessibility.md`, `23_eval_axis_delight.md`
+- Anchor selection: `31_anchor.md`

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/31_anchor.md

@@ -0,0 +1,27 @@
+# Anchor Screen Selection
+
+## Purpose
+
+Document the selected anchor screen and rationale for the design direction.
+
+## Selected Anchor
+
+- Screen: [Screen name/identifier]
+- Source option: [Option X from 30_comparison.md]
+- Rationale: [Why this screen was selected as the anchor]
+
+## Anchor Screen Description
+
+- Primary purpose: [What the user accomplishes on this screen]
+- Key interactions: [List of primary interactions]
+- Entry points: [How users reach this screen]
+- Exit points: [Where users go from this screen]
+
+## Design Constraints
+
+- [Constraint derived from comparison and scoring]
+
+## Cross-references
+
+- Option comparison: `30_comparison.md`
+- Screen contracts: `40_contracts.md`

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/40_contracts.md

@@ -0,0 +1,30 @@
+# Screen Contracts
+
+## Purpose
+
+Draft interaction contracts for the anchor screen and key screens.
+
+## Anchor Screen Contract
+
+### Screen: [Screen name]
+
+#### States
+
+| State     | Trigger                | Display                     | Transitions            |
+| --------- | ---------------------- | --------------------------- | ---------------------- |
+| empty     | Initial load, no data  | [empty state description]   | -> loading (on fetch)  |
+| loading   | Data fetch in progress | [loading indicator]         | -> populated, -> error |
+| error     | Fetch failure          | [error message + retry CTA] | -> loading (on retry)  |
+| populated | Data available         | [primary content layout]    | -> empty (on clear)    |
+
+#### Interactions
+
+| Element     | Action    | Result    | Feedback                 |
+| ----------- | --------- | --------- | ------------------------ |
+| Primary CTA | Click/tap | [outcome] | [visual/haptic feedback] |
+| [element]   | [action]  | [result]  | [feedback]               |
+
+## Cross-references
+
+- Anchor selection: `31_anchor.md`
+- State coverage: see `../03_Story-Workshop.md` Design Direction Summary

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/50_review_bundle.md

@@ -0,0 +1,31 @@
+# Review Input Bundle
+
+## Purpose
+
+Consolidate all sidecar artifacts into a review-ready bundle for design reviewers.
+
+## Bundle Contents
+
+| Artifact           | Path                                 | Status                    |
+| ------------------ | ------------------------------------ | ------------------------- |
+| Strategy           | `uiux/10_strategy.md`                | [draft/reviewed/approved] |
+| Usability axis     | `uiux/20_eval_axis_usability.md`     | [draft/reviewed/approved] |
+| Consistency axis   | `uiux/21_eval_axis_consistency.md`   | [draft/reviewed/approved] |
+| Accessibility axis | `uiux/22_eval_axis_accessibility.md` | [draft/reviewed/approved] |
+| Delight axis       | `uiux/23_eval_axis_delight.md`       | [draft/reviewed/approved] |
+| Comparison         | `uiux/30_comparison.md`              | [draft/reviewed/approved] |
+| Anchor selection   | `uiux/31_anchor.md`                  | [draft/reviewed/approved] |
+| Screen contracts   | `uiux/40_contracts.md`               | [draft/reviewed/approved] |
+
+## Review Checklist
+
+- [ ] Strategy aligns with surface type and project constraints
+- [ ] All 4 invariant scoring axes defined with measurable criteria
+- [ ] 2+ options compared against all axes
+- [ ] Anchor screen selected with rationale
+- [ ] Screen contracts cover all 4 required states (empty/loading/error/populated)
+- [ ] Critique loop entries addressed or deferred with rationale
+
+## Reviewer Notes
+
+<!-- Reviewer feedback is captured here during the review cycle. -->

package/assets/init/.qfai/assistant/skills/qfai-discussion/templates/uiux/60_critique_loop.md

@@ -0,0 +1,23 @@
+# Critique Loop Tracking
+
+## Purpose
+
+Track iterative design critique rounds and resolutions.
+
+## Critique Log
+
+| Round | Source                    | Finding               | Severity          | Resolution                             | Status                   |
+| ----- | ------------------------- | --------------------- | ----------------- | -------------------------------------- | ------------------------ |
+| 1     | [reviewer/self/automated] | [finding description] | [high/medium/low] | [resolution or rationale for deferral] | [open/resolved/deferred] |
+
+## Resolution Summary
+
+- Total findings: 0
+- Resolved: 0
+- Deferred: 0 (with rationale in Deferred column)
+- Open: 0
+
+## Cross-references
+
+- Review bundle: `50_review_bundle.md`
+- Design decisions: see `../03_Story-Workshop.md` Design Direction Summary