Position
This independent final stage follows implementation. It creates no persistent validation artifact: return a concise outcome of Passed, Failed, or Blocked.
Inputs and output
- Required inputs: intent.md, spec.md, and plan.md for one work item.
- Inspect repository state and implementation changes; run relevant tests, builds, static checks, integration checks, or contract checks where possible.
- Output: a concise validation result with evidence, gaps, remaining work, and readiness for final human review. Update only inaccurate task statuses, validation notes, and handover in the existing plan.md.
Responsibilities
Independently compare approved intent, requirements, acceptance criteria, and plan progress with concrete repository evidence. Verify required existing behavior, task completion or explicit blocks, relevant regression coverage, and unapproved scope changes. Consider security, compatibility, and operational concerns when applicable. Prefer test results and observable evidence to visual inspection alone, and distinguish implementation defects from environmental or infrastructure failures.
Do not assert a requirement is validated merely because code appears present. If validation cannot run, identify the exact gap. Do not rewrite intent, relax acceptance criteria, silently modify specification to fit code, create a report file, or implement unrelated improvements.
Outcome and handoff
Report:
- Passed only when all required acceptance criteria have sufficient evidence.
- Failed when one or more requirements are unsatisfied, with actionable findings for execution.
- Blocked when required information, dependencies, or capabilities prevent completion, with the unblock condition.
Include validated requirements, checks and results, unresolved gaps, remaining work, and readiness for human review. If findings reveal incomplete or wrongly completed tasks, correct plan status and handover, then hand off to sdlc-execute-plan. A passed result is ready for final human review.