https://specdd.ai/how-to/code-review-and-governance/Spec-driven development code review and governance guides for pull requests, spec updates, agent-generated specs, write authority, architecture reviews, and boundary changes.Hugoen-ushttps://specdd.ai/how-to/code-review-and-governance/how-to-review-a-specdd-pull-request/https://specdd.ai/how-to/code-review-and-governance/how-to-review-a-specdd-pull-request/Review a spec-driven development pull request by checking changed files against write authority, behavior rules, Must not, Forbids, tasks, Done when, and verification.https://specdd.ai/how-to/code-review-and-governance/how-to-require-spec-updates-in-code-review/https://specdd.ai/how-to/code-review-and-governance/how-to-require-spec-updates-in-code-review/Require SpecDD spec updates in code review for spec-driven development when behavior, ownership, dependencies, public contracts, tasks, or completion criteria change.https://specdd.ai/how-to/code-review-and-governance/how-to-review-agent-generated-specs/https://specdd.ai/how-to/code-review-and-governance/how-to-review-agent-generated-specs/Review agent-generated SpecDD specs for spec-driven development by checking assumptions, local authority, old behavior, Must not, Forbids, tasks, Done when, and syntax before implementation.https://specdd.ai/how-to/code-review-and-governance/how-to-use-specdd-in-architecture-reviews/https://specdd.ai/how-to/code-review-and-governance/how-to-use-specdd-in-architecture-reviews/Use spec-driven development in architecture reviews by turning accepted decisions into reviewed local specs with ownership, boundaries, dependencies, tasks, and Done when criteria.https://specdd.ai/how-to/code-review-and-governance/how-to-define-write-authority-for-agents/https://specdd.ai/how-to/code-review-and-governance/how-to-define-write-authority-for-agents/Define spec-driven development write authority for agents with Can modify, Owns, Can read, References, Must not, and Forbids so changes stay inside the intended boundary.https://specdd.ai/how-to/code-review-and-governance/how-to-create-a-specdd-review-checklist/https://specdd.ai/how-to/code-review-and-governance/how-to-create-a-specdd-review-checklist/Create a spec-driven development review checklist that covers spec chain, write authority, behavior, boundaries, tasks, verification, risk, and review outcome.https://specdd.ai/how-to/code-review-and-governance/how-to-reject-a-spec-driven-change-constructively/https://specdd.ai/how-to/code-review-and-governance/how-to-reject-a-spec-driven-change-constructively/Reject a spec-driven change constructively by naming the violated spec-driven development contract, explaining the risk, and giving the smallest safe path forward.https://specdd.ai/how-to/code-review-and-governance/how-to-review-changes-to-must-not-and-forbids/https://specdd.ai/how-to/code-review-and-governance/how-to-review-changes-to-must-not-and-forbids/Review spec-driven development changes to Must not and Forbids by checking boundary risk, dependency risk, inherited constraints, rationale, alternatives, and verification.https://specdd.ai/how-to/code-review-and-governance/how-to-review-a-spec-only-pull-request/https://specdd.ai/how-to/code-review-and-governance/how-to-review-a-spec-only-pull-request/Review a spec-only spec-driven development pull request by treating .sdd changes as authority changes, checking scope, behavior, tasks, conflicts, and future implementation risk.