Project Moc Generator

Input Requirements

The skill expects:

• Project root access: Ability to read codebase structure and files
• docs/ folder: Output location where MOC files will be created
• docs/devlog/ folder (optional but recommended): Contains devlog entries, interstitial notes, or ongoing work documentation
• Source code access: To analyze actual implementation and extract feature details

Optional context that improves output:

• README.md or project documentation
• Architecture diagrams or notes
• CHANGELOG or version history
• Package configuration files (package.json, requirements.txt, etc.)

Output Formats

All output is written to the docs/moc/ folder in your project:

Project MOC Structure

docs/
└── moc/
    ├── README.md           # Main entry point (auto-renders on GitHub!)
    ├── features.md         # Feature overview and catalog
    ├── architecture.md     # Architecture and design decisions
    ├── components.md       # Component maps and details
    └── decisions.md        # Architectural decision records (optional)

Benefits of this structure:

• Single moc/ folder keeps all MOC files together
• README.md auto-renders when you navigate to docs/moc/ on GitHub
• Lowercase filenames follow markdown conventions
• No _MOC suffix needed (folder context makes it clear)
• Won't conflict with existing docs/ files

Frontmatter Format

Every generated MOC includes:

---