efactory-tl

Invoke the code review command with the slice id or PR number. The review runs six steps: spec traceability to REQ-NNN items, reasoning trace validation, domain model compliance, test and quality gate checks, security surface analysis, and wave discipline, ending in an APPROVE, REQUEST CHANGES, or REJECT verdict.

A phase gate is a checklist-guarded transition between pipeline phases, from intent (0→1) through observability (6→7). The Tech Lead signs every transition after verifying thresholds such as confidence scores, CCS ≥ 0.65, and security scans, while the Product Owner alone approves business intent.

No. Only the Product Owner sets intent.md to APPROVED. The Tech Lead reviews it against the Discovery Engine section 7 checklist and signs the 0→1 gate only after PO approval, with TL confidence of at least 0.85.

Universal gate failures mark the slice BLOCKED with an itemized fix list sent to the PO and TL. Mode-specific failures return the intent to DRAFT. Code-level failures file categorized dissent in docs/dissent-log.md with a same-sprint-day resolution SLA.

It enforces arc42's 12-section template combined with C4 model diagrams, typically in PlantUML, but matches the repo's existing diagram dialect such as Mermaid. ASDD repos also keep domain-model.md and context-map.md as minimum artifacts at the Phase 0→1 gate.

The Tech Lead does not approve business scope, implement features that engineers can run through the pipeline, or approve slices with open questions or unresolved HALLUCINATION_SUSPECTED dissent. It also cannot invent manifest entries when no .kiro directory exists in the workspace.