aico-backend-task-breakdown

Break down PM story into backend tasks following LAYERED ARCHITECTURE order: Data Models → Database → Repository → Service → API → Validation → Tests. UNIQUE VALUE: Ensures proper dependency order and separation of concerns. Tasks are ordered by architectural layers, not random order. Use this skill when: - Running /backend.tasks command - User asks to "break down story for backend", "create backend tasks", "split into backend tasks" - Have story at docs/reference/pm/stories/ and need organized task list - Need tasks ordered by architectural layers (not random order) - Starting backend work and want organized, layered task list Layer order is CRITICAL: Types/Entities → Migrations → Repository → Service → API → Validation → Tests Output: ALWAYS write to docs/reference/backend/tasks/{story-name}.md