Use this skill when the user mentions "mastermind", "track projects", "project overview", "sync sessions", "project progress", or wants to manage multiple ongoing projects from a central location.
/plugin marketplace add mconcat/mastermind/plugin install mconcat-mm@mconcat/mastermindThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/report-properties.mdreferences/vault-structure.mdUse this skill when the user mentions "mastermind", "track projects", "project overview", "sync sessions", "project progress", or wants to manage multiple ongoing projects from a central location.
Trust the specifications. Do NOT verify documented structures.
All mastermind commands include complete specifications for:
When executing a command:
Anti-patterns:
head/grep to "understand" file formats already documentedls to "discover" directory structures already specifiedThe specifications are authoritative. If something doesn't match, report the discrepancy - don't try to "figure out" the actual format through exploration.
Mastermind is a markdown-based framework for tracking progress across multiple projects via Claude Code session analysis. It maintains a central "vault" with project specs, session reports, and daily digests.
Vault: The mastermind directory containing all tracking data. Location configured in ~/.claude/mastermind.local.md.
Projects: Registered directories that mastermind monitors for Claude Code session activity.
Session Reports: Property-based narrative reports generated from Claude Code conversation history, capturing decisions, issues, learnings, and user preferences.
Specs: Source-of-truth documents defining each project's purpose, scope, and direction.
[vault]/
├── config.yaml # Project registry
├── state/
│ └── sync-state.yaml # Sync tracking (last synced timestamps)
├── projects/
│ └── [project-name]/
│ ├── spec.md # Project specification
│ ├── status.md # Current state summary
│ └── sessions/
│ └── YYYY-MM-DD-descriptive-title.md # Session reports
└── daily/
└── [YYYY-MM-DD].md # Cross-project daily digests
Session filename format: YYYY-MM-DD-descriptive-title.md
2026-01-15-implementing-jwt-authentication.md| Command | Purpose |
|---|---|
/mm:init <vault-path> | Initialize a new vault (first-time setup) |
/mm:add <name> <path> | Register a new project to monitor |
/mm:sync [project] | Analyze new Claude Code sessions and generate reports |
/mm:overview | Dashboard of all monitored projects |
/mm:status <project> | Deep dive on one project |
/mm:plan [project] | Create or update a project spec |
/mm:daily | Generate today's cross-project digest |
/mm:init ~/path/to/vault/mm:add my-project /path/to/project/mm:sync/mm:plan my-projectThe vault path is stored in ~/.claude/mastermind.local.md (created by /mm:init):
# Mastermind Configuration
vault: /path/to/your/mastermind/vault
All commands work from any directory - they read the vault location from this config file.
Reports are narrative documents (like blog posts) that capture these properties when present:
/mm:init ~/your/vault to create vault/mm:add <name> <path> for each project to track/mm:sync (from any directory)/mm:plan/mm:dailyFor detailed specifications, see:
references/vault-structure.md - Complete vault formatreferences/report-properties.md - Session report property definitionsThis skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.