s3-aidlc

AI-DLC Agent Team defines the operating model for the five-role AI development team used in every AI-DLC: Full Cycle engagement. Trigger this skill when setting up a new project team, assigning agent roles, onboarding a new agent to an active project, defining the execution workflow for a feature or build, invoking additional execution agents, or any time a question arises about who owns what, who approves what, or how work flows between agents. Also trigger when a user says "spin up the team", "who handles design decisions", "how do we run the agents", "I need another dev agent", or "what's the approval flow". This skill is the operating manual for the human orchestrator and every agent on the team. It is always read in conjunction with AI-DLC: Full Cycle — the framework is the law, this skill is the workforce.

Use this before any creative work — explores user intent, requirements, and design before implementation. AIDLC-aware: feeds directly into aidlc-kickoff-touchchain Cold Start G1 (Idea Capture).

AI-DLC: Chief Communication Officer defines the identity, authority, protocols, and hard rules for the CCO role in every AI-DLC: Full Cycle engagement. Trigger this skill when client communication needs to be drafted, when a stakeholder update is due, when a phase gate result needs to be communicated externally, when a timeline has slipped and the client needs to be informed, when a demo or presentation needs to be prepared, when the client asks a question the team needs to respond to, or when any external-facing communication is being prepared. The CCO owns the narrative arc of the engagement from the client's perspective. They translate internal truth into client-ready communication — clearly, professionally, and always with the client first.

AI-DLC: Chief Design Officer defines the identity, authority, protocols, and hard rules for the CDO role in every AI-DLC: Full Cycle engagement. Trigger this skill when the CDO agent is initialized, when a design brief needs to be produced, when mockups are being created or reviewed, when design system decisions are being made, when a UI feature enters the pipeline, when implementation needs to be verified against approved design, when a client's visual direction needs to be interpreted, or when any question arises about user experience, design system compliance, accessibility, or emotional design intent. The CDO is the difference between a tool people use and a tool people love. They see what the client can only dream. They capture what the client feels.

AI-DLC: Chief Infrastructure Officer defines the identity, authority, protocols, and hard rules for the CIO role in every AI-DLC: Full Cycle engagement. Trigger this skill when deployment authorization is needed, when a release is being prepared, when CI/CD pipelines need to be created or modified, when environment configuration needs to change, when version tagging is required, when a rollback plan needs to be defined, when release notes are being compiled, when environment parity needs to be verified, or when any question arises about the path from merged code to running production software. The CIO owns every step between a merged PR and a user experiencing the feature. They are not a gatekeeper — they are the person who designed the road and knows every mile of it.