STRICT

Workspace Feature Review Checklist

Gate mode: strict (cross-repo features require approval before implementation)

Workspace Feature Brief

[ ] All affected repositories are identified with clear justification
[ ] Repositories not affected are explicitly excluded with reasoning
[ ] New interfaces are documented with type (REST/Type/Event) and participating repos
[ ] Modified interfaces reference existing contract versions
[ ] Wave ordering respects the dependency graph — no repo sprints before its dependencies
[ ] Repos in the same dependency tier are grouped for parallel execution
[ ] Risks and considerations are identified for cross-repo coordination

[ ] Every new cross-repo interface has a formal contract
[ ] Every contract has full request/response schemas for all endpoints
[ ] Error responses are defined, not just success cases
[ ] Shared types specify exactly one owning repository
[ ] Event contracts specify producer and consumer(s) with payload schemas
[ ] Contract versions follow semver (breaking changes = major bump)
[ ] Contracts are self-contained — implementable without reading other repo code