How does it handle infrastructure requirements?

It identifies specific infrastructure needs such as external API definitions, database table schema changes, and Dockerfile modifications.

How does this help with project management?

By creating highly granular tasks, it ensures better tracking, clearer code reviews, and more accurate progress reporting within a development team.

Does it support both frontend and backend development?

Yes, it provides specific structures for frontend tasks (constants, domain, infra) and backend tasks (controller, use case, domain, infra).

What is the Sub-Issue Architect skill?

It is a specialized capability for Claude Code that helps developers break down large features into smaller, manageable sub-issues following Domain-Driven Design (DDD) principles.

Can it be used for non-DDD projects?

While it is optimized for DDD, the logic for creating granular, requirement-based tasks can be adapted to any structured software project.

Sub-Issue Architect

Name: Sub-Issue Architect
Author: uuta

byuuta

•

Collaboration Tools

Breaks down complex implementation requirements into granular, DDD-aligned sub-issues for frontend and backend development.

About

The Sub-Issue Architect skill optimizes your development workflow by automatically decomposing broad requirements into manageable, structured tasks based on Domain-Driven Design (DDD) principles. It provides specific guidance for splitting tasks across frontend (constants, domain, infrastructure) and backend layers (controller, use case, domain, infrastructure), ensuring that every implementation detail—from API definitions to Dockerfile updates—is accounted for and properly scoped for efficient execution.

Key Features

1 GitHub stars
Categorizes frontend work into constants, domain, and infrastructure
Identifies infrastructure needs such as API definitions and table schemas
Adjusts task granularity based on specific project requirements and DevOps needs
DDD-aligned task decomposition for frontend and backend layers
Organizes backend tasks into controller, use case, and domain components

Use Cases

Breaking down a high-level feature request into actionable GitHub or Jira sub-issues
Ensuring clean separation of concerns when planning complex DDD-based refactors
Generating granular task lists for sprint planning and engineering estimation

About

Key Features

1 GitHub stars
Categorizes frontend work into constants, domain, and infrastructure
Identifies infrastructure needs such as API definitions and table schemas
Adjusts task granularity based on specific project requirements and DevOps needs
DDD-aligned task decomposition for frontend and backend layers
Organizes backend tasks into controller, use case, and domain components

Use Cases

Breaking down a high-level feature request into actionable GitHub or Jira sub-issues
Ensuring clean separation of concerns when planning complex DDD-based refactors
Generating granular task lists for sprint planning and engineering estimation