---
title: "moe"
description: "The Moe skill library: brainstorming, planning, TDD, systematic debugging, code review, worktrees, parallel dispatch, plugin authoring, and more."
canonical: https://agentpluginsdirectory.com/plugins/moe
last-updated: 2026-10-21
---

# moe
The Moe skill library: brainstorming, planning, TDD, systematic debugging, code review, worktrees, parallel dispatch, plugin authoring, and more.
- Slug: moe
- Publisher: Zak Keown
- Repository: https://github.com/zak-keown/moe
- Manifest: plugins/moe/plugin.json
- Version: 0.2.0
- License: MIT AND Apache-2.0
- Category (editorial): agent-tooling
- Skills: 41 (audit-progress, brainstorming, cc-config, cc-plugins, codebase-design, dispatch-agents, docs-update, domain-modeling, execute-plan, extract-requirements, find-duplicates, finish-branch, fix-review, implement-tasks, improve-architecture, iterate, mcp-cli, merge-discipline, moe-dev, moe-discipline, prototype, receive-review, request-review, resolve-conflicts, retrieve-context, review-codebase, run-iteration, scope-core, sdd, sequence-plans, smooth-experience, systematic-debugging, tdd, use-tmux, use-worktrees, using-moe, verify-completion, windows-vm, write-clearly, write-plan, write-skill)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-09-02
- Repository last pushed: 2026-09-04
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/moe
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## Skills

- audit-progress: Use when an iteration has just finished and you need to verify behavior evidence quality in three tiers, deep evidence for current stories, impacted behavior for touched scenarios, and sentinel corpus for high-value regression detection.
- brainstorming: You MUST use this before any creative work, creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- cc-config: Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature, routes to the official documentation instead of guessing, and can cache it locally for offline use
- cc-plugins: Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining), provides streamlined workflows, patterns, and examples for the complete plugin lifecycle
- codebase-design: Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
- dispatch-agents: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- docs-update: Generate or update project documentation verified against the codebase, use when docs are missing, stale, or need an accuracy audit
- domain-modeling: Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
- execute-plan: Use when you have a written implementation plan to execute in a separate session with review checkpoints
- extract-requirements: Use when starting an iterate run on human spec collateral, reads the spec, produces per-epic requirement files with proof obligations and behavior scenario cards with stable IDs.
- find-duplicates: Use when auditing a codebase for semantic duplication, functions that do the same thing but have different names or implementations. Especially useful for LLM-generated codebases where new functions are often created rather than reusing existing ones.
- finish-branch: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
- fix-review
- implement-tasks
- improve-architecture
- iterate
- mcp-cli
- merge-discipline
- moe-dev
- moe-discipline
- prototype
- receive-review
- request-review
- resolve-conflicts
- retrieve-context
- review-codebase
- run-iteration
- scope-core
- sdd
- sequence-plans
- smooth-experience
- systematic-debugging
- tdd
- use-tmux
- use-worktrees
- using-moe
- verify-completion
- windows-vm
- write-clearly
- write-plan
- write-skill

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.