Architecture Ownership

Use this skill for repo-specific ownership and placement decisions in layered systems.

Focus on long-term canonical ownership, not only the layer where the current bug appears.

Required Discovery

Before deciding ownership:

• Read the repo docs that define architecture, boundaries, or responsibilities.
• Read ADRs or design docs that define runtime flow, request flow, or package boundaries.
• Inspect the top-level project structure to map the repo's concrete module or package names onto the generic layers in this skill.

When docs are incomplete:

• infer the current layer model from the codebase
• state the assumption explicitly
• keep the recommendation aligned to one canonical owner