slice-decomposition

To decide on feature decomposition for a Flutter application, evaluate whether the functionality represents an independent flow or extends an existing state machine. If the feature requires isolated state management and separate multi-step workflows, create a new slice; otherwise, extend the existing slice.

Slice decomposition in clean architecture is the process of splitting features into the right slices by reasoning about independent flows, bounded contexts, and state machines. It organizes modular application architectures by ensuring independent screens and overlapping workflows remain structurally separated.

Shared code should be used when logic needs to be triggered from multiple independent flows, whereas slice-specific logic should stay isolated within a bounded context. Evaluate if the abstraction serves a single slice or supports cross-cutting operations before promoting it to shared code.

Yes, feature decomposition applies specifically to planning conversations about multi-step workflows with overlapping operations. It uses boundary-aware reasoning to separate independent flows, ensuring operations triggered from different places do not overload a single slice or mix with shared code.

The best way to handle this in modular application architectures is to separate the edit flow into its own slice while keeping the delete action reusable. This prevents overloading one slice and ensures the delete operation can be triggered from different places via shared code.