Skip to content
Get packs

Module Governance

Sets up local agent rules and domain-doc links for a business module without duplicating project docs

Source Download skill
Repository
affaan-m/ECC
Stars
295,127
Licence
MIT
Files
2 files

What it does

When you start a new business module or change what a module is responsible for, this skill guides the agent to read the project's existing rules, glossary, contracts and decisions, then add only the minimal local instruction file and links that are genuinely missing. It deliberately avoids creating documents for simple bug fixes, styling, or read-only discussions, and it asks for confirmation on ambiguous business rules instead of inventing them.

Great for

  • Engineering teams maintaining a large codebase split into business modules with agent instructions
  • Developers who want documentation links checked against the code before a module change is declared done
  • Teams already using the ECC workflow skills it references

Skip it if

  • Small projects or single-directory tasks, since the skill's own guidance says not to create documents there (it adds overhead without benefit)
  • Anyone expecting it to auto-generate full DDD documentation; the skill says it is not a documentation generator
  • Users without the referenced ECC skills installed, because most of its steps depend on them and will not work as written

Try asking

  • “Implement an inventory module and set up its local agent instructions and glossary links”
  • “Should payments become a separate module? Explain the boundary options without writing files”
  • “Audit the documentation for the orders module and report broken links”
  • “Fix the inventory badge color (the skill should stay out of the way and create no documents)”
Step-by-step guide: how to use Module GovernanceInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    module-governance.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip module-governance.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip module-governance.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Name the module directory explicitly so the agent scopes the audit with --module correctly
  • Ask for a read-only audit or design discussion first if you are unsure whether files should be created
  • Confirm the agent's list of created or changed files before accepting, since it is instructed to write only authorized records

What's inside

  • agents/openai.yaml
  • SKILL.md

Redistributed unmodified from affaan-m/ECC under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-11-02. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.