esg-sustainability-reporting

Game Development specialist team — 4 agents, 5 skills, 4-file cited knowledge bank, 3 templates, 5 commands, 8 best-practice rules, 1 advisory hook. A production-and-design team for a game studio or indie team — it scopes to a vertical slice before a full build, designs core loops and economies that retain, runs production on milestones and risk burn-down, and reads live-ops on retention and monetization the way a team that ships and then operates a game must. Inherits ravenclaude-core protocols.

Travel agency / tour-operator operations team — 3 agents (travel-agency-operations-lead, itinerary-and-booking-specialist, supplier-and-commission-manager) for the three engines of a leisure travel business: agency P&L and revenue model (commission vs service fee vs markup, supplier mix, host splits, E&O risk), itinerary design and multi-supplier booking (FIT vs group, quoting, changes, documentation, service recovery), and supplier + commission management (net vs commissionable, BSP/ARC settlement, commission tracking and recovery, consortia). ADVISORY operations knowledge, not legal, tax, or financial advice; supplier fare rules, commission norms, cancellation penalties, and seller-of-travel requirements are volatile and supplier-/jurisdiction-specific — each carries a retrieval date + verify-at-use; no traveler PII. 4 skills, a decision-tree knowledge bank (4 Mermaid trees + a dated 2026 reference), 5 best-practices, 2 templates, 2 commands. Requires ravenclaude-core@>=0.7.0.

Power Platform specialist team — 11 agents (incl. power-platform-tester, power-bi-engineer) and 23 skills, with strong ALM/git coverage for solutions, flows, and PBIP. A house-opinions hook flags 8 §3/§4 violations; the knowledge bank carries production decision trees (PA-flow recovery, Dataverse token-acquisition, PCF React surface, PBI deploy/refresh, custom-connector build-path, PBIR Enhanced infinite-spinner debug + full build reference, DAX silent-zero scoring via the `Domain` pattern, sempy.fabric notebook reference, Power BI Copilot report-readiness, Code Apps connector gotchas, PBIP deployment variables + #839, PBIR reference enrichment, PBIP report fast-solve triage router [MCP-optional], main-forms-are-Web-API-authorable grounding) plus a real-engagement scenarios bank. Bundles the community pbix-mcp server (d0nk3yhm/pbix-mcp, MIT) for .pbix/.pbit read/write/DAX-eval (`pip install pbix-mcp`); documents (not bundles) the official Microsoft Dataverse MCP (CLAUDE.md §9a). Extends ravenclaude-core.

FinOps & Cloud Cost specialist team — 4 agents (finops-lead, cost-allocation-analyst, commitment-planning-specialist, unit-economics-strategist), 5 skills, 4 templates, 5 commands, 1 advisory hook, 8 best-practice rules, and a 4-file research-grounded knowledge bank. A FinOps team for a cost lead or eng-finance partner accountable for cloud spend and unit economics — it allocates spend before optimizing it, reads unit economics over the total bill, treats commitments as a portfolio decision made after rightsizing, and kills waste first. Inherits ravenclaude-core protocols.

Salesforce practitioner team — 5 agents (apex-engineer, flow-automation-architect, agentforce-architect, salesforce-platform-architect, salesforce-reviewer) covering governor-safe bulkified Apex (triggers/async/services), declarative automation by density (Flow vs Apex), Agentforce agent design (topics/subagents, Agent Script determinism, RAG grounding, Trust Layer), org architecture (data model, OWD→role→sharing→Apex security model, 2GP packaging/DevOps, LDV), and a forked review rubric (the 15 house opinions as pass/fail). 9-doc citation-grounded knowledge bank (9 Mermaid decision trees, dated 2026-05-30), 5 skills, 5 templates, 1 advisory hook (grep-able anti-patterns: SOQL/DML-in-loop, hard-coded IDs, SeeAllData=true, missing with-sharing). Seams: integration→azure-cloud, analytics→data-platform/microsoft-fabric, LWC styling→web-design, methodology/DevOps/security-review→ravenclaude-core. Requires ravenclaude-core@>=0.7.0.

Renewable Energy specialist team — 4 agents, 5 skills, 4-file cited knowledge bank, 3 templates, 5 commands, 8 best-practice rules, 1 advisory hook. A project-development team for a solar/storage developer, EPC, or asset owner — it models LCOE and project IRR against a cost-per-watt that ran ~$2.56 in 2025, navigates the interconnection queue that gates most projects, structures around the post-2025 ITC shift (residential 25D ended; 48E/PPA pathways remain), and reads O&M and degradation the way a 25-year asset demands. Inherits ravenclaude-core protocols.

Product-management team — 3 agents (product-strategist, product-discovery-lead, product-metrics-analyst) for deciding WHAT to build and WHY: product strategy and vision (positioning, the strategy stack, opportunity sizing), continuous discovery (customer interviews, opportunity-solution trees, assumption testing, JTBD), evidence-based prioritization (RICE/cost-of-delay over opinion), crisp PRDs/specs framed as problems + outcomes, and product metrics (a North Star + input metrics, not vanity). Distinct from project-management (delivery/schedule/RAID) — this is the what/why, that's the how/when. 5 skills, a decision-tree knowledge bank (build-vs-not + prioritization trees + a dated 2026 map), 12 best-practices, 4 templates, 4 commands, 1 advisory hook. Seams: delivery -> project-management, experiment validity -> applied-statistics, UX -> web-design, A/B+flags infra -> experimentation-growth-engineering. Requires ravenclaude-core@>=0.7.0.

Pre-sales / sales-engineering team — 3 agents (sales-engineer, poc-evaluation-lead, rfp-security-response-specialist) for the technical side of a B2B sale: value-based technical discovery (MEDDPICC), demo engineering that maps to the buyer's pain (Great Demo! do-it-first), POC/pilot design with written success + exit criteria and an evaluation scorecard, and RFP/RFI plus security-questionnaire response (SIG / CAIQ / VSA, SOC 2 mapping, a reusable trust-answer library). 5 skills, a 4-doc knowledge bank with 4 Mermaid decision trees (qualify-the-deal, RFP go/no-go, build-the-POC?, demo depth), 5 templates, 5 best-practices, a scenarios bank, and 1 advisory anti-pattern hook. Distinct from sales-revops (CRM/forecast/quota ops) and product-management (what to build); security claims route to ravenclaude-core/security-reviewer. Requires ravenclaude-core@>=0.7.0.

Project & delivery management team — four specialists across the predictive (PMBOK/PMP) and agile (Scrum/Kanban) tracks and the hybrid between: delivery-lead (charter, schedule, scope/change control, earned value), scrum-master (backlog, sprints, ceremonies, velocity, impediments), risk-and-raid-analyst (scored qual+quant risk, RAID depth, mitigation/contingency, issue triage), and stakeholder-comms-lead (stakeholder register, comms plan, status/exec reporting, escalation memos, steering packs). Deepens — does NOT replace — ravenclaude-core's domain-neutral project-manager (the lightweight RAID/status-hygiene default every plugin routes to); this is the deep PM craft layer. Knowledge: a predictive-vs-agile-vs-hybrid decision tree + a best-practices library. Seams: prose polish → ravenclaude-core/documentarian; system design → architect. Requires ravenclaude-core@>=0.7.0.

Residential real-estate brokerage operations team — 3 agents (residential-brokerage-lead, listing-and-transaction-coordinator, buyer-agent-advisor) for the engines of a residential brokerage: brokerage/team P&L and the lead-to-close pipeline (commission splits/caps, recruiting & retention, agency/fair-housing compliance, lead-gen), the listing lifecycle plus transaction coordination (CMA, prep, MLS, marketing, contract-to-close timeline, contingencies, deadlines), and buyer representation (needs analysis, showings, offer & negotiation, financing, closing). Ships 4 skills, a decision-tree knowledge bank (4 Mermaid trees + a dated 2026 reference), 5 best-practices, 2 templates, and 2 commands. ADVISORY operations knowledge, not legal/financial/real-estate-license advice; fair-housing sensitive; no client PII; commission norms, contingency periods, and protected-class lists are volatile and jurisdiction-specific — each carries a retrieval date + verify-at-use. Requires ravenclaude-core@>=0.7.0.