What This Skill Does

This skill compares two or more band-tagged frameworks and produces a framework-neutral topic matrix as its primary output. Its input is the output of the Developmental Band Translator skill, one output per framework. Every framework is treated as an equal participant: topics present in any framework appear as rows in the matrix, and a framework's absence at a given theme × band is shown as an explicit ", " gap, not an omission. This makes the primary output useful for identifying what any framework lacks, not just where frameworks agree.

If a reference framework is also supplied, the skill additionally produces a secondary reference-centric crosswalk document, a Markdown document that a teacher or PLC facilitator can open and use directly for a professional discussion, organised under five required sections: Convergence, Divergence, Unique Content, Sequencing Differences, and Questions for PLC. The secondary document and its associated CSV are only produced when a reference framework is supplied.

The skill is deliberately additive, not reductive. It does not merge the frameworks into a single synthesised schema. It does not rewrite statements into a common voice. Each framework's content appears in the output in the original words the framework used, attributed by name. This is a design decision grounded in Martone & Sireci (2009): alignment work that hides framework distinctiveness loses the very information a PLC needs to make a planning decision.

The skill is opinionated about the distinction between "cross-framework agreement" and "cross-framework coincidence". Two frameworks addressing the same topic at the same band is convergence only if they also treat the topic at comparable depth and intent. Where that is unclear, the skill flags the pairing as apparent convergence, teacher confirmation needed rather than silently counting it as agreement.

Evidence Foundation