Planning & architecture

Compare project workflows, module boundaries, and service splitting to decide how responsibilities, checks, and changes fit together.

Search within: Planning & architecture

10 field notes

Architecture boundaries & dependencies

Point source dependencies inward to protect application policy.

Separate application rules from input and storage technologies through ports and replaceable adapters.

Separate stable responsibilities along a simple dependency path.

Deploy capabilities independently when operational independence justifies coordination.

Enforce module ownership while retaining one deployment unit.

Deploy together when simple operations outweigh independent releases.

Use existing agent instructions and checks when extra workflow setup adds little value.

Keep current specifications alongside reviewed change proposals and deltas when evolving agreed behavior.

Track requirements through a specification, plan, tasks, and implementation checks when shared rules need durable agreement.

Use composable development skills when repeatable design, testing, debugging, and review steps are the priority.