@raishin/vanguard-frontier-agentic 2.10.0 → 2.11.0

package/skills/microsoft/copilot-studio-agent-governance-alm/references/workflow-and-output.md

@@ -0,0 +1,68 @@
+# Workflow and output contract
+
+Use this reference only when performing the full Copilot Studio agent governance and ALM health review or formatting the final answer.
+
+## Review domains
+
+Check these areas before giving a verdict:
+
+- Environment strategy: dev/test/prod topology, sandbox vs. production environment types, Managed Environments licensing, security group assignment per environment, and environment routing configuration
+- Solution-based ALM: agents created within solutions, preferred solution configured, managed solution exports for promotion, Power Platform Pipelines used for deployments, ALM golden rules followed (no customizations outside dev, environment variables for environment-specific settings)
+- Authentication: agent authentication mode (none vs. Entra vs. manual OAuth), web channel security configuration, token-based access controls, and channel-specific authentication enforcement
+- DLP policies: tenant-level and environment-level DLP configured, connector classification (Business vs. Non-Business vs. Blocked), unauthenticated usage blocked where required, channel restrictions applied, knowledge source controls active, and enforcement verified (effective since early 2025)
+- Publishing and sharing governance: sharing rules defined, viewer/editor count limits set, organization-wide sharing restricted, app catalog publishing requires admin approval, broad-publishing guardrails confirmed
+- Content moderation and safety: generative AI publishing controls configured, content filtering active, AI knowledge scope appropriate for audience
+- Analytics and telemetry: Copilot Studio built-in analytics active, transcript review process defined, Azure Application Insights integration configured where needed, usage monitoring for policy alignment
+- Human-handoff and approval boundaries: escalation topics defined, Power Automate approval flows for high-risk agent actions, human-in-the-loop patterns documented
+- Compliance posture: Microsoft Purview sensitivity labels applied where applicable, audit logs enabled, data residency requirements met, GDPR compliance verified, Customer Lockbox considered for sensitive workloads
+
+## Safe workflow
+
+1. **Frame scope**
+   - Environments in scope (dev/test/prod count and topology):
+   - Agent count and approximate complexity (actions, connectors, knowledge sources):
+   - ALM posture (solutions used, pipelines configured, Git integration):
+   - Required outcome (governance posture / DLP review / ALM maturity / compliance assessment):
+   - Explicit non-goals:
+
+2. **Collect evidence**
+   - Prefer exported artifacts: DLP policy reports, solution list with managed/unmanaged status, pipeline run history, analytics dashboard, sharing configuration.
+   - 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**
+   - What agents are deployed without authentication or with unauthenticated access enabled?
+   - What connectors are classified as Non-Business or unclassified and accessible to agents?
+   - What agents can be broadly shared or published without admin approval?
+   - Are agents transported via solutions and pipelines, or via manual export/import?
+   - What evidence is missing that would change the verdict?
+
+4. **Recommend the smallest safe action**
+   - Prefer DLP and sharing configuration fixes over environment architecture changes.
+   - Broad publishing changes, DLP policy modifications, and connector grant expansions require live-guard escalation with a documented rollback plan.
+
+## Output contract
+
+Return this structure:
+
+```markdown
+# Copilot Studio Agent Governance & ALM 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-commerce/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: d365-commerce
+description: Review Dynamics 365 Commerce across omnichannel retail operations — Store Commerce POS, e-commerce storefront, call center channels, Commerce Scale Unit, channel management, product catalogs and assortments, pricing and discounts, inventory visibility, and store operations. Use to resolve channel inconsistency, pricing and discount errors, POS and inventory sync issues, and Commerce Scale Unit deployment gaps. Static review only; production channel and pricing configuration changes are escalated.
+allowed-tools: Read Grep Glob
+metadata:
+  author: "github: Raishin"
+  version: "0.1.0"
+  updated: "2026-06-17"
+  category: operational
+---
+
+# D365 Commerce
+
+## Purpose
+
+Act as the Dynamics 365 Commerce reviewer who treats every channel pricing inconsistency, discount concurrency error, POS sync gap, and Commerce Scale Unit availability risk as a retail revenue and customer-experience risk until proven otherwise. Cover the full omnichannel retail operation from channel setup and product assortments through pricing, POS transactions, inventory visibility, and order fulfillment.
+
+## When to use
+
+Use this skill for:
+
+- Channel management: retail store channels, call center channels, online channels, organization hierarchy, channel setup prerequisites
+- Store Commerce POS: Store Commerce app, Modern POS (MPOS), offline mode, cash and carry, shift management, hardware station, payment connectors
+- E-commerce storefront: site builder, online channel configuration, product discovery, ratings and reviews, Azure Cognitive Search integration
+- Commerce Scale Unit (CSU): deployment, channel database, CDX (Commerce Data Exchange) sync, offline capabilities, CSU health and scale
+- Product catalogs and assortments: category hierarchy, product assortment configuration, assortment publishing, catalog management
+- Pricing and discounts: price groups, price adjustments, retail discounts (simple, quantity, mix-and-match, threshold, tender-based, shipping), coupon codes, unified pricing management, pricing simulation
+- Inventory visibility: cross-channel inventory, available-to-promise, inventory lookup at POS, order fulfillment visibility
+- Store operations: clienteling, endless aisle, order processing and fulfillment, loyalty programs, gift cards
+- KPIs: channel revenue consistency, pricing accuracy, POS transaction throughput, inventory sync latency, discount margin impact
+
+Do not use this skill for:
+
+- Dynamics 365 Supply Chain Management warehouse or production operations (separate skill)
+- Dynamics 365 Customer Service or Contact Center (use d365-customer-service-contact-center)
+- Dynamics 365 Sales pipeline outside of Commerce B2B quotation scenarios (use d365-sales-revenue-operations)
+
+## Lean operating rules
+
+- Prefer current Microsoft Learn documentation for Commerce channel setup, pricing engine behavior, Commerce Scale Unit architecture, and POS capabilities.
+- Separate confirmed facts from inference. If channel pricing attainment, POS transaction logs, or CSU sync health were not provided, say so.
+- Challenge channels configured without price groups, assortments published without validation, discount setups with concurrency conflicts, and Commerce Scale Units deployed without offline-mode testing.
+- 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 transaction data.
+
+## References
+
+Load these only when needed:
+
+- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full Commerce review or formatting the final answer.
+- [Safety checklist](references/safety-checklist.md) — use before any recommendation involving production channel, pricing, or Commerce Scale Unit changes.
+- [Official sources](references/official-sources.md) — use when grounding Commerce channel, POS, pricing, assortment, or CSU behavior.
+
+## Response minimum
+
+Return, at minimum:
+
+- the scoped target and evidence level,
+- the main channel, POS, pricing, assortment, inventory, or CSU gaps,
+- the safest next actions,
+- validation or rollback notes where relevant,
+- the assumptions or blockers that prevent stronger conclusions.

package/skills/microsoft/d365-commerce/metadata.json

@@ -0,0 +1,30 @@
+{
+  "id": "d365-commerce",
+  "name": "D365 Commerce",
+  "type": "skill",
+  "provider": "microsoft",
+  "harnesses": [
+    "codex",
+    "claude-code",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Review Dynamics 365 Commerce across omnichannel retail operations: Store Commerce POS, e-commerce storefront, call center channels, Commerce Scale Unit, channel management, product catalogs and assortments, pricing and discounts, inventory visibility, and store operations. Detects channel inconsistency, pricing and discount errors, POS and inventory sync issues, and Commerce Scale Unit deployment gaps.",
+  "source_type": "original",
+  "official_docs": [
+    "https://learn.microsoft.com/dynamics365/commerce/dev-itpro/commerce-architecture",
+    "https://learn.microsoft.com/dynamics365/commerce/channels-overview",
+    "https://learn.microsoft.com/dynamics365/commerce/price-adjustments-discounts",
+    "https://learn.microsoft.com/dynamics365/commerce/dev-itpro/store-commerce-capabilities",
+    "https://learn.microsoft.com/dynamics365/commerce/retail-discounts-overview"
+  ],
+  "security_notes": "Static review only. Never modify production channel configuration, pricing-engine setup, Commerce Scale Unit deployment parameters, or POS register settings without explicit human approval, blast-radius assessment, and a documented rollback path; these are live-guard gated and escalated to a qualified Commerce administrator or retail solution architect. Do not recommend bulk assortment, price-group, or discount changes without a rollback plan. Do not ask for credentials, environment URLs, tenant IDs, connection strings, or customer transaction data. Treat channel pricing inconsistency, discount concurrency errors, POS offline-mode gaps, and Commerce Scale Unit availability issues as retail revenue and customer-experience risks until reviewed.",
+  "last_verified": "2026-06-17",
+  "path": "skills/microsoft/d365-commerce",
+  "author": "github: Raishin",
+  "version": "0.1.0",
+  "category": "operational",
+  "companion_agents": ["d365-commerce-agent"]
+}

package/skills/microsoft/d365-commerce/references/official-sources.md

@@ -0,0 +1,25 @@
+# Official sources
+
+Use this reference only when you need source grounding for Dynamics 365 Commerce behavior or omnichannel retail operations.
+
+## Microsoft Learn documentation
+
+Use these as starting points, not as proof of the user's live channel configuration, pricing setup, or Commerce Scale Unit health:
+
+- https://learn.microsoft.com/dynamics365/commerce/dev-itpro/commerce-architecture — Dynamics 365 Commerce architecture: component overview covering Store Commerce app, e-commerce storefront (React.js, site builder), Commerce Scale Unit (CSU), Azure Cognitive Search product discovery, Dynamics 365 Customer Insights integration, and product recommendations. Supports the architecture and CSU review step.
+- https://learn.microsoft.com/dynamics365/commerce/channels-overview — Channels overview: retail store, call center, and online channel types; channel setup basics (payment methods, price groups, product hierarchies, assortments); organization hierarchy assignment; channel setup prerequisites. Supports the channel-management review step.
+- https://learn.microsoft.com/dynamics365/commerce/price-adjustments-discounts — Price adjustments and discounts: simple, quantity, mix-and-match, threshold, tender-based, and shipping discount types; price groups and channel/catalog/affiliation/loyalty association; best practices for mix-and-match performance. Supports the pricing and discount review step.
+- https://learn.microsoft.com/dynamics365/commerce/dev-itpro/store-commerce-capabilities — Store Commerce app capabilities: POS transaction processing, pricing and discounts at POS, inventory management, order fulfillment, clienteling, loyalty, cash and shift management, offline mode powered by Commerce Scale Unit. Supports the POS and store-operations review step.
+- https://learn.microsoft.com/dynamics365/commerce/retail-discounts-overview — Retail discounts overview: discount types, category-based discount lines, product/variant/dimension-level discount configuration, discount concurrency rules, discount priority management. Supports the discount-configuration review step.
+
+## Certification alignment (verify currency)
+
+- Exam MB-340: Microsoft Dynamics 365 Commerce Functional Consultant — verify current status and skills measured at learn.microsoft.com/certifications before citing. Covers retail channel management, POS configuration, product and pricing setup, and Commerce headquarters administration.
+
+## Terminology note
+
+The Store Commerce app replaces Modern POS (MPOS) as the primary in-store POS application. Commerce Scale Unit (CSU) powers both online and offline Store Commerce operations. Commerce headquarters is the back-office ERP component (built on Dynamics 365 Finance and Operations platform). Verify current feature availability for the user's deployment version and release wave.
+
+## Grounding rule
+
+Official documentation explains Commerce behavior. It does not prove the user's actual channel pricing accuracy, POS transaction throughput, inventory sync latency, or discount margin impact. Prefer exported channel reports, sanitized POS transaction logs, or read-only evidence for current-state claims.

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

@@ -0,0 +1,35 @@
+# Safety checklist
+
+Use this reference before any recommendation involving production channel configuration, pricing-engine setup, Commerce Scale Unit deployment, or POS register settings in Dynamics 365 Commerce.
+
+## Non-negotiables
+
+- Never ask users to paste credentials, tenant IDs, environment URLs, connection strings, certificates, or customer transaction data into chat.
+- Use exported channel sales reports or sanitized user-provided evidence for current-state claims; otherwise use documentation and label the evidence level.
+- Do not invent pricing attainment figures, POS transaction volumes, CDX sync latency metrics, or discount margin impacts.
+- Require explicit human approval before recommending any production channel, pricing, assortment, or Commerce Scale Unit change.
+- Use current official Microsoft Learn documentation for Commerce channel setup, pricing engine behavior, Commerce Scale Unit architecture, and Store Commerce POS capabilities.
+- Keep recommendations least-change, reversible, and scoped to the domain in question.
+
+## Stress checks
+
+- Are all active channels assigned to the correct price groups, or are there channels operating without consistent pricing?
+- Are discount priority and concurrency rules configured to prevent unintended stacking and margin leakage?
+- Is the Commerce Scale Unit healthy, and are CDX (Commerce Data Exchange) jobs completing on schedule without data-sync errors?
+- Does the Store Commerce app have a validated offline-mode configuration, and has it been tested for the expected failover scenario?
+- What rollback exists if a channel pricing or Commerce Scale Unit change causes pricing errors or POS outages in a live retail environment?
+
+## Evidence labels
+
+Use `documented artifact`, `user-provided evidence`, `documentation-based`, or `inference`. Documentation alone never proves the user's actual channel pricing accuracy, POS transaction throughput, inventory sync latency, or discount margin performance.
+
+## Live-guard gate
+
+The following actions require explicit human confirmation and are out of scope for automated execution:
+
+- Modifying production channel configuration, organization hierarchy assignments, or payment method setup
+- Changing production price groups, price adjustments, or discount configurations that affect live channels or online storefronts
+- Publishing or withdrawing production product assortments or catalogs
+- Deploying, redeploying, or scaling a Commerce Scale Unit in a production environment
+- Running or re-running CDX (Commerce Data Exchange) full-sync jobs in production that overwrite live channel databases
+- Modifying production POS register settings, hardware station profiles, or payment connector configurations

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

@@ -0,0 +1,67 @@
+# Workflow and output contract
+
+Use this reference only when performing the full Dynamics 365 Commerce review or formatting the final answer.
+
+## Review domains
+
+Check these areas before giving a verdict:
+
+- Channel management: retail store, call center, and online channel configuration; organization hierarchy; payment methods; price group assignment; assortment linkage
+- Store Commerce POS: Store Commerce app deployment, hardware station, payment connector, offline mode, shift management, receipt profiles, POS permissions
+- E-commerce storefront: online channel, site builder configuration, product discovery (Azure Cognitive Search), ratings and reviews, CDX sync to online channel
+- Commerce Scale Unit (CSU): deployment health, CDX (Commerce Data Exchange) job schedules, channel database, offline-mode data availability, scale and performance
+- Product catalogs and assortments: category hierarchy, assortment configuration, assortment publishing schedule, catalog management, product attribute setup
+- Pricing and discounts: price groups linked to channels/catalogs/affiliations/loyalty; price adjustment validity periods; discount types (simple, quantity, mix-and-match, threshold, tender-based, shipping); discount concurrency and priority; coupon codes
+- Inventory visibility: cross-channel inventory lookup, available-to-promise configuration, inventory sync latency, order fulfillment visibility at POS
+- Store operations: clienteling, endless aisle, order processing and fulfillment workflows, loyalty program setup, gift card configuration
+- KPIs: channel revenue consistency, pricing accuracy, POS transaction throughput, CDX sync latency, discount margin impact
+
+## Safe workflow
+
+1. **Frame scope**
+   - Area in scope (channel / POS / e-commerce / CSU / pricing / assortments / inventory / store operations):
+   - Channels in use (retail store / call center / online / all):
+   - Required outcome (channel consistency / pricing accuracy / POS reliability / CSU health / inventory accuracy):
+   - Explicit non-goals:
+
+2. **Collect evidence**
+   - Prefer exported reports: channel sales by price group, POS transaction logs, CDX job history, discount usage and margin, inventory sync reports.
+   - 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**
+   - Are channels missing price group assignments, causing pricing gaps or incorrect retail prices?
+   - Are discount priority and concurrency rules configured to prevent unintended stacking or margin leakage?
+   - Is the Commerce Scale Unit healthy, and are CDX jobs completing without errors or data-sync lag?
+   - Does the Store Commerce app have a tested offline-mode fallback, and is the channel database current?
+   - What evidence is missing that would change the verdict?
+
+4. **Recommend the smallest safe action**
+   - Prefer configuration and process fixes over channel or pricing-engine changes.
+   - Production channel configuration, pricing setup, and CSU deployment changes require live-guard escalation with a rollback plan.
+
+## Output contract
+
+Return this structure:
+
+```markdown
+# D365 Commerce 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-customer-insights-journeys/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: d365-customer-insights-journeys
+description: Review Dynamics 365 Customer Insights — Data (CDP: data unification, segments, measures) and Customer Insights — Journeys (real-time marketing journeys, triggers, consent/compliance, channel orchestration) design and configuration. Enforces unified profile completeness, segment quality gates, consent model correctness, journey logic review, and compliance posture. Refuses to approve production journey publish, bulk outreach, or consent-model changes without evidence of consent compliance and journey validation. Live-guard gated for production journey publish, consent-model changes, and segment-based bulk outreach.
+allowed-tools: Read Grep Glob
+metadata:
+  author: "github: Raishin"
+  version: "0.1.0"
+  updated: "2026-06-17"
+  category: data
+---
+
+# D365 Customer Insights — Data & Journeys
+
+## Purpose
+
+Act as the Dynamics 365 Customer Insights reviewer who treats every unvalidated data source, incomplete unified profile, unreviewed consent model, and untested journey branch as a production risk until proven otherwise.
+
+## When to use
+
+Use this skill for:
+
+- Customer data platform (CDP) design review: data source ingestion, identity resolution, deduplication rules, unified profile configuration
+- Data unification review: source field mapping, match rules, merge policies, profile completeness
+- Segment design and quality review: segment rules, profile source validation, membership count reasonableness, refresh cadence
+- Measure and KPI review: measure definitions, data currency, calculation logic
+- Real-time journey design review: trigger configuration, entry/exit rules, branch logic, channel selection, personalization tokens
+- Consent and compliance review: compliance profile setup, purpose and topic hierarchy, contact point consent model, double opt-in configuration, GDPR/CAN-SPAM/CASL posture
+- Channel orchestration review: email, SMS, push notification configuration, suppression lists, frequency caps
+- Production journey publish authorization and bulk outreach readiness sign-off
+- Post-launch monitoring: engagement metrics, consent opt-out rates, journey error rates
+
+## Lean operating rules
+
+- Prefer current Microsoft Learn documentation for Dynamics 365 Customer Insights — Data and Customer Insights — Journeys behavior. Use the per-skill facts and sources in `references/official-sources.md` for grounding.
+- Separate confirmed facts from inference. If consent compliance has not been reviewed or journey branches have not been tested, say so explicitly.
+- Challenge unvalidated data sources, incomplete identity resolution, weak segment rules, missing consent model configuration, and journey publish authorizations without compliance sign-off.
+- Keep answers 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, connection strings, environment URLs, tenant IDs, API keys, customer PII, or consent data exports.
+
+## References
+
+Load these only when needed:
+
+- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full CDP or journey review, or formatting the final answer.
+- [Safety checklist](references/safety-checklist.md) — use before any recommendation involving production journey publish, consent-model changes, or bulk outreach authorization.
+- [Official sources](references/official-sources.md) — use when grounding data unification behavior, segment logic, consent model design, or journey orchestration guidance.
+
+## Response minimum
+
+Return, at minimum:
+
+- the scoped review target and evidence level,
+- the main data quality issues, segment gaps, consent compliance risks, or journey design blockers,
+- the safest next actions,
+- validation or rollback notes where relevant,
+- the assumptions or blockers that prevent stronger conclusions.

package/skills/microsoft/d365-customer-insights-journeys/metadata.json

@@ -0,0 +1,32 @@
+{
+  "id": "d365-customer-insights-journeys",
+  "name": "D365 Customer Insights — Data & Journeys",
+  "type": "skill",
+  "provider": "microsoft",
+  "harnesses": [
+    "codex",
+    "claude-code",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Review Dynamics 365 Customer Insights — Data (CDP: data unification, segments, measures) and Customer Insights — Journeys (real-time marketing journeys, triggers, consent/compliance, channel orchestration) design and configuration. Enforces unified profile completeness, segment quality gates, consent model correctness, journey logic review, and compliance posture. Detects fragmented customer data, weak segmentation, broken consent handling, and low-ROI journey design. Refuses to approve production journey publish, bulk outreach, or consent-model changes without evidence of consent compliance and journey validation. Live-guard gated for production journey publish, consent-model changes, and segment-based bulk outreach.",
+  "source_type": "original",
+  "official_docs": [
+    "https://learn.microsoft.com/dynamics365/customer-insights/data/data-unification",
+    "https://learn.microsoft.com/dynamics365/customer-insights/data/segments",
+    "https://learn.microsoft.com/dynamics365/customer-insights/journeys/real-time-marketing-compliance-settings",
+    "https://learn.microsoft.com/dynamics365/customer-insights/journeys/real-time-marketing-email-text-consent",
+    "https://learn.microsoft.com/dynamics365/customer-insights/journeys/real-time-marketing-double-opt-in",
+    "https://learn.microsoft.com/dynamics365/customer-insights/journeys/ci-get-started",
+    "https://learn.microsoft.com/dynamics365/customer-insights/data/get-started"
+  ],
+  "security_notes": "Never approve production journey publish or bulk outreach without documented evidence of consent compliance review, audience segment validation, and journey logic sign-off. Production journey publish, consent-model changes, and segment-based bulk outreach are live-guard gated and must be escalated to the marketing operations lead and compliance owner before execution. Consent model changes — including compliance profile edits, purpose reconfiguration, and topic restructuring — must be reviewed for regulatory impact (GDPR, CAN-SPAM, CASL) before deployment. Do not accept segment membership count alone as evidence of segment quality; require rule review and profile source validation. Do not ask for credentials, tenant IDs, environment URLs, API keys, customer PII, or consent data exports. Treat every unvalidated consent migration, missing double opt-in configuration, and untested journey branch as a production risk requiring explicit human sign-off.",
+  "last_verified": "2026-06-17",
+  "path": "skills/microsoft/d365-customer-insights-journeys",
+  "author": "github: Raishin",
+  "version": "0.1.0",
+  "category": "data",
+  "companion_agents": ["d365-customer-insights-journeys-agent"]
+}

package/skills/microsoft/d365-customer-insights-journeys/references/official-sources.md

@@ -0,0 +1,46 @@
+# Official sources
+
+Use this reference only when you need source grounding for Dynamics 365 Customer Insights — Data or Customer Insights — Journeys behavior, data unification, segment design, consent compliance, or journey orchestration guidance.
+
+## Microsoft Learn documentation
+
+Use these as starting points, not as proof of the user's live environment configuration or consent posture:
+
+- https://learn.microsoft.com/dynamics365/customer-insights/data/data-unification
+- https://learn.microsoft.com/dynamics365/customer-insights/data/segments
+- https://learn.microsoft.com/dynamics365/customer-insights/data/measures
+- https://learn.microsoft.com/dynamics365/customer-insights/data/get-started
+- https://learn.microsoft.com/dynamics365/customer-insights/journeys/real-time-marketing-compliance-settings
+- https://learn.microsoft.com/dynamics365/customer-insights/journeys/real-time-marketing-email-text-consent
+- https://learn.microsoft.com/dynamics365/customer-insights/journeys/real-time-marketing-double-opt-in
+- https://learn.microsoft.com/dynamics365/customer-insights/journeys/ci-get-started
+- https://learn.microsoft.com/dynamics365/customer-insights/journeys/real-time-marketing-migrate-consent
+- https://learn.microsoft.com/dynamics365/customer-insights/journeys/unified-profile-segment-creation
+
+## Grounding rule
+
+Official documentation explains Dynamics 365 Customer Insights behavior, data unification mechanics, segment evaluation rules, and consent enforcement logic. It does not prove the user's actual unified profile completeness, segment membership accuracy, consent record state, or journey branch coverage. Prefer documented artifacts (unification run logs, segment inspection results, consent audit exports, journey test run evidence, compliance profile configuration screenshots) over inference.
+
+## Service facts (verified 2026-06-17)
+
+Customer Insights — Data (CDP) structure:
+- Customer Insights — Data is a customer data platform (CDP) that ingests data from multiple sources, runs identity resolution through deduplication and match rules, and produces unified customer profiles stored in Dataverse.
+- **Data sources**: ingested via Power Query connectors, Azure Data Lake Storage, Dataverse, or other supported connectors. Each source table must be mapped to semantic fields before unification.
+- **Unification phases**: source field mapping → deduplication → match rules → merge policies. All four phases must be configured and run before unified profiles are available.
+- **Segments**: evaluated against unified customer profiles. Segment rules can reference profile attributes, activities, measures, and enrichments. Segments must be refreshed (scheduled or on-demand) before they reflect current profile data.
+- **Measures**: calculated KPIs based on unified profile data. Measures can be used as segment criteria in Customer Insights — Journeys.
+
+Consent model (Customer Insights — Journeys):
+- Consent is captured and enforced at the **contact point level** (email address, phone number, or custom channel address), not at the contact/lead record level.
+- The consent hierarchy: compliance profile → purpose → topic. A compliance profile must be configured before journeys can enforce consent.
+- **Double opt-in**: must be explicitly enabled per compliance profile. Enabling the feature switch does not automatically apply double opt-in to all forms; additional configuration per compliance profile is required.
+- The `DoNotEmail`, `DoNotBulkEmail`, and `DoNotTrack` fields on the contact record are **not** evaluated by default in real-time journeys. To enforce them, the "Check contact consent in real-time journeys" feature switch must be enabled.
+- Consent migration from outbound marketing or external systems requires manual import or the Load Consent function; contact point consent records are not automatically created from legacy field values.
+
+Journey orchestration:
+- Real-time journeys support segment-based entry (scheduled) and trigger-based entry (event-driven).
+- Journey branches, wait conditions, and channel steps must be tested before production publish. A journey cannot be edited after it is set to Live status without creating a new version.
+- Production journey publish is irreversible without stopping the journey; stopping a live journey affects all in-progress participants.
+
+Certification anchor:
+- MB-260 (Customer Insights Data Specialist) was retired 2026-06-17 per latest available information; MB-220 (Marketing) was also retired. Verify current certification and Applied Skills offerings on Microsoft Learn before citing exam references. (E4: verify before citing.)

package/skills/microsoft/d365-customer-insights-journeys/references/safety-checklist.md

@@ -0,0 +1,41 @@
+# Safety checklist
+
+Use this reference before any recommendation involving production journey publish authorization, consent-model changes, bulk outreach approval, or compliance-impacting configuration changes in Dynamics 365 Customer Insights — Data or Customer Insights — Journeys.
+
+## Non-negotiables
+
+- Never ask users to paste credentials, API keys, tenant IDs, environment URLs, client secrets, customer PII, or consent data exports into chat.
+- Use documented artifacts or sanitized user-provided evidence for live-state claims; otherwise use documentation and label the evidence level.
+- Do not invent unified profile counts, segment membership sizes, consent record states, journey test results, or compliance profile configurations.
+- Require explicit human approval before recommending production journey publish, consent-model changes, or bulk outreach execution.
+- Use current official Microsoft Learn documentation for Dynamics 365 Customer Insights — Data and Customer Insights — Journeys behavior.
+- Keep recommendations least-change, reversible, and scoped to the workload in question.
+- Production journey publish, consent-model changes, and segment-based bulk outreach are live-guard gated. Always escalate to the marketing operations lead and named compliance owner before execution.
+
+## Stress checks
+
+- Have all data sources been ingested and mapped before unification runs were executed?
+- Has the unified profile configuration been validated with sample profile results showing correct identity resolution?
+- Do segment rules reference validated profile attributes with a refresh schedule aligned to journey entry cadence?
+- Has at least one compliance profile been configured with purpose and topic hierarchy before any journey is published?
+- Is double opt-in configured on all compliance profiles where required by applicable regulation (GDPR, CAN-SPAM, CASL)?
+- Has legacy consent data been fully migrated from outbound marketing or external systems before bulk outreach begins?
+- Have all journey branches — including suppression, exit, error, and no-match paths — been tested in a non-production environment?
+- Has the compliance owner signed off on the consent model and unsubscribe path?
+- Is there a post-launch monitoring plan for engagement metrics, consent opt-out rates, and journey error rates?
+
+## Evidence labels
+
+Use `live evidence`, `documented artifact`, `user-provided evidence`, `documentation-based`, or `inference`. Documentation alone never proves the user's actual unified profile state, segment membership accuracy, consent record coverage, or journey branch coverage.
+
+## Live-guard gate
+
+The following actions require explicit human confirmation and are out of scope for automated execution:
+
+- Publishing a journey to Live status in the production environment
+- Modifying compliance profiles, purposes, or topics in the production consent model
+- Executing segment-based bulk email, SMS, or push notification outreach in production
+- Migrating or bulk-loading consent records into the production consent center
+- Enabling or disabling double opt-in on a compliance profile in production
+- Authorizing suppression list changes that affect production outreach
+- Signing off on regulatory compliance posture on behalf of the compliance owner

package/skills/microsoft/d365-customer-insights-journeys/references/workflow-and-output.md

@@ -0,0 +1,74 @@
+# Workflow and output contract
+
+Use this reference only when performing the full Customer Insights — Data or Customer Insights — Journeys review, or formatting the final answer.
+
+## Review domains
+
+Check these areas before giving a verdict:
+
+- Data source ingestion: source connectivity, table selection, schema mapping, refresh schedule
+- Data unification: source field mapping completeness, deduplication rule quality, match rule coverage, merge policy correctness
+- Unified profile quality: profile completeness, identity resolution evidence, known duplicates or splits
+- Segment design: rule logic, profile source validation, membership count reasonableness, refresh cadence, downstream usage
+- Measures and KPIs: definition correctness, data currency, calculation logic, usage in segments or journeys
+- Consent model: compliance profile configuration, purpose and topic hierarchy, contact point consent coverage, double opt-in status, legacy consent migration completeness
+- Journey design: trigger or segment entry configuration, branch logic, channel steps, personalization token validity, suppression and frequency cap configuration
+- Compliance posture: GDPR, CAN-SPAM, CASL, or other applicable regulation alignment; unsubscribe link presence; preference center availability
+- Stakeholder sign-off: named compliance owner and marketing operations lead approvals, dated
+- Post-launch monitoring: engagement metrics baseline, consent opt-out rate tracking, journey error rate monitoring
+
+## Safe workflow
+
+1. **Frame scope**
+   - Customer Insights workloads in scope (Data, Journeys, or both):
+   - Data sources being unified:
+   - Journey types in scope (segment-based, trigger-based, or both):
+   - Regulatory jurisdictions in scope (GDPR, CAN-SPAM, CASL, other):
+   - Explicit non-goals:
+
+2. **Collect evidence**
+   - Prefer documented artifacts: unification run logs, segment inspection exports, consent audit reports, journey test run results, compliance profile configuration, stakeholder sign-off records.
+   - Otherwise inspect sanitized user-provided summaries or official Dynamics 365 Customer Insights documentation.
+   - Label each finding as `live evidence`, `documented artifact`, `user-provided evidence`, `documentation-based`, or `inference`.
+
+3. **Stress-test risk**
+   - Have all data sources been ingested and schema-mapped before unification runs?
+   - Has the deduplication and match configuration been validated with sample profile results?
+   - Do segment rules reference correct profile attributes and are refresh schedules aligned with journey entry cadence?
+   - Has the consent model been configured with at least one compliance profile, purpose, and topic before journey publish?
+   - Is double opt-in configured on the relevant compliance profiles if required by applicable regulation?
+   - Has legacy consent been migrated from outbound marketing or external systems?
+   - Have all journey branches been tested including suppression, exit, and error paths?
+   - Has the compliance owner signed off on the consent model and unsubscribe path before production journey publish?
+   - What evidence is missing that would change the verdict?
+
+4. **Recommend the smallest safe action**
+   - Prefer additional unification runs over proceeding to production journeys with incomplete profiles, staged consent migration over bulk outreach, and journey test runs over direct production publish.
+   - If the safest action is to stop and complete consent model configuration or validate segment membership, say that plainly.
+   - Production journey publish and bulk outreach require live-guard escalation. Do not recommend production publish without explicit human approval from the marketing operations lead and compliance owner.
+
+## Output contract
+
+Return this structure:
+
+```markdown
+# D365 Customer Insights Review: <scope>
+## Executive verdict
+- Status: READY / READY WITH CONDITIONS / NOT READY / 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
+- Artifacts or checks to review:
+- Expected result:
+## Residual risk
+- <risk or explicit none>
+```

package/skills/microsoft/d365-customer-service-contact-center/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: d365-customer-service-contact-center
+description: Review Dynamics 365 Customer Service and Contact Center operations across the case-to-resolution lifecycle — case management, unified routing, Omnichannel for Customer Service, queues, entitlements, service-level agreements (SLAs), knowledge management, and Copilot in Service. Use to improve case resolution time, routing accuracy, knowledge reuse, omnichannel consistency, and CSAT. Static review only; production routing-rule, SLA, and channel configuration changes are escalated.
+allowed-tools: Read Grep Glob
+metadata:
+  author: "github: Raishin"
+  version: "0.1.0"
+  updated: "2026-06-16"
+  category: operational
+---
+
+# D365 Customer Service & Contact Center
+
+## Purpose
+
+Act as the Dynamics 365 Customer Service reviewer who treats every misrouted case, breached SLA, stale knowledge base, and inconsistent channel experience as a CSAT and cost-to-serve risk until proven otherwise. Cover the case-to-resolution lifecycle from intake across channels through routing, resolution, and knowledge reuse.
+
+## When to use
+
+Use this skill for:
+
+- Case management: record creation/update rules, case resolution experience, status reasons, timeline
+- Unified routing: rules, skills-based routing, capacity profiles, work classification, queue assignment
+- Omnichannel for Customer Service: voice, chat, messaging channels, workstreams, agent experience
+- Queues, entitlements, and service scheduling
+- Service-level agreements (SLAs): KPIs, applicable-when conditions, success criteria, warning/failure actions, recalculation
+- Knowledge management: article authoring/curation/publishing, internal and external (SharePoint) search, AI suggestions
+- Copilot in Service: case/conversation summaries, ask-a-question, draft-a-response, knowledge integration
+- Customer Service KPIs: first-response/resolution time, SLA attainment, routing accuracy, deflection, CSAT
+
+Do not use this skill for:
+
+- Field Service work orders and scheduling (use d365-field-service-to-cash)
+- Sales pipeline/forecasting (use d365-sales-revenue-operations)
+- Customer Insights segmentation/journeys (separate skill)
+
+## Lean operating rules
+
+- Prefer current Microsoft Learn documentation for Customer Service, Omnichannel, unified routing, and SLA behavior. Administration is configured in the Copilot Service admin center (formerly Customer Service admin center); verify current naming.
+- Separate confirmed facts from inference. If SLA attainment or routing metrics were not provided, say so.
+- Challenge cases routed manually at scale, SLAs without warning actions, knowledge bases without curation/expiry, and channels configured without capacity profiles.
+- 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 data.
+
+## References
+
+Load these only when needed:
+
+- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full Customer Service review or formatting the final answer.
+- [Safety checklist](references/safety-checklist.md) — use before any recommendation involving production routing rules, SLA configuration, or channel changes.
+- [Official sources](references/official-sources.md) — use when grounding Customer Service, Omnichannel, unified routing, or SLA behavior.
+
+## Response minimum
+
+Return, at minimum:
+
+- the scoped target and evidence level,
+- the main case-management, routing, SLA, knowledge, or omnichannel gaps,
+- the safest next actions,
+- validation or rollback notes where relevant,
+- the assumptions or blockers that prevent stronger conclusions.