mt-publish

MT-Publish: Module Publisher

"Execution should be isolated, but Knowledge must be federated."

This skill helps refine a specific module's knowledge into reusable, context-independent artifacts and publish them to the central Knowledge Base.

When to Use

• User explicitly requests: "KB에 발행해줘", "publish to KB", "모듈 발행해줘"
• User wants to share a specific module's learnings
• Module is mature and worth preserving

For project-wide overview, use mt-master-module instead.

Workflow

Phase 1: Analyze (분석)

Review target module:

cat .memory/modules/<path>/current.md
cat .memory/modules/<path>/decisions.md
cat .memory/modules/<path>/module.md

Identify publishable content:

• Core patterns and architectures
• Reusable solutions
• Key decisions with rationale

Phase 2: Refine (정제)

De-contextualization:

• Remove project-specific paths, variable names
• Generalize code examples
• Make dependencies explicit

Before (project-specific):

from myproject.auth import JWTHandler
db = connect("postgres://myproject:pass@localhost/mydb")

After (generalized):

# Requires: pyjwt, psycopg2
from auth_module import JWTHandler  # Your JWT implementation
db = connect(DATABASE_URL)  # Set via environment variable

Add explicit dependencies:

## Prerequisites
- Python 3.10+
- PostgreSQL 14+
- Required packages: pyjwt, psycopg2

Phase 3: Validate (검증)

Self-check question:

"이 문서만 보고, 빈 프로젝트에서 해당 기능을 구현할 수 있는가?"

If missing information, add:

• Environment variables needed
• Database schema
• External service setup
• Configuration files

Phase 4: Publish (발행)

Preview first:

mpublish <module-name> --dry-run

Publish with metadata:

mpublish <module-name> --tags auth,security,jwt

Verify:

mimport --list

KB Path Structure

mpublish creates files at:

{KB_PATH}/modules/{category}/{project_name}/{module_name}/

Parameter	Default	Description
category	Projects	Use --category Topics for topic-based modules
project_name	Auto-detected	From directory name or config.yaml
module_name	Local module name	e.g., search-system