client-engagement

name	client-engagement
description	Domain knowledge for the {{client_name}} client engagement — stakeholders, technology stack, and editorial standards. USE FOR: client deliverables, agent specs, architecture docs, status reports, any client-specific content. DO NOT USE FOR: generic documents not related to the client.

{{client_name}} Engagement Skill

Domain knowledge for the {{client_name}} client engagement. Provides context about the client, technology stack, engagement scope, and editorial standards for generating client-specific deliverables.

Client Profile

• Client: {{client_name}} ({{client_official_name}})
• Sector: {{client_sector}}
• Headquarters: {{client_hq}}
• Canonical source: context/CLIENT.md

Engagement

• Project: {{engagement_project_name}}
• Objective: {{engagement_objective}}
• Timeline: {{engagement_timeline}}
• Delivery partner: {{delivery_partner}}

Technology Stack

Layer	Technology
Cloud	{{tech_cloud}}
CI/CD	{{tech_cicd}}
Repository	{{tech_repo}}
Models	{{tech_models}}

Key Stakeholders

Person	Role	Key Directive
{{stakeholder_1_name}}	{{stakeholder_1_role}}	{{stakeholder_1_directive}}

Editorial Rules

• Language: English
• Filename: NN_Title_vX.Y.Z_YYYY-MM-DD.md (sequential numbering)
• Structure: YAML frontmatter, Change Log, Table of Contents, References
• Canonical client source: context/CLIENT.md
• References path: sources/ (lowercase)
• Markdown-first: every document must have a Markdown version in output/md/
• Versioning: semantic versioning (major.minor.patch)
• Archiving: move previous version to archive/ before overwriting

Diagram Color Rules

SVG (preferred for Markdown documents)

• Border / stroke: Microsoft palette (#0078D4 blue, #F25022 red, #7FBA00 green, #FFB900 yellow)
• Fill: Always white (#FFFFFF)
• Text: Always black (#323130)
• Connectors: 1.5px, #605E5C (secondary gray)

Mermaid (only for FigJam via MCP connector)

• Primary nodes: fill:#0078D4,color:#fff (Microsoft blue)
• Result/success: fill:#E8F5E9,stroke:#107C10
• System/integration: fill:#EFF6FC,stroke:#0078D4
• Warning/caution: fill:#FFF3E0,stroke:#FFB900
• Error/alert: fill:#FDEDED,stroke:#E81123
• Human review: fill:#F3F2F1,stroke:#323130

Factual Integrity (Reinforced)

• NEVER fabricate, assume, presume, or invent metrics, KPIs, ROI, market data, or statistics.
• Every data claim MUST include a hyperlink to a credible source.
• Approved sources: Gartner, DORA, Microsoft Learn, GitHub, Anthropic, IDC, McKinsey, IBM.
• If no source exists, state as assumption or omit.
• Every document ends with a References section with full URLs.

Quality Checklist

Before delivering any {{client_name}} document, verify:

• Language is English
• Filename follows naming convention (NN_Title_vX.Y.Z_YYYY-MM-DD.md)
• Frontmatter includes: title, description, author, date, version, status, tags, client: "{{client_name}}"
• Markdown version exists in output/md/
• No fabricated data — every metric/KPI/statistic has a hyperlink to its source
• No TODO, TBD, or placeholder text
• Diagrams use SVG (white fill, black text, Microsoft colors on borders)
• Every diagram has a descriptive paragraph above it
• References to context use context/CLIENT.md as canonical source
• Previous version archived before overwriting
• References section present at the end with full URLs
• Editorial UX: bold key terms, callout blocks, tables, icons where appropriate