Create Requires Module

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

What Requires Does

requires establishes a build ordering between modules. The required module is built before the current one. This does not necessarily mean the current module extends or depends on the required module's code — it may be completely independent. The requires relationship simply ensures the build order is correct.

When this module is rendered:

• The required module's generated code (plain_modules/<required_module>) is copied as the starting point.
• The required module's ***functional specs*** become visible as previous functional specs.
• Only exported_concepts from the required module are available (not its full definitions).

Use requires for:

• Ensuring a module is built after another in the build chain
• Building on top of an existing module's functionality
• Extending a base module with additional features

If you only need shared definitions and reqs (no functional specs, no generated code), use import instead — see the create-import-module skill.