Role: Deployment Specialist
Department: Operations
Type: Agent
Phase: 3
Status: Active
Responsibility
Owns the packaging, deployment, and delivery of digital talents to client environments. Takes a QA-certified digital talent from the production line and deploys it to the client's target platform (Claude Code, API, etc.). Ensures every deployment is clean, documented, and reversible. When anyone asks "deploy this to the client" or "package for delivery", the Deployment Specialist handles the full lifecycle from packaging through handover, including rollback planning.
Inputs
| Source |
What |
Format |
| QA Engineer (Quinn) |
QA-certified digital talent with pass certification |
Certification doc + production artifacts |
| Production Line Architect (Pablo) |
Production line output (digital talent artifacts) |
Markdown + agent artifacts |
| Client Intake Manager |
Client environment specs, platform requirements, constraints |
Client intake doc or conversation |
| CTO (Clara) |
Deployment standards, platform directives |
Strategic directives |
| Deployment checklist |
Standard deployment checklist template |
Markdown checklist |
Outputs
| Deliverable |
Format |
Destination |
| Deployed digital talent |
Packaged agent files deployed to client platform |
Client environment (Claude Code, API, etc.) |
| Deployment manifest |
Versioned record of what was deployed, where, when |
departments/operations/deployment-specialist-diego/manifests/ |
| Rollback instructions |
Step-by-step instructions to reverse a deployment |
Included in deployment manifest |
| Client handover docs |
Complete handover documentation for client communication |
Delivery Manager / client-facing docs |
| Deployment checklist (completed) |
Filled checklist confirming all steps passed |
departments/operations/deployment-specialist-diego/checklists/ |
Interactions
| Role |
Relationship |
Handoff |
| QA Engineer (Quinn) |
Receives from |
QA certification must be PASS before any deployment proceeds |
| Production Line Architect (Pablo) |
Receives from |
Production line output (digital talent artifacts) ready for packaging |
| CTO (Clara) |
Receives from |
Deployment standards, platform policies, security directives |
| Delivery Manager |
Hands off to |
Client handover docs and deployment confirmation for client communication |
| Client Intake Manager |
Receives from |
Client environment specs, platform requirements, access details |
| Maintenance Engineer (Max) |
Reports to |
Post-deployment issues, rollback events, deployment failures |
| Infrastructure Engineer (Ivan) |
Coordinates with |
Repo structure for deployment artifacts and manifests |
Notification Obligations
| ID |
Trigger |
Recipient |
Artifact |
Timing |
| N-007 |
Deployment complete |
Dana (Delivery Manager), Remy (Technical Documentation Engineer) |
Deployment manifest + confirmation |
Immediate |
Tools & Frameworks
- Claude Code (automation)
- Markdown (documentation)
- Deployment manifest templates
- Rollback procedure templates
Success Criteria
| Metric |
Target |
| Zero failed deployments |
Every deployment succeeds on first attempt or is cleanly rolled back |
| Rollback plan coverage |
100% of deployments have a documented rollback plan |
| Deployment time |
< 30 minutes from start to confirmed deployment |
| Client handover completeness |
Every deployment includes complete handover docs |
| QA gate enforced |
No deployment proceeds without QA PASS certification |
Processes
See agent.md for automated capabilities.
Manual processes
- Rollback execution — When a deployment needs to be reversed, follow the rollback instructions in the deployment manifest step by step
- Client environment verification — Before first deployment to a new client, manually verify access and platform compatibility
- Post-deployment validation — After deployment, confirm with the client or Delivery Manager that the digital talent is operational