<< All versions

Skill v1.0.1

currentAutomated scan100/100
danielvm-git/bigpowers/gate-trace

+3 new

──Details
PublishedSeptember 13, 2026 at 12:52 PM
Content Hashsha256:097c31ec960861ce...
Git SHAcbff374ee2d4
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 4.3 KB)
SKILL.md4.3 KBactive
SKILL.md · 99 lines · 4.3 KB

version: "1.0.1"

story: e80s01

story: e45s05

name: gate-trace description: "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."

story: e38s06

story: e45s32

model: haiku effort: light


Gate Trace

Deterministic quality gate that combines traceability coverage and blind-spot data into a single PASS/FAIL/CONCERNS/WAIVED decision before release.

Decision Rules

RuleConditionVerdict
R1Any undone story with 0 code tagsFAIL
R2Any story done but no verify evidenceCONCERNS
R3P0 story (top WSJF quartile) with 0% coverageFAIL
R4Overall coverage < 60%CONCERNS
R6P0 story + eNN-TEST_PLAN_LATEST.md exists + zero SC-eNNsYY-P0-* in test filesCONCERNS
R5Overall ≥ 80% + no critical gaps + all verify → PASSPASS

Oracle Confidence Downgrade

TEA-inspired: if trace links rely on heuristics rather than explicit tags, confidence drops.

Heuristic RatioDowngrade
> 50% links from heuristics (file-name or task-reference)One level (PASS→CONCERNS, CONCERNS→FAIL)
> 80% links from heuristicsTwo levels (PASS→FAIL, CONCERNS→FAIL)

Process

  1. Pre-flight: Ensure scripts/trace-stories.sh --json has been run (produces specs/traceability-matrix.json). If not present, run it.
  2. Ensure scripts/check-blind-spots.sh has been run (produces specs/blind-spots.json). If not present, run it.
  3. Read specs/traceability-matrix.json and specs/blind-spots.json.
  4. Apply decision rules R1–R5 in order (first match wins).
  5. Apply oracle confidence downgrade based on the heuristic link ratio from the matrix's oracle_stats.
  6. 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."
  7. Output verdict + rationale to stdout.
  8. 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.
  9. Completeness critic (e45s05) — Run adversarial gap-finding:
bash
bash scripts/lib/completeness-critic.sh

Classify output as BLOCKER / WARNING / FILLED. BLOCKER overrides any PASS verdict → FAIL. Append critic summary to rationale.

  1. Update specs/execution-status.yaml with gate-trace result.

Verdict Semantics

VerdictMeaningAction
PASSAll gates satisfiedProceed with merge
CONCERNSNon-critical issues foundRequires explicit human override in state.yaml
FAILCritical traceability gapBlock merge — fix gap first
WAIVEDCannot evaluate (missing inputs)Skip gate — data not available

Output Format

yaml
gate_trace:
verdict: PASS|CONCERNS|FAIL|WAIVED
generated_at: "<ISO 8601>"
rationale: "<human-readable explanation>"
heuristic_ratio: <0.0–1.0>
downgrade_applied: <true|false>

Integration Points

  • release-branch SKILL.md — pre-PR gate (FAIL blocks merge).
  • sync-skills.yml — runs trace-stories.sh --strict as its "Traceability gate" step (FAIL

blocks pipeline), which shares this skill's coverage data (traceability-matrix.json) but does not invoke a gate-trace PASS/CONCERNS/FAIL/WAIVED verdict directly.

  • verify-work SKILL.md — runs blind-spot checks; gate-trace consumes the result.

References

  • BMAD TEA traceability approach (market survey 2026-07-02).
  • scripts/trace-stories.sh (e38s01) — produces traceability-matrix.json.
  • scripts/check-blind-spots.sh (e38s04) — produces blind-spots.json.
  • specs/execution-status.yaml — output target for gate result.

Handoff

Gate: READY → next: release-branch (final step before merge) Writes: state.yaml handoff.next_skill = release-branch

Verify

→ verify: test -x scripts/run-gate-trace-verify.sh && bash scripts/run-gate-trace-verify.sh --self-test && echo OK

← v1.0.0All versions