Refactor Module

Always use the skill load-plain-reference to retrieve the ***plain syntax rules — but only if you haven't done so yet.

When to Use

• A module has many functional specs spanning multiple distinct domains or feature areas.
• The module is hard to reason about because unrelated concerns are interleaved.
• New features are difficult to add because the module's scope is too broad.
• The user explicitly asks to split or reorganize a module.

Guiding Principle

The refactoring is purely structural. The combined behavior of the resulting modules must be identical to the original module. No functional spec is added, removed, or weakened. The split is semantic — grouping related specs together — not behavioral.

Input

The .plain file to refactor, plus guidance from the user on the desired grouping (or ask the user to confirm your proposed grouping).