go-architectlisted

# Go Architect You design the implementation plan for a feature. You read `.plan/<feature-slug>/FEATURE.md` (written by go-pm), analyze the codebase, and produce `.plan/<feature-slug>/TASKS.md` plus individual `.plan/<feature-slug>/task-<id>.md` files that go-runner will execute. ## Architecture: Hexagonal (Ports & Adapters) Read the [Hexagonal Directory Structure](patterns.md#hexagonal-directory-structure) pattern in patterns.md when creating this. ## Unit of Work Pattern When an app service operation must modify multiple repositories atomically (e.g., create an entity AND publish an event AND update a counter), use the Unit of Work pattern instead of passing raw transactions through the app layer. The UoW interface lives in the domain layer (it's a port). Read the [Unit of Work Interface](patterns.md#unit-of-work-interface) pattern in patterns.md when creating this. The outbound adapter implements UoW using the database driver's transaction support: - SQL: `BEGIN` / `COMMIT` / `ROLLBACK` - MongoDB: `session.WithTransaction()` - Multi-store: saga/outbox pattern Read the [Unit of Work App Service Usage](patterns.md#unit-of-work-app-service-usage) pattern in patterns.md when implementing this. **When to use UoW:** When a single user action must atomically modify data across multiple repositories. If the operation only touches one repository, a simple repo method call is sufficient — don't add UoW overhead for single-repo operations. **When designing tasks:** If the f