{
  "id": "page:library-maestro",
  "_kind": "Page",
  "_file": "wiki/library/maestro.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Maestro App Factory (Library)",
    "displayName": "Maestro App Factory (Library)",
    "slug": "library/maestro",
    "articlePath": "wiki/library/maestro.md",
    "article": "\n# Maestro App Factory\n\n**Source:** [Maestro](https://github.com/SnapdragonPartners/maestro) by SnapdragonPartners\n**Category:** Multi-Agent App Factory Framework\n**License:** MIT\n**Priority:** High\n\n## Overview\n\nMaestro orchestrates AI agents mimicking high-performing human dev teams for production-ready applications. It features three core agent roles (Product Manager, Architect, Coders) with strict separation of concerns: PMs gather requirements, Architects design and review, Coders implement and test. Code review separation is enforced -- architects never write code, coders never self-review.\n\n## Key Features\n\n- **Multi-Agent Roles** with strict responsibility separation\n- **Operating Modes**: Bootstrap, Development, Hotfix, Maintenance\n- **Knowledge Graph** (`.maestro/knowledge.dot`) for institutional memory\n- **Quality Gates** with DRY, YAGNI, abstraction, coverage enforcement\n- **Parallel Coder Dispatch** with stateless coder lifecycle\n- **Metrics Dashboard** for tokens, time, quality, and costs\n- **Maintenance Mode** triggered after N specs for tech debt management\n\n## Process Files\n\n| File | Description | Primary Agents |\n|------|-------------|----------------|\n| `maestro-orchestrator.js` | Full lifecycle (PM interview through merge) | All agents |\n| `maestro-bootstrap.js` | New project scaffold and setup | Architect, Coder |\n| `maestro-development.js` | Feature development cycle | Architect, Coder, Test Engineer |\n| `maestro-hotfix.js` | Fast-path production fixes | Hotfix Specialist, Architect |\n| `maestro-maintenance.js` | Technical debt management | Maintenance Engineer, Knowledge Curator |\n| `maestro-knowledge-graph.js` | Knowledge capture, validation, sync | Knowledge Curator |\n\n## Agent Personas\n\n| Agent | Role | ID |\n|-------|------|----|\n| Product Manager | Requirements elicitation and specification | `product-manager` |\n| Architect | Technical design, stories, code oversight, merge | `architect` |\n| Coder | Implementation, testing, PR submission | `coder` |\n| Code Reviewer | Independent quality verification | `code-reviewer` |\n| Knowledge Curator | Knowledge graph maintenance | `knowledge-curator` |\n| Maintenance Engineer | Technical debt management | `maintenance-engineer` |\n| Hotfix Specialist | Rapid triage and fix | `hotfix-specialist` |\n| Test Engineer | Test strategy and coverage | `test-engineer` |\n\n## Skills\n\n| Skill | Description | Agent |\n|-------|-------------|-------|\n| Requirements Interview | Expertise-adaptive PM interview | Product Manager |\n| Specification Generation | Requirements to tech spec | PM + Architect |\n| Story Decomposition | Spec to implementable stories | Architect |\n| Code Review Gate | Principle enforcement review | Architect / Code Reviewer |\n| Knowledge Graph Management | Pattern capture, validation, query | Knowledge Curator |\n| Maintenance Orchestration | Tech debt management | Maintenance Engineer |\n| Hotfix Triage | Issue classification and routing | Hotfix Specialist |\n| Test Enforcement | Test validation and coverage | Test Engineer |\n\n## Operating Modes\n\n### Bootstrap\nNew project minimum infrastructure: scaffold directories, configure tooling, install dependencies, define initial architecture, initialize knowledge graph.\n\n### Development (Default)\nFeature development: story planning, parallel coder implementation, automated testing, architect code review, merge. Coders terminate between story batches.\n\n### Hotfix\nFast-path for urgent production issues: triage, locate root cause, minimal fix, regression test, expedited review, deploy. Simple fixes skip planning.\n\n### Maintenance\nTechnical debt management after every N specs: branch cleanup, knowledge sync, doc verification, TODO scanning, coverage analysis, dependency audit.\n\n## Quality Principles\n\n1. **DRY** - No unnecessary duplication\n2. **YAGNI** - No speculative features\n3. **Proper Abstraction** - Correct encapsulation\n4. **Test Coverage** - Adequate automated tests\n5. **Separation of Concerns** - Architects review, coders implement\n\n## Attribution\n\nAdapted from [Maestro App Factory](https://github.com/SnapdragonPartners/maestro) by SnapdragonPartners. Licensed under MIT.\n",
    "documents": [
      "specialization:maestro"
    ]
  },
  "outgoingEdges": [
    {
      "from": "page:library-maestro",
      "to": "specialization:maestro",
      "kind": "documents"
    }
  ],
  "incomingEdges": [
    {
      "from": "page:index",
      "to": "page:library-maestro",
      "kind": "contains_page"
    }
  ]
}