What
Proposing a dedicated DevOps Lead persona ("Riley") to fill the infrastructure and deployment gap in BMAD's agent roster. This persona would own infrastructure-as-code, CI/CD pipeline design, deployment strategies, environment management, and pipeline security — areas currently handled only superficially by the Architect's Category 5 decisions.
A companion SRE persona (observability, incident response, reliability engineering) is planned as a separate follow-up proposal.
Why
Prior Art — This Was Started Before
Community Signal
Current Gap
The architecture workflow's step-04-decisions.md Category 5 (Infrastructure & Deployment) covers hosting, CI/CD, environment config, monitoring, and scaling — but only as 5 bullet points within a broader architecture decision step. There is no:
- Guided IaC strategy workflow
- CI/CD pipeline design workflow
- Deployment strategy patterns (blue-green, canary, rolling)
- Multi-environment management guidance
- Secrets management patterns
- Container best practices
- Pipeline security (SBOM, provenance, image signing)
How
PR 1: DevOps Lead Agent Persona (this proposal)
src/bmm-skills/3-solutioning/bmad-agent-devops/SKILL.md- Registration in
module-help.csv
- Core principles: IaC-first, idempotent deployments, environment parity, shift-left security, automate toil, pipelines-as-products
PR 2: Infrastructure-as-Code Workflow (follow-up)
bmad-create-infrastructure skill — guided IaC tool selection, environment topology, state management, drift detection- Infrastructure specification template
PR 3: CI/CD Pipeline Design Workflow (follow-up)
bmad-create-pipeline skill — pipeline stage design, deployment strategies, promotion gates, rollback procedures- Pipeline specification template
PR 4: Architecture Integration (follow-up)
- Expand
step-04-decisions.md Category 5 to reference DevOps Lead
- Add infrastructure validation to implementation readiness checks
- Add infra/deploy story types to epics workflow
Testing
- Verified SKILL.md format matches existing v6 agent patterns (architect, qa, dev)
npm run validate:refs should pass (no broken file references in initial persona)
Related
What
Proposing a dedicated DevOps Lead persona ("Riley") to fill the infrastructure and deployment gap in BMAD's agent roster. This persona would own infrastructure-as-code, CI/CD pipeline design, deployment strategies, environment management, and pipeline security — areas currently handled only superficially by the Architect's Category 5 decisions.
A companion SRE persona (observability, incident response, reliability engineering) is planned as a separate follow-up proposal.
Why
Prior Art — This Was Started Before
Community Signal
Current Gap
The architecture workflow's
step-04-decisions.mdCategory 5 (Infrastructure & Deployment) covers hosting, CI/CD, environment config, monitoring, and scaling — but only as 5 bullet points within a broader architecture decision step. There is no:How
PR 1: DevOps Lead Agent Persona (this proposal)
src/bmm-skills/3-solutioning/bmad-agent-devops/SKILL.mdmodule-help.csvPR 2: Infrastructure-as-Code Workflow (follow-up)
bmad-create-infrastructureskill — guided IaC tool selection, environment topology, state management, drift detectionPR 3: CI/CD Pipeline Design Workflow (follow-up)
bmad-create-pipelineskill — pipeline stage design, deployment strategies, promotion gates, rollback proceduresPR 4: Architecture Integration (follow-up)
step-04-decisions.mdCategory 5 to reference DevOps LeadTesting
npm run validate:refsshould pass (no broken file references in initial persona)Related