create-module

/create-module

Command Context

When to Reference DIP-0007

Always reference when:

• Creating module structure
• Validating module.yaml
• Checking required files
• Auditing existing modules

Key decisions this DIP informs:

• Required files (module.yaml, CLAUDE.base.md)
• Settings section format
• Provides section structure
• Hook definitions

Quick Reference

Question	Answer
Required files?	module.yaml, CLAUDE.base.md, .gitignore
Module location?	.datacore/modules/<name>/
Command style?	Conversational, not CLI wrapper
What DIPs govern this?	DIP-0007 (Module Spec), DIP-0002 (Layers)

Agents This Command Invokes

Agent	Purpose
create-module	Scaffold/convert/audit
module-registrar	CATALOG registration

Integration Points

• DIP-0007 - Module specification
• DIP-0002 - Layered context pattern
• Trading module - Reference implementation

---

Create, convert, or audit Datacore modules for spec alignment.

Workflow

Step 1: Understand Intent

If user invoked /create-module with no clear intent, ask:

"What would you like to do?"

1. Create new - Start a new module from scratch with correct structure
2. Convert existing - Turn existing code into a spec-aligned module
3. Audit - Check an existing module for spec alignment and suggest improvements

If intent is clear from context (e.g., "make datacortex a module"), proceed directly.

Step 2: Gather Information

For new module:

• Ask: "What should the module be called?" (lowercase, hyphenated)
• Ask: "What does it do?" (one-line description)
• Ask: "What will it provide?" (commands, agents, templates)
• Default location: .datacore/modules/<name>

For conversion:

• Ask: "Where is the code?" (path to existing project)
• Then same questions as new module

For audit:

• Ask: "Which module?" (path or name)

Step 3: Execute

Invoke the create-module agent with gathered information.