Translate internal project status into client-facing communications with orchestrator approval.
npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-cco
Please help me install this Agent Skill. Skill: aidlc-cco Source: https://github.com/CornFedKratos/s3-aidlc/tree/main/plugins/s3-aidlc/skills/aidlc-cco Command: npx skills add https://github.com/CornFedKratos/s3-aidlc --skill aidlc-cco
External client communications often lag behind internal progress, risking misalignment and eroded trust. The CCO provides a client-first narrative layer that translates technical updates into clear, credible client-facing messages.
Draft your first client-facing update by translating the current phase status into client language and submitting it for orchestrator approval.
High-intent search queries and answers about installing and using this skill.
Drafting client-facing communications requires translating current phase status into client language and submitting it for orchestrator approval. This enforces client-first language while preserving internal context for governance and knowledge base logging.
Managing hard conversations and risk briefings involves using specialized templates and playbooks for risky updates. This ensures communications remain credible and client-first during phase gates, stakeholder demos, and risk materializations.
Orchestrator approval for external stakeholder updates is required for every external message across all engagement phases. This protocol ensures all client-facing communications are logged in the knowledge base to maintain governance and alignment.
This approach applies during routine status updates, phase gates, demos, and risk briefings across all engagement phases. It enforces client-first language and orchestrator approval to ensure external communications remain clear and credible.
External client communication often lags behind internal progress because technical details require translation into client-first language. Without enforcing orchestrator approval and knowledge base logging, external messaging risks misalignment and eroded trust.
Without a knowledge base, managing client communications lacks the mandated logging required for every external message. This limitation prevents internal context preservation and breaks orchestrator approval protocols, risking governance and stakeholder trust.
yachelaGenerate template-based client letters for student clinic correspondence.
CornFedKratosOrchestrate AI project delivery from idea to shipped product with phase gates.
brainbrewlabsCoordinate progress tracking and reporting for multi-agent projects.
notqueExtract propositions from technical updates into executive-ready summaries with status indicators.
