{
  "markdown": "<div align=\"center\">\n\n# Maister\n\n**Structured, standards-aware development workflows for Claude Code**\n\nDescribe 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.\n\n</div>\n\n## What You Get\n\n- **Guided workflows** for features, bug fixes, enhancements, performance, migrations, research, and product design\n- **Auto-discovered standards** from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow\n- **Test-driven implementation** with automated planning, incremental verification, and full test suite runs before completion\n- **Pause and resume** any workflow - state is preserved across sessions\n- **Production readiness checks** including code review, reality assessment, and pragmatic over-engineering detection\n\n## Getting Started\n\n### Prerequisites\n\n- [Claude Code](https://claude.ai/code) CLI installed and configured\n\n### Installation\n\n```bash\n/plugin marketplace add SkillPanel/maister\n/plugin install maister@maister-plugins\n```\n\nAfter installing, restart Claude Code (`/exit` and relaunch) to ensure the plugin is fully loaded.\n\n### Initial project setup\n\nInitialize your project to auto-detect coding standards and generate project documentation:\n\n```bash\n/maister:init\n```\n\nThis scans your codebase and creates `.maister/` with standards, docs, and task folders. May take a few minutes on larger projects.\n\nIf you have another project already using Maister, you can reuse its standards as a starting point:\n\n```bash\n/maister:init --standards-from=/path/to/other-project\n```\n\n### First Workflow\n\n```bash\n/maister:development Add user profile page with avatar upload\n```\n\nOr just discuss your task with Claude and then run:\n\n```bash\n/maister:development\n```\n\nThe plugin picks up context from your conversation - no arguments needed.\n\n## How It Works\n\n1. You describe a task - either as an argument or just in conversation\n2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow\n3. You confirm, and it guides you through phases: **requirements → spec → plan → implement → verify**\n4. At each phase, it asks for your input and decisions\n5. You get tested, verified code with a detailed work log\n\nAll artifacts are saved in `.maister/tasks/` organized by type and date.\n\n### Context-Aware Commands\n\nEvery workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:\n\n```\nYou: \"The login page throws a 500 error when the session expires\"\nYou: /maister:development\n→ Auto-detects: bug fix, extracts description from conversation\n```\n\n```\nYou: /maister:standards-update\n→ Scans conversation for patterns like \"we always use...\" or \"prefer X over Y\"\n```\n\nYou can always be explicit when you prefer - arguments and flags simply override the auto-detection.\n\n## Supported Workflows\n\n| Command | Use When |\n|---------|----------|\n| `/maister:development` | Features, bug fixes, enhancements |\n| `/maister:research` | Research with synthesis and solution design |\n| `/maister:performance` | Optimizing speed or resource usage |\n| `/maister:migration` | Changing technologies or patterns |\n| `/maister:product-design` | Product and feature design |\n\nTask 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.\n\n### Quick Commands\n\nFor smaller tasks that don't need a full workflow:\n\n| Command | Use When |\n|---------|----------|\n| `/maister:quick-plan` | You want a plan with standards awareness before coding |\n| `/maister:quick-dev` | You know what to do - just implement with standards applied |\n| `/maister:quick-bugfix` | Quick TDD-driven bug fix — write failing test, fix, verify |\n\n## Standards-Aware Development\n\nThis is the key differentiator. Maister doesn't just run workflows - it learns your project's conventions and enforces them:\n\n- **`/maister:init`** scans config files, source code, and documentation to auto-detect your coding standards\n- **Continuous checking** - standards are consulted before specification, during planning, and while coding (not just at the start)\n- **`/maister:standards-discover`** refreshes standards from your evolving codebase\n- **`/maister:standards-update`** lets you add or refine standards manually, or sync from another project with `--from=PATH`\n\nStandards live in `.maister/docs/standards/` and are indexed in `.maister/docs/INDEX.md`.\n\n**Important**: Run workflows with **auto-accept edits** enabled. Do not use Claude Code's plan mode with workflows (see [Best Practices](#best-practices) below).\n\n## Beta Channel\n\nWant to try experimental features before they hit stable? Install from the beta channel:\n\n```bash\n# Add the beta marketplace\n/plugin marketplace add SkillPanel/Maister#beta\n\n# Install the beta plugin\n/plugin install maister@maister-plugins-beta\n```\n\nIf you already have the stable version installed, uninstall it first to avoid conflicts:\n\n```bash\n/plugin uninstall maister@maister-plugins\n```\n\nTo switch back to stable:\n\n```bash\n/plugin uninstall maister@maister-plugins-beta\n/plugin install maister@maister-plugins\n```\n\nBeta versions may contain features that are not yet fully tested. Use at your own discretion.\n\n## Best Practices\n\n**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.\n\n**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.\n\n**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:\n\n```bash\n/maister:development .maister/tasks/research/2026-01-12-oauth-research\n```\n\nYou can also append additional instructions to narrow scope or guide the workflow:\n\n```bash\n/maister:development .maister/tasks/product-design/2026-03-10-dashboard-redesign Implement only phase 1\n```\n\n## Known Issues\n\n**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:\n\n```bash\n/maister:development .maister/tasks/development/2026-03-24-my-feature\n```\n\n## Learn More\n\n- [Workflow Details](docs/workflows.md) - phases, examples, and task structure for each workflow type\n- [Full Command Reference](docs/commands.md) - all workflow, review, utility, and quick commands\n",
  "bytes": 7164,
  "sha": "42b49af1cf690026a702f50525f06f3af6b9f46571a9f9f3a93ed726b29305e5",
  "repo_slug": "skillpanel/maister",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_skillpanel_maister_maister_4c265695/readme"
}