BranchesTags

Repository files navigation

Maister

Structured, standards-aware development workflows for Claude Code

Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.

What You Get

  • Guided workflows for features, bug fixes, enhancements, performance, migrations, research, and product design
  • Auto-discovered standards from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
  • Test-driven implementation with automated planning, incremental verification, and full test suite runs before completion
  • Pause and resume any workflow - state is preserved across sessions
  • Production readiness checks including code review, reality assessment, and pragmatic over-engineering detection

Getting Started

Prerequisites

Installation

/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins

After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.

Initial project setup

Initialize your project to auto-detect coding standards and generate project documentation:

/maister:init

This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.

If you have another project already using Maister, you can reuse its standards as a starting point:

/maister:init --standards-from=/path/to/other-project

First Workflow

/maister:development Add user profile page with avatar upload

Or just discuss your task with Claude and then run:

/maister:development

The plugin picks up context from your conversation - no arguments needed.

How It Works

  1. You describe a task - either as an argument or just in conversation
  2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
  3. You confirm, and it guides you through phases: requirements → spec → plan → implement → verify
  4. At each phase, it asks for your input and decisions
  5. You get tested, verified code with a detailed work log

All artifacts are saved in .maister/tasks/ organized by type and date.

Context-Aware Commands

Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:

You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation

You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"

You can always be explicit when you prefer - arguments and flags simply override the auto-detection.

Supported Workflows

CommandUse When
/maister:developmentFeatures, bug fixes, enhancements
/maister:researchResearch with synthesis and solution design
/maister:performanceOptimizing speed or resource usage
/maister:migrationChanging technologies or patterns
/maister:product-designProduct and feature design

Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.

Quick Commands

For smaller tasks that don't need a full workflow:

CommandUse When
/maister:quick-planYou want a plan with standards awareness before coding
/maister:quick-devYou know what to do - just implement with standards applied
/maister:quick-bugfixQuick TDD-driven bug fix — write failing test, fix, verify

Standards-Aware Development

This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:

  • /maister:init scans config files, source code, and documentation to auto-detect your coding standards
  • Continuous checking - standards are consulted before specification, during planning, and while coding (not just at the start)
  • /maister:standards-discover refreshes standards from your evolving codebase
  • /maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATH

Standards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.

Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).

Beta Channel

Want to try experimental features before they hit stable? Install from the beta channel:

# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
# Install the beta plugin
/plugin install maister@maister-plugins-beta

If you already have the stable version installed, uninstall it first to avoid conflicts:

/plugin uninstall maister@maister-plugins

To switch back to stable:

/plugin uninstall maister@maister-plugins-beta
/plugin install maister@maister-plugins

Beta versions may contain features that are not yet fully tested. Use at your own discretion.

Best Practices

Don't use plan mode when starting a workflow. Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.

Start workflows in a fresh session. This is especially useful when chaining workflows (e.g., research → development). Research and product-design artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.

Chain workflows by passing a task folder. If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly:

/maister:development .maister/tasks/research/2026-01-12-oauth-research

You can also append additional instructions to narrow scope or guide the workflow:

/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1

Known Issues

Orchestrator may stall after long phases. After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:

/maister:development .maister/tasks/development/2026-03-24-my-feature

Learn More

About

Maister - Structured, standards-aware development workflows for Claude Code

Resources

Readme
MIT license
Activity
Custom properties

Stars

221 stars

Watchers

18 watching

Forks

31 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
BranchesTags
Repository files navigation
Maister
Structured, standards-aware development workflows for Claude Code
Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
What You Get
  • Guided workflows for features, bug fixes, enhancements, performance, migrations, research, and product design
  • Auto-discovered standards from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
  • Test-driven implementation with automated planning, incremental verification, and full test suite runs before completion
  • Pause and resume any workflow - state is preserved across sessions
  • Production readiness checks including code review, reality assessment, and pragmatic over-engineering detection
Getting Started
Prerequisites
Installation
/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins
After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.
Initial project setup
Initialize your project to auto-detect coding standards and generate project documentation:
/maister:init
This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.
If you have another project already using Maister, you can reuse its standards as a starting point:
/maister:init --standards-from=/path/to/other-project
First Workflow
/maister:development Add user profile page with avatar upload
Or just discuss your task with Claude and then run:
/maister:development
The plugin picks up context from your conversation - no arguments needed.
How It Works
  1. You describe a task - either as an argument or just in conversation
  2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
  3. You confirm, and it guides you through phases: requirements → spec → plan → implement → verify
  4. At each phase, it asks for your input and decisions
  5. You get tested, verified code with a detailed work log
All artifacts are saved in .maister/tasks/ organized by type and date.
Context-Aware Commands
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation

You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"

You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
Supported Workflows
CommandUse When
/maister:developmentFeatures, bug fixes, enhancements
/maister:researchResearch with synthesis and solution design
/maister:performanceOptimizing speed or resource usage
/maister:migrationChanging technologies or patterns
/maister:product-designProduct and feature design
Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.
Quick Commands
For smaller tasks that don't need a full workflow:
CommandUse When
/maister:quick-planYou want a plan with standards awareness before coding
/maister:quick-devYou know what to do - just implement with standards applied
/maister:quick-bugfixQuick TDD-driven bug fix — write failing test, fix, verify
Standards-Aware Development
This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:
  • /maister:init scans config files, source code, and documentation to auto-detect your coding standards
  • Continuous checking - standards are consulted before specification, during planning, and while coding (not just at the start)
  • /maister:standards-discover refreshes standards from your evolving codebase
  • /maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATH
Standards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.
Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).
Beta Channel
Want to try experimental features before they hit stable? Install from the beta channel:
# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
# Install the beta plugin
/plugin install maister@maister-plugins-beta
If you already have the stable version installed, uninstall it first to avoid conflicts:
/plugin uninstall maister@maister-plugins
To switch back to stable:
/plugin uninstall maister@maister-plugins-beta
/plugin install maister@maister-plugins
Beta versions may contain features that are not yet fully tested. Use at your own discretion.
Best Practices
Don't use plan mode when starting a workflow. Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
Start workflows in a fresh session. This is especially useful when chaining workflows (e.g., research → development). Research and product-design artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.
Chain workflows by passing a task folder. If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly:
/maister:development .maister/tasks/research/2026-01-12-oauth-research
You can also append additional instructions to narrow scope or guide the workflow:
/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1
Known Issues
Orchestrator may stall after long phases. After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:
/maister:development .maister/tasks/development/2026-03-24-my-feature
Learn More
About
Maister - Structured, standards-aware development workflows for Claude Code
Resources
Readme
MIT license
Activity
Custom properties
Stars
221 stars
Watchers
18 watching
Forks
31 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Maister
Structured, standards-aware development workflows for Claude Code
Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
What You Get
  • Guided workflows for features, bug fixes, enhancements, performance, migrations, research, and product design
  • Auto-discovered standards from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
  • Test-driven implementation with automated planning, incremental verification, and full test suite runs before completion
  • Pause and resume any workflow - state is preserved across sessions
  • Production readiness checks including code review, reality assessment, and pragmatic over-engineering detection
Getting Started
Prerequisites
Installation
/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins
After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.
Initial project setup
Initialize your project to auto-detect coding standards and generate project documentation:
/maister:init
This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.
If you have another project already using Maister, you can reuse its standards as a starting point:
/maister:init --standards-from=/path/to/other-project
First Workflow
/maister:development Add user profile page with avatar upload
Or just discuss your task with Claude and then run:
/maister:development
The plugin picks up context from your conversation - no arguments needed.
How It Works
  1. You describe a task - either as an argument or just in conversation
  2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
  3. You confirm, and it guides you through phases: requirements → spec → plan → implement → verify
  4. At each phase, it asks for your input and decisions
  5. You get tested, verified code with a detailed work log
All artifacts are saved in .maister/tasks/ organized by type and date.
Context-Aware Commands
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation

You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"

You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
Supported Workflows
CommandUse When
/maister:developmentFeatures, bug fixes, enhancements
/maister:researchResearch with synthesis and solution design
/maister:performanceOptimizing speed or resource usage
/maister:migrationChanging technologies or patterns
/maister:product-designProduct and feature design
Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.
Quick Commands
For smaller tasks that don't need a full workflow:
CommandUse When
/maister:quick-planYou want a plan with standards awareness before coding
/maister:quick-devYou know what to do - just implement with standards applied
/maister:quick-bugfixQuick TDD-driven bug fix — write failing test, fix, verify
Standards-Aware Development
This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:
  • /maister:init scans config files, source code, and documentation to auto-detect your coding standards
  • Continuous checking - standards are consulted before specification, during planning, and while coding (not just at the start)
  • /maister:standards-discover refreshes standards from your evolving codebase
  • /maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATH
Standards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.
Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).
Beta Channel
Want to try experimental features before they hit stable? Install from the beta channel:
# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
# Install the beta plugin
/plugin install maister@maister-plugins-beta
If you already have the stable version installed, uninstall it first to avoid conflicts:
/plugin uninstall maister@maister-plugins
To switch back to stable:
/plugin uninstall maister@maister-plugins-beta
/plugin install maister@maister-plugins
Beta versions may contain features that are not yet fully tested. Use at your own discretion.
Best Practices
Don't use plan mode when starting a workflow. Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
Start workflows in a fresh session. This is especially useful when chaining workflows (e.g., research → development). Research and product-design artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.
Chain workflows by passing a task folder. If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly:
/maister:development .maister/tasks/research/2026-01-12-oauth-research
You can also append additional instructions to narrow scope or guide the workflow:
/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1
Known Issues
Orchestrator may stall after long phases. After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:
/maister:development .maister/tasks/development/2026-03-24-my-feature
Learn More
About
Maister - Structured, standards-aware development workflows for Claude Code
Resources
Readme
MIT license
Activity
Custom properties
Stars
221 stars
Watchers
18 watching
Forks
31 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Maister
Structured, standards-aware development workflows for Claude Code
Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
What You Get
  • Guided workflows for features, bug fixes, enhancements, performance, migrations, research, and product design
  • Auto-discovered standards from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
  • Test-driven implementation with automated planning, incremental verification, and full test suite runs before completion
  • Pause and resume any workflow - state is preserved across sessions
  • Production readiness checks including code review, reality assessment, and pragmatic over-engineering detection
Getting Started
Prerequisites
Installation
/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins
After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.
Initial project setup
Initialize your project to auto-detect coding standards and generate project documentation:
/maister:init
This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.
If you have another project already using Maister, you can reuse its standards as a starting point:
/maister:init --standards-from=/path/to/other-project
First Workflow
/maister:development Add user profile page with avatar upload
Or just discuss your task with Claude and then run:
/maister:development
The plugin picks up context from your conversation - no arguments needed.
How It Works
  1. You describe a task - either as an argument or just in conversation
  2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
  3. You confirm, and it guides you through phases: requirements → spec → plan → implement → verify
  4. At each phase, it asks for your input and decisions
  5. You get tested, verified code with a detailed work log
All artifacts are saved in .maister/tasks/ organized by type and date.
Context-Aware Commands
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation

You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"

You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
Supported Workflows
CommandUse When
/maister:developmentFeatures, bug fixes, enhancements
/maister:researchResearch with synthesis and solution design
/maister:performanceOptimizing speed or resource usage
/maister:migrationChanging technologies or patterns
/maister:product-designProduct and feature design
Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.
Quick Commands
For smaller tasks that don't need a full workflow:
CommandUse When
/maister:quick-planYou want a plan with standards awareness before coding
/maister:quick-devYou know what to do - just implement with standards applied
/maister:quick-bugfixQuick TDD-driven bug fix — write failing test, fix, verify
Standards-Aware Development
This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:
  • /maister:init scans config files, source code, and documentation to auto-detect your coding standards
  • Continuous checking - standards are consulted before specification, during planning, and while coding (not just at the start)
  • /maister:standards-discover refreshes standards from your evolving codebase
  • /maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATH
Standards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.
Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).
Beta Channel
Want to try experimental features before they hit stable? Install from the beta channel:
# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
# Install the beta plugin
/plugin install maister@maister-plugins-beta
If you already have the stable version installed, uninstall it first to avoid conflicts:
/plugin uninstall maister@maister-plugins
To switch back to stable:
/plugin uninstall maister@maister-plugins-beta
/plugin install maister@maister-plugins
Beta versions may contain features that are not yet fully tested. Use at your own discretion.
Best Practices
Don't use plan mode when starting a workflow. Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
Start workflows in a fresh session. This is especially useful when chaining workflows (e.g., research → development). Research and product-design artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.
Chain workflows by passing a task folder. If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly:
/maister:development .maister/tasks/research/2026-01-12-oauth-research
You can also append additional instructions to narrow scope or guide the workflow:
/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1
Known Issues
Orchestrator may stall after long phases. After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:
/maister:development .maister/tasks/development/2026-03-24-my-feature
Learn More
About
Maister - Structured, standards-aware development workflows for Claude Code
Resources
Readme
MIT license
Activity
Custom properties
Stars
221 stars
Watchers
18 watching
Forks
31 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
BranchesTags
Repository files navigation
Maister
Structured, standards-aware development workflows for Claude Code
Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
What You Get
  • Guided workflows for features, bug fixes, enhancements, performance, migrations, research, and product design
  • Auto-discovered standards from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
  • Test-driven implementation with automated planning, incremental verification, and full test suite runs before completion
  • Pause and resume any workflow - state is preserved across sessions
  • Production readiness checks including code review, reality assessment, and pragmatic over-engineering detection
Getting Started
Prerequisites
Installation
/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins
After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.
Initial project setup
Initialize your project to auto-detect coding standards and generate project documentation:
/maister:init
This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.
If you have another project already using Maister, you can reuse its standards as a starting point:
/maister:init --standards-from=/path/to/other-project
First Workflow
/maister:development Add user profile page with avatar upload
Or just discuss your task with Claude and then run:
/maister:development
The plugin picks up context from your conversation - no arguments needed.
How It Works
  1. You describe a task - either as an argument or just in conversation
  2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
  3. You confirm, and it guides you through phases: requirements → spec → plan → implement → verify
  4. At each phase, it asks for your input and decisions
  5. You get tested, verified code with a detailed work log
All artifacts are saved in .maister/tasks/ organized by type and date.
Context-Aware Commands
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation

You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"

You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
Supported Workflows
CommandUse When
/maister:developmentFeatures, bug fixes, enhancements
/maister:researchResearch with synthesis and solution design
/maister:performanceOptimizing speed or resource usage
/maister:migrationChanging technologies or patterns
/maister:product-designProduct and feature design
Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.
Quick Commands
For smaller tasks that don't need a full workflow:
CommandUse When
/maister:quick-planYou want a plan with standards awareness before coding
/maister:quick-devYou know what to do - just implement with standards applied
/maister:quick-bugfixQuick TDD-driven bug fix — write failing test, fix, verify
Standards-Aware Development
This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:
  • /maister:init scans config files, source code, and documentation to auto-detect your coding standards
  • Continuous checking - standards are consulted before specification, during planning, and while coding (not just at the start)
  • /maister:standards-discover refreshes standards from your evolving codebase
  • /maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATH
Standards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.
Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).
Beta Channel
Want to try experimental features before they hit stable? Install from the beta channel:
# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
# Install the beta plugin
/plugin install maister@maister-plugins-beta
If you already have the stable version installed, uninstall it first to avoid conflicts:
/plugin uninstall maister@maister-plugins
To switch back to stable:
/plugin uninstall maister@maister-plugins-beta
/plugin install maister@maister-plugins
Beta versions may contain features that are not yet fully tested. Use at your own discretion.
Best Practices
Don't use plan mode when starting a workflow. Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
Start workflows in a fresh session. This is especially useful when chaining workflows (e.g., research → development). Research and product-design artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.
Chain workflows by passing a task folder. If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly:
/maister:development .maister/tasks/research/2026-01-12-oauth-research
You can also append additional instructions to narrow scope or guide the workflow:
/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1
Known Issues
Orchestrator may stall after long phases. After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:
/maister:development .maister/tasks/development/2026-03-24-my-feature
Learn More
About
Maister - Structured, standards-aware development workflows for Claude Code
Resources
Readme
MIT license
Activity
Custom properties
Stars
221 stars
Watchers
18 watching
Forks
31 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Maister
Structured, standards-aware development workflows for Claude Code
Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
What You Get
  • Guided workflows for features, bug fixes, enhancements, performance, migrations, research, and product design
  • Auto-discovered standards from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
  • Test-driven implementation with automated planning, incremental verification, and full test suite runs before completion
  • Pause and resume any workflow - state is preserved across sessions
  • Production readiness checks including code review, reality assessment, and pragmatic over-engineering detection
Getting Started
Prerequisites
Installation
/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins
After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.
Initial project setup
Initialize your project to auto-detect coding standards and generate project documentation:
/maister:init
This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.
If you have another project already using Maister, you can reuse its standards as a starting point:
/maister:init --standards-from=/path/to/other-project
First Workflow
/maister:development Add user profile page with avatar upload
Or just discuss your task with Claude and then run:
/maister:development
The plugin picks up context from your conversation - no arguments needed.
How It Works
  1. You describe a task - either as an argument or just in conversation
  2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
  3. You confirm, and it guides you through phases: requirements → spec → plan → implement → verify
  4. At each phase, it asks for your input and decisions
  5. You get tested, verified code with a detailed work log
All artifacts are saved in .maister/tasks/ organized by type and date.
Context-Aware Commands
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation

You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"

You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
Supported Workflows
CommandUse When
/maister:developmentFeatures, bug fixes, enhancements
/maister:researchResearch with synthesis and solution design
/maister:performanceOptimizing speed or resource usage
/maister:migrationChanging technologies or patterns
/maister:product-designProduct and feature design
Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.
Quick Commands
For smaller tasks that don't need a full workflow:
CommandUse When
/maister:quick-planYou want a plan with standards awareness before coding
/maister:quick-devYou know what to do - just implement with standards applied
/maister:quick-bugfixQuick TDD-driven bug fix — write failing test, fix, verify
Standards-Aware Development
This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:
  • /maister:init scans config files, source code, and documentation to auto-detect your coding standards
  • Continuous checking - standards are consulted before specification, during planning, and while coding (not just at the start)
  • /maister:standards-discover refreshes standards from your evolving codebase
  • /maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATH
Standards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.
Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).
Beta Channel
Want to try experimental features before they hit stable? Install from the beta channel:
# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
# Install the beta plugin
/plugin install maister@maister-plugins-beta
If you already have the stable version installed, uninstall it first to avoid conflicts:
/plugin uninstall maister@maister-plugins
To switch back to stable:
/plugin uninstall maister@maister-plugins-beta
/plugin install maister@maister-plugins
Beta versions may contain features that are not yet fully tested. Use at your own discretion.
Best Practices
Don't use plan mode when starting a workflow. Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
Start workflows in a fresh session. This is especially useful when chaining workflows (e.g., research → development). Research and product-design artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.
Chain workflows by passing a task folder. If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly:
/maister:development .maister/tasks/research/2026-01-12-oauth-research
You can also append additional instructions to narrow scope or guide the workflow:
/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1
Known Issues
Orchestrator may stall after long phases. After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:
/maister:development .maister/tasks/development/2026-03-24-my-feature
Learn More
About
Maister - Structured, standards-aware development workflows for Claude Code
Resources
Readme
MIT license
Activity
Custom properties
Stars
221 stars
Watchers
18 watching
Forks
31 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
Maister
Structured, standards-aware development workflows for Claude Code
Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
What You Get
  • Guided workflows for features, bug fixes, enhancements, performance, migrations, research, and product design
  • Auto-discovered standards from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
  • Test-driven implementation with automated planning, incremental verification, and full test suite runs before completion
  • Pause and resume any workflow - state is preserved across sessions
  • Production readiness checks including code review, reality assessment, and pragmatic over-engineering detection
Getting Started
Prerequisites
Installation
/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins
After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.
Initial project setup
Initialize your project to auto-detect coding standards and generate project documentation:
/maister:init
This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.
If you have another project already using Maister, you can reuse its standards as a starting point:
/maister:init --standards-from=/path/to/other-project
First Workflow
/maister:development Add user profile page with avatar upload
Or just discuss your task with Claude and then run:
/maister:development
The plugin picks up context from your conversation - no arguments needed.
How It Works
  1. You describe a task - either as an argument or just in conversation
  2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
  3. You confirm, and it guides you through phases: requirements → spec → plan → implement → verify
  4. At each phase, it asks for your input and decisions
  5. You get tested, verified code with a detailed work log
All artifacts are saved in .maister/tasks/ organized by type and date.
Context-Aware Commands
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation

You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"

You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
Supported Workflows
CommandUse When
/maister:developmentFeatures, bug fixes, enhancements
/maister:researchResearch with synthesis and solution design
/maister:performanceOptimizing speed or resource usage
/maister:migrationChanging technologies or patterns
/maister:product-designProduct and feature design
Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.
Quick Commands
For smaller tasks that don't need a full workflow:
CommandUse When
/maister:quick-planYou want a plan with standards awareness before coding
/maister:quick-devYou know what to do - just implement with standards applied
/maister:quick-bugfixQuick TDD-driven bug fix — write failing test, fix, verify
Standards-Aware Development
This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:
  • /maister:init scans config files, source code, and documentation to auto-detect your coding standards
  • Continuous checking - standards are consulted before specification, during planning, and while coding (not just at the start)
  • /maister:standards-discover refreshes standards from your evolving codebase
  • /maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATH
Standards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.
Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).
Beta Channel
Want to try experimental features before they hit stable? Install from the beta channel:
# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
# Install the beta plugin
/plugin install maister@maister-plugins-beta
If you already have the stable version installed, uninstall it first to avoid conflicts:
/plugin uninstall maister@maister-plugins
To switch back to stable:
/plugin uninstall maister@maister-plugins-beta
/plugin install maister@maister-plugins
Beta versions may contain features that are not yet fully tested. Use at your own discretion.
Best Practices
Don't use plan mode when starting a workflow. Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
Start workflows in a fresh session. This is especially useful when chaining workflows (e.g., research → development). Research and product-design artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.
Chain workflows by passing a task folder. If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly:
/maister:development .maister/tasks/research/2026-01-12-oauth-research
You can also append additional instructions to narrow scope or guide the workflow:
/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1
Known Issues
Orchestrator may stall after long phases. After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:
/maister:development .maister/tasks/development/2026-03-24-my-feature
Learn More
About
Maister - Structured, standards-aware development workflows for Claude Code
Resources
Readme
MIT license
Activity
Custom properties
Stars
221 stars
Watchers
18 watching
Forks
31 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
BranchesTags
Repository files navigation
Maister
Structured, standards-aware development workflows for Claude Code
Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
What You Get
  • Guided workflows for features, bug fixes, enhancements, performance, migrations, research, and product design
  • Auto-discovered standards from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
  • Test-driven implementation with automated planning, incremental verification, and full test suite runs before completion
  • Pause and resume any workflow - state is preserved across sessions
  • Production readiness checks including code review, reality assessment, and pragmatic over-engineering detection
Getting Started
Prerequisites
Installation
/plugin marketplace add SkillPanel/maister
/plugin install maister@maister-plugins
After installing, restart Claude Code (/exit and relaunch) to ensure the plugin is fully loaded.
Initial project setup
Initialize your project to auto-detect coding standards and generate project documentation:
/maister:init
This scans your codebase and creates .maister/ with standards, docs, and task folders. May take a few minutes on larger projects.
If you have another project already using Maister, you can reuse its standards as a starting point:
/maister:init --standards-from=/path/to/other-project
First Workflow
/maister:development Add user profile page with avatar upload
Or just discuss your task with Claude and then run:
/maister:development
The plugin picks up context from your conversation - no arguments needed.
How It Works
  1. You describe a task - either as an argument or just in conversation
  2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
  3. You confirm, and it guides you through phases: requirements → spec → plan → implement → verify
  4. At each phase, it asks for your input and decisions
  5. You get tested, verified code with a detailed work log
All artifacts are saved in .maister/tasks/ organized by type and date.
Context-Aware Commands
Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
You: "The login page throws a 500 error when the session expires"
You: /maister:development
→ Auto-detects: bug fix, extracts description from conversation

You: /maister:standards-update
→ Scans conversation for patterns like "we always use..." or "prefer X over Y"

You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
Supported Workflows
CommandUse When
/maister:developmentFeatures, bug fixes, enhancements
/maister:researchResearch with synthesis and solution design
/maister:performanceOptimizing speed or resource usage
/maister:migrationChanging technologies or patterns
/maister:product-designProduct and feature design
Task type (feature/bug/enhancement) is auto-detected from context. Override with --type=feature|bug|enhancement if needed. Or use /maister:work as a single entry point that routes to the right workflow.
Quick Commands
For smaller tasks that don't need a full workflow:
CommandUse When
/maister:quick-planYou want a plan with standards awareness before coding
/maister:quick-devYou know what to do - just implement with standards applied
/maister:quick-bugfixQuick TDD-driven bug fix — write failing test, fix, verify
Standards-Aware Development
This is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:
  • /maister:init scans config files, source code, and documentation to auto-detect your coding standards
  • Continuous checking - standards are consulted before specification, during planning, and while coding (not just at the start)
  • /maister:standards-discover refreshes standards from your evolving codebase
  • /maister:standards-update lets you add or refine standards manually, or sync from another project with --from=PATH
Standards live in .maister/docs/standards/ and are indexed in .maister/docs/INDEX.md.
Important: Run workflows with auto-accept edits enabled. Do not use Claude Code's plan mode with workflows (see Best Practices below).
Beta Channel
Want to try experimental features before they hit stable? Install from the beta channel:
# Add the beta marketplace
/plugin marketplace add SkillPanel/Maister#beta
# Install the beta plugin
/plugin install maister@maister-plugins-beta
If you already have the stable version installed, uninstall it first to avoid conflicts:
/plugin uninstall maister@maister-plugins
To switch back to stable:
/plugin uninstall maister@maister-plugins-beta
/plugin install maister@maister-plugins
Beta versions may contain features that are not yet fully tested. Use at your own discretion.
Best Practices
Don't use plan mode when starting a workflow. Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
Start workflows in a fresh session. This is especially useful when chaining workflows (e.g., research → development). Research and product-design artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.
Chain workflows by passing a task folder. If you've completed a research or product-design workflow and want to build on those results, pass the task folder directly:
/maister:development .maister/tasks/research/2026-01-12-oauth-research
You can also append additional instructions to narrow scope or guide the workflow:
/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1
Known Issues
Orchestrator may stall after long phases. After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:
/maister:development .maister/tasks/development/2026-03-24-my-feature
Learn More
About
Maister - Structured, standards-aware development workflows for Claude Code
Resources
Readme
MIT license
Activity
Custom properties
Stars
221 stars
Watchers
18 watching
Forks
31 forks
Report repository
Releases
Packages
Contributors
Languages