Component Composition Analysis

An interactive, iterative workflow for figuring out the right component structure before writing any code. The output is a locked hierarchy document — file trees, layer assignments, primitive interfaces, and call mappings — that a migration or implementation agent can execute without further design decisions.

Announce at start: "I'm using the obsidian-arrow-composition skill to analyse the component structure."

Hard gate: Do NOT produce a hierarchy document until the user has confirmed the proposed structure. Show file trees, ask questions, iterate. The locked plan is the output of a confirmed conversation, not a first-pass guess.

Process