skill-decomposer

Skill decomposition isolates a single reusable capability from a larger source by mapping scope, identifying candidates, and defining boundaries. This prevents over-conversion and ensures the extracted capability remains decoupled from local machinery.

Isolating reusable sigils from a source with multiple capabilities requires mapping candidate discovery points and making boundary decisions. You validate the extracted candidate to ensure it is coherent and not source-coupled before generating a handoff package.

Preparing a handoff package for skill-transcriptor requires executing map, extract, boundary, and handoff steps on the source. The process outputs a structured decomposition report and a transferable package plan for the downstream transcriptor.

Yes, a SKILL.md frontmatter at the root is required to execute the map, extract, boundary, and handoff steps. This frontmatter provides the necessary structural context to initiate the decomposition process and generate the handoff package.

You should avoid a decomposition approach when the source contains a single clear capability or when boundary decisions are unambiguous. Decomposition is designed specifically for tangled sources with multiple potential sigils and unclear boundary demarcations.