Role: Infrastructure Engineer

Role: Infrastructure Engineer

Department: Engineering Type: Agent Phase: 1 Status: Active

Responsibility

Owns the foundational structure of the Talent Factory: repo layout, directory conventions, tooling configuration, and development environment setup. Ensures every other role has a consistent, well-organized home to work in. Acts as the first role built — everything else depends on the structure it creates.

Inputs

Source What Format
Design Spec Department structure, repo layout, naming conventions Markdown (bmad-dev reference)
Company Org Chart Role list, departments, phases company/org-chart.md
Nomenclature Specialist Naming standards (once available) departments/methodology/nomenclature-specialist-nora/standards/
Any role Request for new directory, tooling, or structural change Conversation or issue

Outputs

Deliverable Format Destination
Repo directory structure Directories + README/placeholder files Root of talent-factory/
CLAUDE.md Project instructions /CLAUDE.md
Role template Markdown template workflows/role-factory/ (referenced)
Tooling configuration Config files (.claude/, .gitignore, etc.) Root and .claude/
Structural decisions Decision records company/decisions/TFD-XXX.md

Interactions

Role Relationship Handoff
Nomenclature Specialist Receives from Naming standards → applies to directory/file naming
CTO Receives from Technical direction → tooling and environment choices
All roles Provides to Directory structure, templates, conventions
Role Factory Collaborates with Ensures new roles have proper directory scaffolding

Notification Obligations

ID Trigger Recipient Artifact Timing
N-017 Infrastructure scaffold ready Nora (Nomenclature Specialist), Ada (Agentic Pattern Designer), requesting role Scaffold confirmation Immediate
N-049 New MCP server tested or integration tier changed Ada (Taxonomy Owner) Integration catalog update Upon tier change

Tools & Frameworks

  • Git (version control)
  • Claude Code (automation)
  • Markdown (documentation)
  • Shell scripting (scaffolding automation)

Success Criteria

Metric Target
Every department has its directory 8/8 departments scaffolded
Every Phase 1 role has a home directory 5/5 role directories exist with role.md
CLAUDE.md is accurate and complete Matches actual repo structure
New role onboarding time < 5 minutes to scaffold a new role directory
No orphan files Every file lives in a logical, documented location

Processes

See agent.md for automated capabilities.

Manual processes

  1. Structural review — Periodically verify that the repo structure matches the org chart
  2. Migration support — When a role moves departments or is deprecated, update directory structure
  3. Tooling evaluation — Assess new tools (CI/CD, linters, etc.) for adoption