Auto-classifies your task and routes to the appropriate workflow. Accepts:
- No arguments: Extracts the task from your current conversation context
- Task description:
/maister:work "Add user profile page" - Task folder path:
/maister:work .maister/tasks/new-features/2026-02-17-user-profile(resumes) - GitHub issue URL:
/maister:work https://github.com/org/repo/issues/42
The plugin classifies the task type with confidence scoring, asks for confirmation, then launches the matching orchestrator.
Starts the unified development workflow (14 adaptive phases) or resumes an existing one. All arguments are optional — when run without a description, the plugin extracts it from your current conversation. Pass an existing task path to resume. Task type (bug/enhancement/feature) is auto-detected from context when --type is omitted.
| Flag | Description |
|---|---|
--type=bug|enhancement|feature |
Specify task type (auto-detected if omitted) |
--e2e |
Include E2E testing phase |
--user-docs |
Generate user documentation phase |
--code-review |
Include code review phase |
--research=PATH |
Start development informed by a completed research task |
--from=PHASE |
Start from or resume at a specific phase |
--reset-attempts |
Reset failed attempt counters (resume) |
Task directory: .maister/tasks/development/
Resume phases: analysis, gap, spec, plan, implement, verify
Starts performance optimization with static bottleneck analysis (9 phases) or resumes an existing one. Can be run without arguments — the plugin extracts the optimization target from your conversation. Detects N+1 queries, missing indexes, O(n^2) algorithms, blocking I/O, and memory leak patterns.
| Flag | Description |
|---|---|
--from=PHASE |
Start from or resume at a specific phase |
--reset-attempts |
Reset failed attempt counters (resume) |
You can optionally provide profiling data (flame graphs, APM screenshots) — the workflow creates a directory for these.
Task directory: .maister/tasks/performance/
Resume phases: analysis, specification, planning, implementation, verification
Starts migration workflow (8 phases) with mandatory rollback planning and risk assessment, or resumes an existing one. Can be run without arguments — the plugin extracts migration details from your conversation.
| Flag | Description |
|---|---|
--type=code|data|architecture|general |
Migration type (affects risk focus) |
--from=PHASE |
Start from or resume at a specific phase |
--reset-attempts |
Reset failed attempt counters (resume) |
Task directory: .maister/tasks/migrations/
Resume phases: analysis, target, spec, plan, execute, verify, docs
Starts research workflow (8 phases) with multi-source gathering, synthesis, and optional solution brainstorming, or resumes an existing one. Can be run without arguments — the plugin extracts the research question from your conversation.
| Flag | Description |
|---|---|
--type=technical|requirements|literature|mixed |
Research methodology type |
--brainstorm |
Force brainstorming + design phases |
--no-brainstorm |
Skip brainstorming phases |
--from=PHASE |
Start from or resume at a specific phase |
--reset-attempts |
Reset failed attempt counters (resume) |
Research output can feed into development: /maister:development --research=.maister/tasks/research/...
Task directory: .maister/tasks/research/
Resume phases: foundation, brainstorming-decision, brainstorming, design, outputs, verification, integration
Starts the interactive product/feature design workflow (9 adaptive phases) or resumes an existing one. Transforms ideas into structured product briefs through collaborative exploration, iterative refinement, and visual prototyping. Can be run without arguments — the plugin extracts the design brief from your conversation.
| Flag | Description |
|---|---|
--research=PATH |
Start design informed by a completed research task |
--no-visual |
Skip browser-based visual companion (use ASCII mockups only) |
--from=PHASE |
Start from or resume at a specific phase |
--reset-attempts |
Reset failed attempt counters (resume) |
Design output can feed directly into development: /maister:development .maister/tasks/product-design/...
Task directory: .maister/tasks/product-design/
Resume phases: context, synthesis, problem, personas, alternatives, convergence, specification, prototyping, handoff
Standalone review commands that can be run anytime, independent of workflows.
Automated code quality, security, and performance analysis.
| Flag | Description |
|---|---|
--scope=quality|security|performance|all |
Focus area (default: all) |
Analyzes complexity, duplication, code smells, security vulnerabilities, and performance issues. Generates report with severity levels (Critical/Warning/Info).
Detects over-engineering and ensures code matches project scale. Identifies excessive abstraction, enterprise patterns in simple code, infrastructure overkill. Recommends specific simplifications with before/after examples.
Validates that completed work actually solves the intended problem. Runs tests, checks end-to-end workflows, and evaluates error scenarios. Returns deployment decision: Ready / Issues Found / Not Ready.
Independent specification audit with senior auditor perspective.
| Flag | Description |
|---|---|
--post-implementation |
Compare spec vs actual implementation (default: pre-implementation) |
Identifies ambiguities, missing details, and gaps. Uses external tools (GitHub CLI, Azure CLI) for verification.
Pre-deployment verification across 7 dimensions: configuration, monitoring, error handling, performance, security, deployment, and GO/NO-GO recommendation.
| Flag | Description |
|---|---|
--target=prod|staging |
Target environment (default: prod with full rigor) |
Initialize the Maister framework. Scans your codebase with a project-analyzer subagent, presents findings for confirmation, then generates:
.maister/docs/with INDEX.md, project docs (vision, roadmap, tech-stack), and coding standards.maister/tasks/directory structure- CLAUDE.md integration
| Flag | Description |
|---|---|
--standards-from=PATH |
Copy standards from another project's .maister/docs/standards/ instead of built-in defaults. Useful when starting a new project that should follow the same conventions as an existing one. |
If .maister/ already exists, offers to backup, update, or cancel.
Auto-discovers coding standards from multiple sources in parallel: config files, source code patterns, documentation, pull requests, and CI/CD pipelines.
| Flag | Description |
|---|---|
--scope=full|quick|frontend|backend|testing|custom |
Discovery scope (default: full) |
--confidence=N |
Minimum confidence threshold, 0-100 (default: 60) |
--auto-apply |
Auto-apply standards with 90%+ confidence |
--skip-external |
Skip PR and CI/CD analysis |
--pr-count=N |
Number of PRs to analyze (default: 10, max: 20) |
Presents findings in confidence tiers (high/medium/low) for review before applying.
Update or create standards from conversation context or explicit description. When run without arguments, scans your current conversation for standards patterns like "we should always...", "our convention is...", "prefer X over Y" and proposes them as new standards.
| Flag | Description |
|---|---|
--from=PATH |
Sync standards from another project. Analyzes differences, shows what's missing or changed, and lets you select which standards to import. |
Lightweight commands for small tasks that don't need a full orchestrator workflow.
Implement a task directly with standards awareness. Reads INDEX.md, loads applicable standards, then implements without planning mode.
When to use: Task is clear, no architectural decisions needed, you know what needs doing.
Enter Claude Code's planning mode with standards awareness. Discovers and reads applicable standards before entering plan mode, so your plan is informed by project conventions.
Standards compliance checklist is required in the plan file before exiting plan mode.
Lightweight TDD-driven bug fix without a full orchestrator workflow. Analyzes the bug, writes a failing test, implements the fix, and verifies the test passes.
When to use: Simple, isolated bugs where you can quickly identify the root cause. If the bug is too complex (multiple files, unclear root cause, architectural impact), the skill suggests escalating to /maister:development.
No task directory created — works directly in your codebase.