magnus919_agent-skills/spec-driven-development/templates/VERIFICATION.md

Verification Report: <Project / Feature Name>

Source Specification

• Spec: SPEC.md (version <x.y.z>)
• Spec review gate: Approved / Conditions
• Plan reference: TASK-PLAN.md (version <x.y.z>)
• Verification author:
• Verification date:
• Verification mode: automated / manual / interactive

L1: Summary

Metric	Value
Total ACs tested
Pass
Fail
Blocking
Critical
Minor
Compliance score	<XX.X%>
Gate Verdict	APPROVED / CONDITIONS / REJECTED

Gate Verdict Rationale

<One paragraph explaining the verdict based on severity rules: 0 BLOCKING + 0 CRITICAL = APPROVED; 0 BLOCKING + <=2 CRITICAL with remediation plans = CONDITIONS; any BLOCKING = REJECTED; <90% pass rate without exception = REJECTED.>

L2: Verification Matrix

Per-Story Results

Story / Feature	ACs	Pass	Fail	Blocking	Verdict
					PASS / FAIL
					PASS / FAIL

Verification Dimensions Coverage

Dimension	Score	Notes
Functional Correctness	<N/N>
Behavioral Completeness	<N/N>
Contract Compliance	<N/N>
Non-Functional Requirements	<N/N>
Negative Testing	<N/N>

L3: Failure Dossiers

:

• Severity: BLOCKING / CRITICAL / MINOR / INFO
• Story:
• Verification dimension: <Functional / Behavioral / Contract / NFR / Negative>

Expected behavior (from spec):

Actual behavior (from implementation):

Evidence: <Test output, code inspection, observation>

Remediation recommendation: <What to fix, why this severity, how to verify the fix passes the AC>

---

:

...

SOURCES

Reference	Description
SPEC.md	Source specification document
	Section X — user story for this AC

Revision History

Version	Date	Author	Change
1.0			Initial verification