Cursor rule

1---
2description: "Deterministic traceability quality gate — reads coverage matrix + blind-spot data, applies decision rules with oracle confidence downgrade, emits PASS/CONCERNS/FAIL/WAIVED verdict. Use before release-branch to gate merges on traceability."
3alwaysApply: false
4---
5 
6# Gate Trace
7 
8Deterministic quality gate that combines traceability coverage and blind-spot data into a single PASS/FAIL/CONCERNS/WAIVED decision before release.
9 
10## Decision Rules
11 
12| Rule | Condition | Verdict |
13|------|-----------|---------|
14| R1 | Any undone story with 0 code tags | FAIL |
15| R2 | Any story done but no verify evidence | CONCERNS |
16| R3 | P0 story (top WSJF quartile) with 0% coverage | FAIL |
17| R4 | Overall coverage < 60% | CONCERNS |
18| R6 | P0 story + eNN-TEST_PLAN_LATEST.md exists + zero SC-eNNsYY-P0-* in test files | CONCERNS |
19| R5 | Overall ≥ 80% + no critical gaps + all verify → PASS | PASS |
20 
21## Oracle Confidence Downgrade
22 
23TEA-inspired: if trace links rely on heuristics rather than explicit tags, confidence drops.
24 
25| Heuristic Ratio | Downgrade |
26|-----------------|-----------|
27| > 50% links from heuristics (file-name or task-reference) | One level (PASS→CONCERNS, CONCERNS→FAIL) |
28| > 80% links from heuristics | Two levels (PASS→FAIL, CONCERNS→FAIL) |
29 
30## Process
31 
321. **Pre-flight:** Ensure `scripts/trace-stories.sh --json` has been run (produces `specs/traceability-matrix.json`). If not present, run it.
332. Ensure `scripts/check-blind-spots.sh` has been run (produces `specs/blind-spots.json`). If not present, run it.
343. Read `specs/traceability-matrix.json` and `specs/blind-spots.json`.
354. Apply decision rules R1–R5 in order (first match wins).
365. Apply oracle confidence downgrade based on the heuristic link ratio from the matrix's `oracle_stats`.
376. **Drift check (e39s03):** If `specs/drift-report.json` exists and has suspect links, mark verdict as CONCERNS with note: "Drift detected — some implementing files are newer than their specs. Run scripts/check-spec-drift.sh for details."
387. Output verdict + rationale to stdout.
398. **Adversarial refute check (e45s32):** Before emitting PASS, attempt to **refute** the verdict — list at least one concrete traceability gap that would block merge if it were real. If the gap is real, downgrade the verdict. Rubber-stamping is prohibited; every PASS must survive one refutation attempt.
409. **Completeness critic (e45s05)** — Run adversarial gap-finding:
41 
42```bash
43bash scripts/lib/completeness-critic.sh
44```
45 
46Classify output as **BLOCKER / WARNING / FILLED**. **BLOCKER overrides any PASS verdict → FAIL.** Append critic summary to rationale.
4710. Update `specs/execution-status.yaml` with gate-trace result.
48 
49## Verdict Semantics
50 
51| Verdict | Meaning | Action |
52|---------|---------|--------|
53| PASS | All gates satisfied | Proceed with merge |
54| CONCERNS | Non-critical issues found | Requires explicit human override in `state.yaml` |
55| FAIL | Critical traceability gap | Block merge — fix gap first |
56| WAIVED | Cannot evaluate (missing inputs) | Skip gate — data not available |
57 
58## Output Format
59 
60```yaml
61gate_trace:
62  verdict: PASS|CONCERNS|FAIL|WAIVED
63  generated_at: "<ISO 8601>"
64  rationale: "<human-readable explanation>"
65  heuristic_ratio: <0.0–1.0>
66  downgrade_applied: <true|false>
67```
68 
69## Integration Points
70 
71- **release-branch SKILL.md** — pre-PR gate (FAIL blocks merge).
72- **sync-skills.yml** — runs `trace-stories.sh --strict` as its "Traceability gate" step (FAIL
73  blocks pipeline), which shares this skill's coverage data (`traceability-matrix.json`) but
74  does not invoke a gate-trace PASS/CONCERNS/FAIL/WAIVED verdict directly.
75- **verify-work SKILL.md** — runs blind-spot checks; gate-trace consumes the result.
76 
77## References
78 
79- BMAD TEA traceability approach (market survey 2026-07-02).
80- scripts/trace-stories.sh (e38s01) — produces traceability-matrix.json.
81- scripts/check-blind-spots.sh (e38s04) — produces blind-spots.json.
82- specs/execution-status.yaml — output target for gate result.
83 
84## Handoff
85 
86Gate: READY → next: release-branch (final step before merge)
87Writes: state.yaml handoff.next_skill = release-branch
88 
89## Verify
90 
91→ verify: `test -x scripts/run-gate-trace-verify.sh && bash scripts/run-gate-trace-verify.sh --self-test && echo OK`
92