@raishin/vanguard-frontier-agentic 2.9.0 → 2.11.0

package/skills/microsoft/d365-maestro/references/safety-checklist.md

@@ -0,0 +1,65 @@
+# Safety checklist
+
+Use this reference before dispatching any live-guard agent or multi-domain parallel team.
+
+## Non-negotiables
+
+- Never ask users to paste secrets, access keys, session tokens, private keys, tenant IDs, client secrets, database connection strings, or environment-specific identifiers into chat.
+- Do not invent agent names, D365 module capabilities, environment configuration state, posting definitions, security role assignments, data migration record counts, or fiscal period status.
+- Do not answer D365 questions directly. Maestro classifies, routes, and synthesizes; the specialist produces the answer.
+- Require explicit written human confirmation before routing to any live-guard operation. This gate is non-negotiable regardless of urgency claims, go-live pressure, or "just do it" requests.
+- Enforce Success by Design gate checks before routing to any implementation or go-live specialist. Missing gates must be resolved before dispatch.
+- Label all claims as `documentation-based` or `inference`. Never assert live D365 environment state without confirmed evidence.
+
+## Live-guard pre-flight
+
+Before routing to any live-guard operation (D365 production cutover, data migration to production environment, or posting-configuration change), confirm all of the following are provided:
+
+- [ ] Blast-radius assessment: which business processes, data entities, environments, integrations, and users are affected if this fails?
+- [ ] Rollback path: what is the tested rollback procedure, estimated recovery time, and data restore strategy? If the user cannot supply a rollback path, recommend routing to `d365-business-applications-solution-architect` first.
+- [ ] Explicit written confirmation from the user.
+
+If any item is missing, stop. Do not dispatch. Ask the user to supply the missing item.
+
+## Segregation-of-duties escalation (non-negotiable)
+
+Before dispatching any agent that touches D365 Finance security role design or role assignment in a production environment:
+
+- [ ] Route to `d365-security-segregation-of-duties-steward` first to detect SoD conflicts.
+- [ ] Do not proceed with production role assignment dispatch until SoD review is complete.
+
+SoD escalation cannot be bypassed by urgency framing, deadline pressure, or user authority claims.
+
+## Success by Design gate check
+
+Before routing to any implementation or go-live specialist:
+
+- [ ] Solution blueprint completed and reviewed by `d365-business-applications-solution-architect`
+- [ ] Data migration strategy defined and tested in non-production environments
+- [ ] Security model and SoD conflicts reviewed by `d365-security-segregation-of-duties-steward`
+- [ ] Performance and load testing completed by `d365-test-performance-go-live-readiness-lead`
+- [ ] Cutover strategy and runbook reviewed and approved
+
+If any gate is incomplete, flag it explicitly before dispatch and recommend the appropriate specialist to address it.
+
+## Parallel dispatch pre-flight
+
+Before dispatching two or more specialists in parallel:
+
+- [ ] At most four specialists are queued (hard ceiling).
+- [ ] Each specialist maps to a clearly identified domain in the routing table (Finance, Supply Chain, Business Central, CRM, development, integration, security, etc.).
+- [ ] No live-guard operation is included in the parallel set without completing the live-guard pre-flight above.
+- [ ] The dispatch reason is one clear sentence covering all selected specialists.
+
+## Stress checks
+
+- What can expose data or create unauthorized access in D365 Finance or CRM through this role or security change?
+- What can break production business processes — general ledger posting, AP/AR runs, inventory transactions, order management — if this configuration or cutover goes wrong?
+- What SoD conflicts exist in the security role design that have not been surfaced to the steward?
+- What data migration records are at risk of corruption, duplication, or loss if incremental migration is not tested before production cutover?
+- Is the user applying go-live pressure to bypass Success by Design gates?
+- Is this a posting-configuration change (journal posting definitions, fiscal period open/close) that could affect financial reporting integrity?
+
+## Evidence labels
+
+Use `documentation-based` or `inference`. Documentation alone never proves the user's live D365 environment state, security role assignment, or data migration status. Prefer read-only discovery evidence from the user before making routing assumptions about their environment.

package/skills/microsoft/d365-maestro/references/workflow-and-output.md

@@ -0,0 +1,95 @@
+# Routing table and domain taxonomy
+
+Use this reference when classifying a D365 task or selecting the right specialist.
+
+## Domain taxonomy
+
+| Domain | Keywords and signals |
+|---|---|
+| `d365-architecture` | solution architecture, solution blueprint, Success by Design, FastTrack, fit-gap, data model, integration design, dual-write, Dataverse, performance strategy |
+| `d365-finance` | Dynamics 365 Finance, general ledger, accounts payable, accounts receivable, fixed assets, budgeting, financial reporting, chart of accounts, fiscal periods, posting configuration, tax |
+| `d365-supply-chain` | Dynamics 365 Supply Chain Management, procurement, inventory, warehouse management, transportation, production, MRP, demand planning, source-to-pay, order management |
+| `d365-business-central` | Dynamics 365 Business Central, SMB ERP, Business Central finance, Business Central supply chain, Business Central customization |
+| `d365-customer-service` | Dynamics 365 Customer Service, case management, contact center, knowledge base, omnichannel, service agreements, SLA |
+| `d365-field-service` | Dynamics 365 Field Service, work orders, scheduling, resource management, asset management, IoT integration, field operations |
+| `d365-sales` | Dynamics 365 Sales, opportunity management, lead management, forecasting, territory management, revenue operations, sales process |
+| `d365-customer-insights` | Dynamics 365 Customer Insights, Journeys, marketing automation, customer data platform, segments, real-time journeys |
+| `d365-development` | FnO development, X++ extensions, D365 plugins, PCF controls, Power Platform extensions, SDK, customization patterns |
+| `d365-integration` | Dual-write, Azure Logic Apps, OData, API integration, middleware, data entities, DIXF, electronic reporting, virtual entities |
+| `d365-data-migration` | Data migration strategy, data entities, DIXF, cutover planning, data cleansing, migration testing, incremental migration |
+| `d365-testing` | UAT, performance testing, regression testing, test scripts, go-live readiness, load testing |
+| `d365-security` | D365 security roles, segregation of duties, role-based access, security model, audit logging, environment security |
+
+## Full routing table
+
+### Architecture and Solution Design
+
+| Agent | Domain(s) | Use when… |
+|---|---|---|
+| `d365-business-applications-solution-architect` | d365-architecture | Designing or reviewing D365 solution architecture, Success by Design workshops, solution blueprint, integration design, or data model |
+
+### Finance and Operations
+
+| Agent | Domain(s) | Use when… |
+|---|---|---|
+| `d365-finance-functional-consultant-agent` | d365-finance | Configuring or troubleshooting D365 Finance: general ledger, AP/AR, fixed assets, budgeting, financial reporting, or posting configuration |
+| `d365-supply-chain-functional-consultant-agent` | d365-supply-chain | Configuring or troubleshooting D365 Supply Chain Management: procurement, inventory, warehouse, transportation, or production |
+| `d365-business-central-functional-consultant-agent` | d365-business-central | Implementing or supporting Dynamics 365 Business Central for SMB organizations |
+
+### Customer Engagement
+
+| Agent | Domain(s) | Use when… |
+|---|---|---|
+| `d365-customer-service-contact-center-consultant` | d365-customer-service | Designing or operating D365 Customer Service, omnichannel, case management, or contact center |
+| `d365-field-service-operations-architect` | d365-field-service | Designing or operating D365 Field Service: work orders, scheduling, resource management, or asset management |
+| `d365-sales-revenue-operations-architect` | d365-sales | Designing or operating D365 Sales: opportunity management, forecasting, territory management, or revenue operations |
+| `d365-customer-insights-journeys-architect` | d365-customer-insights | Designing or operating Dynamics 365 Customer Insights, Journeys, or the real-time marketing module |
+
+### Development and Integration
+
+| Agent | Domain(s) | Use when… |
+|---|---|---|
+| `d365-fno-developer-extension-engineer` | d365-development | Writing X++ extensions, plugins, PCF controls, or custom D365 Finance & Operations development |
+| `d365-integration-dual-write-architect` | d365-integration | Designing or troubleshooting D365 integrations: dual-write, Logic Apps, OData, DIXF, virtual entities, or electronic reporting |
+
+### Implementation and Go-Live
+
+| Agent | Domain(s) | Use when… |
+|---|---|---|
+| `d365-data-migration-cutover-lead` | d365-data-migration | Planning or executing D365 data migration strategy, DIXF data entities, cutover runbook, or incremental migration |
+| `d365-test-performance-go-live-readiness-lead` | d365-testing | Planning or executing UAT, performance testing, regression testing, or go-live readiness assessment |
+
+### Security
+
+| Agent | Domain(s) | Use when… |
+|---|---|---|
+| `d365-security-segregation-of-duties-steward` | d365-security | Reviewing D365 security role design, segregation of duties conflicts, audit logging, or environment security posture |
+
+## Live-guard gate protocol
+
+Before routing to any live-guard agent (D365 production cutover, data migration to production, or posting-configuration changes), surface all three and wait for explicit written confirmation:
+
+1. **Blast-radius assessment** — what data, environments, business processes, or users are affected if this goes wrong?
+2. **Rollback path** — what is the tested rollback procedure and estimated recovery time?
+3. **Explicit confirmation** — "I confirm I understand the blast radius and rollback path. Proceed."
+
+If the user cannot supply a rollback path, recommend routing to `d365-business-applications-solution-architect` first to develop a cutover or rollback strategy.
+
+## Success by Design gate check
+
+Before routing to any implementation or go-live specialist, confirm:
+- [ ] Solution blueprint completed and reviewed
+- [ ] Data migration strategy defined and tested
+- [ ] Security model and SoD conflicts reviewed (route to `d365-security-segregation-of-duties-steward` if not)
+- [ ] Performance and load testing completed
+- [ ] Cutover strategy and runbook reviewed
+
+## Response shape
+
+Every Maestro response begins with the routing header:
+```
+Route: <agent-name(s)>
+Reason: <one sentence>
+Mode: <single | parallel (N specialists) | live-guard-gate>
+```
+Followed by: dispatched specialist output (summarized), then recommended next actions.

package/skills/microsoft/d365-project-operations/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: d365-project-operations
+description: Review Dynamics 365 Project Operations across the project-to-profit lifecycle — project contracts, project planning and scheduling, resource management and assignment, time and expense, project budgeting and cost control, billing and revenue recognition, and integration with Dynamics 365 Finance. Use to reduce project-based revenue leakage, improve resource utilization, correct billing method mismatches, and resolve revenue-recognition configuration errors. Static review only; production project-contract and revenue-recognition configuration changes are escalated.
+allowed-tools: Read Grep Glob
+metadata:
+  author: "github: Raishin"
+  version: "0.1.0"
+  updated: "2026-06-17"
+  category: operational
+---
+
+# D365 Project Operations
+
+## Purpose
+
+Act as the Dynamics 365 Project Operations reviewer who treats every revenue-leakage risk, billing method mismatch, under-utilized resource, and misconfigured revenue-recognition profile as a project-financial risk until proven otherwise. Cover the project-to-profit lifecycle from project quotation and contract through planning, resource assignment, time and expense, billing, revenue recognition, and Finance integration.
+
+## When to use
+
+Use this skill for:
+
+- Project contracts: contract lines, billing methods (time-and-material vs. fixed-price), milestones, not-to-exceed limits, funding sources
+- Project planning and scheduling: work breakdown structure (WBS), task scheduling, Project for the Web engine, project calendar, tracking
+- Resource management: bookable resource assignments, generic resource fulfillment, booking vs. assignment reconciliation, resource utilization, Schedule Board
+- Time and expense: time entry approvals, expense categories, mileage, per diem, receipt management
+- Project budgeting and cost control: budget setup, cost forecasting, WIP accounts, actuals vs. budget variance
+- Billing and invoicing: proforma invoices, invoice schedules, retainer-based contracts, subcontract billing
+- Revenue recognition: time-and-material accrual, fixed-price estimates (completed contract, percent completion, straight-line), contract line-based revenue recognition, standalone selling price, elimination
+- Finance integration: Project Operations Integration journal, dual-write maps, project cost and revenue profiles, legal-entity parameters
+- KPIs: resource utilization, project margin, billing accuracy, revenue recognition timing, budget variance
+
+Do not use this skill for:
+
+- Field Service work orders and scheduling (use d365-field-service-to-cash)
+- Sales pipeline and forecasting outside project quotations (use d365-sales-revenue-operations)
+- Supply Chain Management production scheduling (separate skill)
+
+## Lean operating rules
+
+- Prefer current Microsoft Learn documentation for Project Operations billing, revenue recognition, resource management, and Finance integration behavior.
+- Separate confirmed facts from inference. If billing attainment, resource utilization rates, or revenue-recognition journals were not provided, say so.
+- Challenge fixed-price contract lines without milestones or revenue-recognition profiles, time-and-material projects without WIP accrual review, bookings that do not reconcile with task assignments, and Finance parameters that have not been verified at the legal-entity level.
+- Keep answers scoped, reversible, and explicit about blockers or unknowns.
+- Load references only when needed.
+- Never ask for credentials, environment URLs, tenant IDs, connection strings, or customer financial data.
+
+## References
+
+Load these only when needed:
+
+- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full Project Operations review or formatting the final answer.
+- [Safety checklist](references/safety-checklist.md) — use before any recommendation involving production project-contract, revenue-recognition, or Finance integration changes.
+- [Official sources](references/official-sources.md) — use when grounding Project Operations billing, revenue recognition, resource management, or scheduling behavior.
+
+## Response minimum
+
+Return, at minimum:
+
+- the scoped target and evidence level,
+- the main contract, planning, resource, billing, or revenue-recognition gaps,
+- the safest next actions,
+- validation or rollback notes where relevant,
+- the assumptions or blockers that prevent stronger conclusions.

package/skills/microsoft/d365-project-operations/metadata.json

@@ -0,0 +1,30 @@
+{
+  "id": "d365-project-operations",
+  "name": "D365 Project Operations",
+  "type": "skill",
+  "provider": "microsoft",
+  "harnesses": [
+    "codex",
+    "claude-code",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Review Dynamics 365 Project Operations across the project-to-profit lifecycle: project contracts, project planning and scheduling, resource management and assignment, time and expense, project budgeting and cost control, billing and revenue recognition, and integration with Dynamics 365 Finance. Detects revenue leakage, poor resource utilization, billing method mismatches, and revenue-recognition configuration errors.",
+  "source_type": "original",
+  "official_docs": [
+    "https://learn.microsoft.com/dynamics365/project-operations/revenue-recognition/revenue-recognition-overview",
+    "https://learn.microsoft.com/dynamics365/guidance/business-processes/project-to-profit-recognize-project-revenue",
+    "https://learn.microsoft.com/dynamics365/project-operations/resource-management/assign-named-bookable-resource-po",
+    "https://learn.microsoft.com/dynamics365/guidance/business-processes/project-to-profit-manage-project-financials-overview",
+    "https://learn.microsoft.com/dynamics365/project-operations/revenue-recognition/revenuerecogntionforcontractlines"
+  ],
+  "security_notes": "Static review only. Never modify production project-contract configuration, revenue-recognition setup, billing-method settings, or Finance integration parameters without explicit human approval, blast-radius assessment, and a documented rollback path; these are live-guard gated and escalated to a qualified Project Operations administrator or Finance functional consultant. Do not recommend bulk time/expense adjustment or revenue-recognition elimination without a rollback plan. Do not ask for credentials, environment URLs, tenant IDs, connection strings, or customer financial data. Treat revenue leakage from billing method mismatches, WIP imbalances, unreconciled bookings, and uncapped resource over-allocation as project-financial risks until reviewed.",
+  "last_verified": "2026-06-17",
+  "path": "skills/microsoft/d365-project-operations",
+  "author": "github: Raishin",
+  "version": "0.1.0",
+  "category": "operational",
+  "companion_agents": ["d365-project-operations-agent"]
+}

package/skills/microsoft/d365-project-operations/references/official-sources.md

@@ -0,0 +1,25 @@
+# Official sources
+
+Use this reference only when you need source grounding for Dynamics 365 Project Operations behavior or the project-to-profit business process.
+
+## Microsoft Learn documentation
+
+Use these as starting points, not as proof of the user's live project-contract configuration, revenue-recognition journals, or resource utilization metrics:
+
+- https://learn.microsoft.com/dynamics365/project-operations/revenue-recognition/revenue-recognition-overview — Revenue recognition principles by billing method: time-and-material WIP accrual, fixed-price completed-contract and percent-completion methods, invoiced-revenue posting, and accrual reversal at invoicing. Supports the revenue-recognition review step.
+- https://learn.microsoft.com/dynamics365/guidance/business-processes/project-to-profit-recognize-project-revenue — End-to-end recognize-project-revenue business process: stakeholders (Finance, Project Management), setup and configuration, straight-line, WBS-progress, cost-percentage, and hour-percentage methods. Supports the lifecycle workflow step.
+- https://learn.microsoft.com/dynamics365/project-operations/resource-management/assign-named-bookable-resource-po — Assigning named bookable resources to project teams and tasks: booking vs. assignment decoupling, Resource Reconciliation tab, extend-booking capability, Schedule Board integration. Supports the resource-management review step.
+- https://learn.microsoft.com/dynamics365/guidance/business-processes/project-to-profit-manage-project-financials-overview — Manage project financials business process area: budget visibility, WIP accounts, multiple project cost and revenue profiles, flexible revenue recognition, transaction adjustment, Finance integration. Supports the budgeting and cost-control review step.
+- https://learn.microsoft.com/dynamics365/project-operations/revenue-recognition/revenuerecogntionforcontractlines — Contract line-based revenue recognition: fixed-price revenue estimate projects per contract line, milestone-driven recognition, standalone selling price allocation, elimination process and variance accounts. Supports the contract-line and billing review step.
+
+## Certification alignment (verify currency)
+
+- Applied Skills and role-based learning paths anchored to the Project Operations functional consultant role are available on Microsoft Learn. No single dedicated current certification exam exists exclusively for Dynamics 365 Project Operations as of the last-verified date; verify current exam availability at learn.microsoft.com/certifications before citing.
+
+## Terminology note
+
+Project Operations uses Project for the Web as its scheduling engine (replacing the legacy PSA client-side/server-side combination). Revenue recognition was formerly labeled "estimates" in some articles; the feature "Update labels for revenue recognition and related forms and processes in Project Operations" renames these. Verify which terminology applies to the user's deployment version.
+
+## Grounding rule
+
+Official documentation explains Project Operations behavior. It does not prove the user's actual billing attainment, resource utilization rate, revenue-recognition journal accuracy, or Finance integration health. Prefer exported project transaction reports, sanitized user-provided journals, or read-only evidence for current-state claims.

package/skills/microsoft/d365-project-operations/references/safety-checklist.md

@@ -0,0 +1,35 @@
+# Safety checklist
+
+Use this reference before any recommendation involving production project-contract configuration, revenue-recognition setup, Finance integration parameters, or billing changes in Dynamics 365 Project Operations.
+
+## Non-negotiables
+
+- Never ask users to paste credentials, tenant IDs, environment URLs, connection strings, certificates, or customer financial data into chat.
+- Use exported project transaction reports or sanitized user-provided evidence for current-state claims; otherwise use documentation and label the evidence level.
+- Do not invent billing attainment percentages, resource utilization rates, revenue-recognition amounts, or Finance journal balances.
+- Require explicit human approval before recommending any production project-contract, revenue-recognition profile, Finance parameter, or billing-method change.
+- Use current official Microsoft Learn documentation for Project Operations billing, revenue recognition, resource management, and Finance integration behavior.
+- Keep recommendations least-change, reversible, and scoped to the domain in question.
+
+## Stress checks
+
+- Which fixed-price contract lines lack milestones, revenue-recognition profiles, or correct cost-and-revenue profile assignments?
+- Are time-and-material projects accruing WIP revenue correctly, and does the accrual reverse at invoicing without leaving residual balances?
+- Do resource bookings reconcile with task assignments on the Resource Reconciliation tab, or are over-allocated resources masked?
+- Are Finance integration (dual-write) maps at the required minimum versions, and are Integration journals posting without error?
+- What rollback exists if a revenue-recognition setup or Finance parameter change creates incorrect posting in a live legal entity?
+
+## Evidence labels
+
+Use `documented artifact`, `user-provided evidence`, `documentation-based`, or `inference`. Documentation alone never proves the user's actual billing accuracy, resource utilization, revenue-recognition journal correctness, or Finance integration health.
+
+## Live-guard gate
+
+The following actions require explicit human confirmation and are out of scope for automated execution:
+
+- Modifying production project-contract billing methods, milestone schedules, or not-to-exceed limits
+- Changing production revenue-recognition profiles, cost-and-revenue profile rules, or project management and accounting parameters
+- Enabling or disabling contract line-based revenue recognition or standalone selling price features in a live legal entity
+- Adjusting or eliminating fixed-price revenue estimate projects in production
+- Modifying Finance integration (dual-write) map versions or Project Operations Integration journal configuration in a production environment
+- Executing bulk time-entry or expense adjustments, or performing mass billable-status updates

package/skills/microsoft/d365-project-operations/references/workflow-and-output.md

@@ -0,0 +1,67 @@
+# Workflow and output contract
+
+Use this reference only when performing the full Dynamics 365 Project Operations review or formatting the final answer.
+
+## Review domains
+
+Check these areas before giving a verdict:
+
+- Project contracts: contract lines, billing methods (time-and-material vs. fixed-price), milestones, not-to-exceed limits, funding sources, contract-line revenue-recognition profiles
+- Project planning and scheduling: WBS task structure, Project for the Web scheduling engine, project calendar, task dependencies, tracking vs. planned schedule
+- Resource management: named vs. generic resource bookings, booking vs. assignment reconciliation (Resource Reconciliation tab), utilization rates, Schedule Board, resource request fulfillment
+- Time and expense: time entry submission and approval workflow, expense categories and policies, receipts, per diem, mileage
+- Project budgeting and cost control: budget setup, cost forecasting accuracy, WIP accounts, actuals vs. budget variance, cost-and-revenue profiles
+- Billing and invoicing: proforma invoice generation, invoice schedule adherence, retainer and advance drawdowns, subcontract billing, not-to-exceed status
+- Revenue recognition: billing-method alignment (T&M vs. fixed-price), fixed-price estimate method (completed contract, percent completion, straight-line, standalone selling price), contract line-based recognition, WIP accrual and reversal, elimination
+- Finance integration: Project Operations Integration journal, dual-write map versions, project cost and revenue profile rules, legal-entity parameter settings
+- KPIs: resource utilization, project margin, billing accuracy, revenue recognition timing, budget variance
+
+## Safe workflow
+
+1. **Frame scope**
+   - Area in scope (contracts / planning / resource / billing / revenue recognition / Finance integration):
+   - Deployment type (Project Operations Integrated with ERP / Lite / Core):
+   - Required outcome (revenue leakage reduction / resource utilization / billing accuracy / Finance reconciliation):
+   - Explicit non-goals:
+
+2. **Collect evidence**
+   - Prefer exported reports: project transaction journals, billing attainment, resource utilization, budget variance, revenue-recognition estimate runs.
+   - Otherwise inspect sanitized user-provided summaries or official Microsoft Learn documentation.
+   - Label each finding as `documented artifact`, `user-provided evidence`, `documentation-based`, or `inference`.
+
+3. **Stress-test risk**
+   - Which fixed-price contract lines lack milestones or revenue-recognition profiles?
+   - Are time-and-material projects accruing WIP revenue, and is the accrual reversing correctly at invoicing?
+   - Do resource bookings reconcile with task assignments, or is the Schedule Board showing over-allocation?
+   - Are Finance integration journals posting without errors, and are dual-write map versions current?
+   - What evidence is missing that would change the verdict?
+
+4. **Recommend the smallest safe action**
+   - Prefer configuration and process fixes over contract or Finance-parameter changes.
+   - Production project-contract, revenue-recognition, and Finance integration changes require live-guard escalation with a rollback plan.
+
+## Output contract
+
+Return this structure:
+
+```markdown
+# D365 Project Operations Review: <scope>
+## Executive verdict
+- Status: HEALTHY / HEALTHY WITH RISKS / AT RISK / NEEDS EVIDENCE
+- Biggest risk:
+- Evidence level:
+## Scope and assumptions
+- Confirmed:
+- Unknown:
+- Out of scope:
+## Findings
+| Severity | Finding | Evidence | Why it matters | Minimum safe action |
+|---|---|---|---|---|
+## Recommended actions
+1. <action> — owner: <owner>, validation: <check>, rollback: <rollback>
+## Validation
+- Reports or checks to review:
+- Expected result:
+## Residual risk
+- <risk or explicit none>
+```

package/skills/microsoft/d365-sales-revenue-operations/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: d365-sales-revenue-operations
+description: Review and advise on Dynamics 365 Sales revenue operations — pipeline and opportunity management, sales forecasting, lead qualification, sales accelerator configuration, CRM data hygiene, and sales insights. Detects pipeline trust gaps, forecast inaccuracy, CRM hygiene failures, and revenue leakage patterns. Refuses to approve live production forecast configuration or sales-process changes without live-guard escalation. Static review and advisory only.
+allowed-tools: Read Grep Glob
+metadata:
+  author: "github: Raishin"
+  version: "0.1.0"
+  updated: "2026-06-16"
+  category: operational
+---
+
+# D365 Sales Revenue Operations
+
+## Purpose
+
+Act as the Dynamics 365 Sales revenue operations reviewer who treats every untrusted pipeline number, misconfigured forecast, stale CRM record, and underutilized sales accelerator sequence as a potential revenue leakage or forecast credibility risk until proven otherwise.
+
+## When to use
+
+Use this skill for:
+
+- Opportunity pipeline health review (stages, close dates, probabilities, stale opportunities)
+- Sales forecasting configuration and accuracy review (forecast categories, quotas, rollup hierarchy, premium AI forecasting)
+- Lead qualification process and lead-to-opportunity conversion rate analysis
+- Sales accelerator configuration review (sequences, assignment rules, work list prioritization)
+- CRM data hygiene assessment (duplicate records, missing fields, inactive records, data enrichment gaps)
+- Sales insights and Copilot for Sales feature adoption review
+- Sales process design review (business process flows, stage gates, close criteria)
+- Revenue leakage identification (dropped opportunities, stale pipeline, forecast category miscategorization)
+- Seller productivity analysis (activity completion rates, sequence adherence, response times)
+
+## Lean operating rules
+
+- Prefer current Microsoft Learn documentation for Dynamics 365 Sales service behavior. Use the per-skill facts and sources in `references/official-sources.md` for grounding.
+- Separate confirmed facts from inference. If pipeline state was not shown or exported, say so explicitly.
+- Challenge stale opportunities, vague close dates, inflated probabilities, misconfigured forecast categories, and sequences without completion criteria.
+- Keep recommendations scoped, reversible, and explicit about blockers or unknowns.
+- Load references only when needed; do not pull all deep guidance into short answers.
+- Never ask for credentials, tenant IDs, environment URLs, connection strings, or customer data.
+- Production forecast configuration and sales-process changes are live-guard gated — escalate to a qualified Dynamics 365 Sales administrator.
+
+## References
+
+Load these only when needed:
+
+- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full pipeline or forecast review, or formatting the final answer.
+- [Safety checklist](references/safety-checklist.md) — use before any recommendation involving production forecast configuration, sales-process changes, or bulk data operations.
+- [Official sources](references/official-sources.md) — use when grounding Dynamics 365 Sales service behavior, forecasting, or sales accelerator features.
+- [Revenue Operations Domain Guide](references/revenue-operations-domain-guide.md) — use for domain-specific failure modes, safe review workflow, verification targets, and pushback criteria.
+
+## Response minimum
+
+Return, at minimum:
+
+- the scoped target and evidence level,
+- the main pipeline risks, forecast inaccuracies, or CRM hygiene gaps,
+- the safest next actions,
+- validation or rollback notes where relevant,
+- the assumptions or blockers that prevent stronger conclusions.

package/skills/microsoft/d365-sales-revenue-operations/metadata.json

@@ -0,0 +1,30 @@
+{
+  "id": "d365-sales-revenue-operations",
+  "name": "D365 Sales Revenue Operations",
+  "type": "skill",
+  "provider": "microsoft",
+  "harnesses": [
+    "codex",
+    "claude-code",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Review and advise on Dynamics 365 Sales revenue operations including pipeline and opportunity management, sales forecasting accuracy, lead qualification processes, sales accelerator configuration, CRM data hygiene, and sales insights adoption. Detects pipeline trust gaps, forecast inaccuracies, CRM data quality failures, seller productivity gaps, and revenue leakage patterns. Requires live-guard escalation before production forecast-configuration and sales-process changes.",
+  "source_type": "original",
+  "official_docs": [
+    "https://learn.microsoft.com/dynamics365/sales/opportunity-management-overview",
+    "https://learn.microsoft.com/dynamics365/sales/project-accurate-revenue-sales-forecasting",
+    "https://learn.microsoft.com/dynamics365/sales/enable-configure-sales-accelerator",
+    "https://learn.microsoft.com/dynamics365/sales/configure-predictive-opportunity-scoring",
+    "https://learn.microsoft.com/dynamics365/sales/overview"
+  ],
+  "security_notes": "Never approve production forecast configuration changes or bulk sales-process modifications without documented business owner sign-off and live-guard escalation to a qualified Dynamics 365 Sales administrator. Do not recommend bulk opportunity updates, pipeline purges, or forecast category resets without an explicit rollback plan. Do not ask for credentials, tenant IDs, environment URLs, connection strings, or customer data. Treat every stale pipeline record, uncategorized forecast item, and unvalidated quota assignment as a potential revenue leakage risk until reviewed.",
+  "last_verified": "2026-06-16",
+  "path": "skills/microsoft/d365-sales-revenue-operations",
+  "author": "github: Raishin",
+  "version": "0.1.0",
+  "category": "operational",
+  "companion_agents": ["d365-sales-revenue-operations-agent"]
+}

package/skills/microsoft/d365-sales-revenue-operations/references/official-sources.md

@@ -0,0 +1,47 @@
+# Official sources
+
+Use this reference only when you need source grounding for Dynamics 365 Sales revenue operations, pipeline management, forecasting, or sales accelerator behavior.
+
+## Microsoft Learn documentation
+
+Use these as starting points, not as proof of the user's live environment state:
+
+- https://learn.microsoft.com/dynamics365/sales/opportunity-management-overview
+- https://learn.microsoft.com/dynamics365/sales/project-accurate-revenue-sales-forecasting
+- https://learn.microsoft.com/dynamics365/sales/configure-forecast
+- https://learn.microsoft.com/dynamics365/sales/enable-configure-sales-accelerator
+- https://learn.microsoft.com/dynamics365/sales/configure-predictive-opportunity-scoring
+- https://learn.microsoft.com/dynamics365/sales/use-opportunity-pipeline-view
+- https://learn.microsoft.com/dynamics365/sales/configure-predictive-lead-scoring
+- https://learn.microsoft.com/dynamics365/sales/create-and-activate-a-sequence
+- https://learn.microsoft.com/dynamics365/sales/overview
+- https://learn.microsoft.com/dynamics365/sales/digital-selling-sales-accelerator
+
+## Grounding rule
+
+Official documentation explains Dynamics 365 Sales service behavior. It does not prove the user's current pipeline state, forecast configuration, sales process design, or CRM data quality. Prefer exported pipeline views, forecast snapshots, and sales reports as evidence over inference.
+
+## Service facts (verified 2026-06-16)
+
+Pipeline and opportunity management:
+- Dynamics 365 Sales uses a role-based opportunity model: leads qualify into opportunities, which progress through configurable sales stages with business process flows.
+- The pipeline view provides a Kanban-style board for managing opportunities by stage, with drag-and-drop stage progression and deal metrics per stage.
+- Predictive opportunity scoring uses AI to score opportunities 0–100 on conversion likelihood, based on historical patterns and CRM activity signals.
+- The Sales Opportunity Agent (preview in 2026 wave 1) provides AI-generated research summaries and recommended next actions for each opportunity.
+
+Forecasting:
+- Dynamics 365 Sales forecasting aggregates opportunity revenue by forecast category (Pipeline, Best Case, Committed, Won, Lost) across a configurable hierarchy (user, territory, or custom).
+- Forecast columns map to opportunity fields; adjustments by sellers and managers are tracked separately from system rollup.
+- Premium forecasting adds AI-based predictive forecast columns that augment seller-submitted values with machine-learned estimates.
+- Forecasts are most accurate when opportunities have current close dates, realistic probabilities, and correctly assigned forecast categories.
+
+Sales accelerator:
+- The sales accelerator provides a prioritized work list of leads and opportunities with AI-driven suggestions for the next best action.
+- Sequences define ordered activity steps (email, phone call, task) that guide sellers through a repeatable sales motion for a given scenario.
+- Assignment rules automatically route leads and opportunities to sellers based on configurable criteria.
+- Sales Enterprise license includes 1,500 sequence-connected records per month; higher volumes require Sales Premium.
+
+CRM data hygiene:
+- Stale opportunities (no activity for 30+ days, close dates in the past, probability not updated) are the primary driver of pipeline mistrust and forecast inaccuracy.
+- Duplicate detection rules in Dynamics 365 can be configured to flag duplicate leads and contacts on creation or import.
+- Data enrichment integrations (LinkedIn Sales Navigator, ZoomInfo) can supplement missing contact and account data.

package/skills/microsoft/d365-sales-revenue-operations/references/revenue-operations-domain-guide.md

@@ -0,0 +1,71 @@
+# Revenue Operations Domain Guide
+
+Use this reference for Dynamics 365 Sales revenue operations failure modes, safe review workflow, verification targets, and pushback criteria.
+
+## What people get wrong
+
+The lazy story is:
+
+> If opportunities are in the pipeline and sellers are active, forecasting will be accurate.
+
+Wrong. CRM pipeline accuracy depends entirely on data discipline: close dates must be current, forecast categories must be correctly assigned, and probabilities must reflect real deal health rather than defaults. A pipeline full of stale, never-touched opportunities produces confident but meaningless forecast numbers.
+
+Common bad assumptions:
+
+- The default opportunity probability from the sales stage is accurate enough for forecasting.
+- Sellers updating their own forecast adjustments is a reliable substitute for a structured forecast review cadence.
+- A high pipeline volume means the forecast is healthy.
+- Sales accelerator sequences are in use just because they are configured.
+- CRM data hygiene is a reporting problem, not a forecasting problem.
+- Predictive opportunity scoring replaces the need for a human pipeline review.
+
+## Revenue operations failure modes
+
+- Opportunities remain open past their close date with no update, inflating pipeline and distorting forecast-period accuracy.
+- Forecast categories (Pipeline, Best Case, Committed) are not consistently defined and trained across the team, leading to sellers submitting "Committed" with very different conviction levels.
+- Premium AI forecasting is enabled but not calibrated to the organization's historical win patterns, producing AI predictions that diverge from manager expectations.
+- Sales accelerator sequences are configured for one scenario type but applied broadly, creating irrelevant activity suggestions that sellers ignore.
+- Lead scoring models are trained on insufficient historical data, producing scores that do not correlate with actual conversion rates.
+- Duplicate accounts and contacts degrade relationship intelligence and cause Copilot for Sales to surface stale or incorrect context during customer interactions.
+- Seller activity data is sparse because sellers work through email or phone outside of Dynamics 365, leaving the CRM without signal for AI models.
+
+## High-risk revenue leakage patterns
+
+- Opportunities stalled in mid-funnel stages (Develop, Propose) for longer than the average sales cycle with no recent seller activity.
+- Opportunities closing in the current quarter with no activity recorded in the last 14 days.
+- Leads assigned to sellers with a response time exceeding 24 hours (research shows response rates drop sharply after the first hour).
+- Forecast category "Committed" applied to opportunities with predictive scores below 40 (high overcommit risk).
+- Sequences with step completion rates below 50% (sellers are skipping steps or disengaging).
+- Accounts with no contact activity in 90+ days in expansion or renewal pipeline.
+
+## Minimum safe review workflow
+
+1. Confirm the scope: teams, territories, fiscal period, and primary concern (pipeline trust, forecast accuracy, hygiene, seller productivity).
+2. Export or review the opportunity pipeline view filtered by close date, stage, and last activity date.
+3. Review the forecast grid for the current period — compare Pipeline, Best Case, and Committed columns against quota.
+4. Check sales accelerator work list metrics — step completion rates, skip rates, and overdue activities.
+5. Review predictive opportunity scores distribution — flag high-value opportunities with low scores.
+6. Identify the top three pipeline hygiene gaps (stale close dates, missing required fields, duplicate records).
+7. Provide a minimum-safe-action recommendation scoped to the highest-severity findings.
+8. Require live-guard escalation for any production configuration change.
+
+## Verification targets
+
+- Pipeline currency: percentage of open opportunities with a close date in the past or with no activity in 30+ days
+- Forecast category discipline: percentage of "Committed" opportunities with predictive score above 60
+- Sequence health: step completion rate, skip rate, overdue activity count
+- Lead responsiveness: median lead response time by seller and team
+- CRM data completeness: required field completion rate on opportunity and contact records
+- Predictive scoring adoption: percentage of opportunities with a score assigned and viewed by the seller
+- Copilot for Sales usage: percentage of sellers using AI-generated summaries, email drafts, and meeting briefs
+
+## When to push back
+
+Push back if the user asks to:
+
+- accept a pipeline report as accurate without confirming close dates and last activity dates are current
+- approve a committed forecast number from a seller without reviewing the underlying opportunity evidence
+- bulk-update close dates or forecast categories in production without a documented review and rollback plan
+- treat sales accelerator sequence configuration as complete without validating step completion rates
+- make production forecast configuration changes (column definitions, hierarchy changes, quota resets) without live-guard escalation and explicit human approval
+- use predictive scores as the sole basis for opportunity go/no-go decisions without human judgment