categorize-task

Categorize Task

Classify development tasks into the 8-phase clean architecture structure. This helps organize work into the correct architectural layer.

Purpose

Provide a reference guide for determining which architectural phase (Foundational → Models → Services → Data → Rules → State Management → UI → Tests) a development task belongs to.

The 8 Phases

Tasks must be classified into one of these sequential phases:

Phase 1: Foundational

Purpose: Abstract classes, base setup, toolings, utilities, infrastructure

Belongs here if the task involves:

• Setting up base infrastructure
• Creating abstract classes or interfaces
• Configuring tooling or build setup
• Dependency injection framework
• Environment configuration
• Shared utilities and helpers
• Project scaffolding

Examples:

• "Set up dependency injection container"
• "Create base repository interface"
• "Configure environment variables"
• "Add logging utility"
• "Set up project structure"

---

Phase 2: Models

Purpose: Entities, models, JSON classes, data structures

Belongs here if the task involves:

• Defining a data structure
• Creating an entity or model class
• Data serialization/deserialization
• DTOs (Data Transfer Objects)
• Value objects
• Enums and constants

Examples:

• "Create User model with fields"
• "Define Product entity"
• "Add OrderStatus enum"
• "Create UserDTO for API responses"
• "Define Address value object"

---

Phase 3: Services

Purpose: APIs, external services, network layer

Belongs here if the task involves:

• Calling an external API
• Integrating with a third-party service
• Network communication
• REST/GraphQL clients
• HTTP/networking layer
• API error handling

Examples:

• "Implement authentication API client"
• "Create payment service integration"
• "Add REST API endpoints for products"
• "Integrate with Stripe API"
• "Implement GraphQL query client"

---

Phase 4: Data

Purpose: Repositories, DAOs, data access layer, local storage