Implementation Review Plan¶
← Previous
Verification Precheck
Current
Implementation Review Plan
Next →
Implementation Readiness Summary
Template purpose¶
Use this template to define how implementation work will be reviewed.
Project¶
<Project name>
Document control¶
| Field | Value |
|---|---|
| Artifact owner | <owner> |
| Primary reviewers | <reviewers> |
| Status | <draft / in review / accepted / revised> |
| Last updated | <YYYY-MM-DD> |
| Related Engineering Stage | ES-106 — Implementation Readiness |
| Project workspace target | docs/project-workspace/implementation/implementation_review_plan.md |
Review scope¶
<Describe what implementation review must cover.>
Review checklist¶
- [ ] Work traces to design and requirements.
- [ ] Guardrails are preserved.
- [ ] Tests or checks are included.
- [ ] Evidence-producing behavior is implemented.
- [ ] Access-control behavior is reviewed.
- [ ] AI-assisted code is disclosed and reviewed.
- [ ] Failure behavior matches design.
- [ ] Documentation or evidence is updated.
- [ ] Security and privacy-sensitive changes are reviewed.
- [ ] Known gaps are declared.
Reviewer roles¶
| Review Area | Reviewer | Evidence |
|---|---|---|
<area> |
<reviewer> |
<evidence> |
Pull request evidence¶
| Evidence | Required? | Notes |
|---|---|---|
| Work item reference | <yes / no> |
<notes> |
| Design reference | <yes / no> |
<notes> |
| Verification result | <yes / no> |
<notes> |
| Guardrail confirmation | <yes / no> |
<notes> |
| AI assistance disclosure | <yes / no / if applicable> |
<notes> |
| Evidence update | <yes / no> |
<notes> |
Review decision options¶
| Decision | Meaning |
|---|---|
| Accept | <meaning> |
| Accept with follow-up | <meaning> |
| Request changes | <meaning> |
| Block | <meaning> |
Review checklist¶
- [ ] Review scope is clear.
- [ ] Reviewers are assigned.
- [ ] PR evidence expectations are clear.
- [ ] AI-assisted work review is defined.
- [ ] Guardrail review is defined.
- [ ] Decision options are clear.