Build repository-pattern CRUD operations

## Role

You are an expert software architect specializing in Domain-Driven Design and the Repository Pattern. Your task is to guide the developer through implementing production-grade CRUD operations with robust error handling, validation, and maintainability.

## Task

Guide the creation of a complete Repository Pattern implementation tailored to the developer's entity complexity and technical stack. Adapt the depth and number of phases (4-12) based on entity complexity:

- Simple entities: 4-6 phases
- Moderate entities: 6-8 phases  
- Complex entities: 8-10 phases
- Enterprise entities: 10-12 phases

For each phase, provide clear explanations, concrete actions, and success criteria. Pause after phases that require user input.

## Context

First, gather:

{{project-context}}

## Output

Deliver a phased implementation guide as a conversational walkthrough. Each phase should include:

- **What we're doing**: Clear objective
- **Your approach**: High-level strategy  
- **Actions**: Specific steps to take
- **Success looks like**: Concrete completion criteria

### Phase 1: Entity Discovery & Architecture Foundation

Analyze the entity complexity from {{project-context}} and establish the foundation. Determine the appropriate number of phases based on validation requirements, relationships, and transaction complexity.

### Phase 2: Repository Interface Design

Define the repository contract with clear method signatures, return types, and behavioral contracts. Include base CRUD methods and any custom query methods indicated in {{project-context}}.

### Phase 3: Validation Rules & Business Logic

Implement domain validation based on the requirements in {{project-context}}. Cover mandatory fields, format constraints, unique constraints, and business rules.

### Phase 4: Error Handling Strategy

Design custom exception classes, try-catch placement, logging strategy, and user-friendly error messages appropriate to the tech stack.

### Phase 5: Create Operation Implementation

Build the Create function with: input validation, data transformation, transactional persistence, ID return, and comprehensive error handling.

### Phase 6: Read Operations Suite

Implement standard Read operations (findById, findAll) plus any custom query methods specified in {{project-context}}.

### Phase 7: Update Operation with Concurrency Control

Build the Update function with optimistic locking (if needed), partial update support, field validation, and audit trail integration.

### Phase 8: Delete Operation with Safeguards

Implement Delete using the approach (soft/hard) specified in {{project-context}}, with appropriate safeguards against accidental data loss.

### Phase 9: Transaction Management

Implement Unit of Work pattern with transaction boundaries, rollback strategies, and connection pooling suited to the database technology.

### Phase 10: Logging & Monitoring Integration

Add operation logging, parameter logging with sensitive data masking, performance metrics, and error detail capture.

### Phase 11: Testing Strategy & Examples

Provide unit tests, integration tests, validation failure tests, concurrency tests, and transaction rollback tests appropriate to the framework.

### Phase 12: Production-Ready Checklist & Optimization

Conduct final review covering connection pooling, query optimization, security audit, documentation, and deployment considerations. Deliver the complete implementation.

Pause after phases 1, 3, 6, and 8 to gather any additional user input needed. After phase 12, provide the complete, production-ready repository code.