meta-module-build

Create structured module manifests and file plans using the msdmd convention.

Updated May 23, 2026
One-click install
npx skills add https://github.com/The-Interdependency/skill-lib --skill meta-module-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-module-build
Source: https://github.com/The-Interdependency/skill-lib/tree/main/meta-module-build
Command: npx skills add https://github.com/The-Interdependency/skill-lib --skill meta-module-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for structured metadata declaration and module development by providing a framework for creating module manifests and file plans, ensuring clarity and control over the development process.

Core Features & Use Cases

  • Module Manifests: Facilitates the declaration of module details like purpose, kind, surfaces, and boundaries.
  • File Plan Creation: Generates file plans for implementation PRs to include in PR bodies.
  • Boundary Declarations: Offers guidelines for declaring runtime boundaries such as auth, storage, and network effects.
  • Test and Rollout Configuration: Allows defining tests and rollout strategies for modules.

Quick Start

Initialize a new module using the meta-module-build skill and declare its MODULE_BUILD block in the module's documentation.

Frequently Asked Questions about meta-module-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a module manifest and why do I need one for software architecture?

A module manifest is a structured metadata declaration defining a module's purpose, kind, surfaces, and boundaries. You need one to establish clarity and control over your module development process using a metadata-first approach.

How do I create a file plan for an implementation PR?

To create a file plan for an implementation PR, you declare a structured file plan detailing module boundaries and rollout strategies. This plan is then included directly in the PR body to guide the implementation.

How do I declare runtime boundaries like auth and storage for a new module?

You declare runtime boundaries like auth, storage, and network effects by defining them within your module manifest. This structured declaration ensures all runtime side effects are explicitly documented and controlled.

Does the msdmd convention support test and rollout configuration for module development?

Yes, the msdmd convention supports test and rollout configuration for module development. It allows you to define specific tests and rollout strategies directly within your module manifest declarations.

What is the best way to document module boundaries and metadata before deployment?

The best way to document module boundaries and metadata is using a metadata-first development practice. You initialize a structured module manifest to declare details and generate a corresponding file plan for your PRs.