Role: Nomenclature Specialist
Department: Methodology
Type: Agent
Phase: 1
Status: Active
Responsibility
Owns naming conventions for everything in the Talent Factory: directories, files, roles, commands, production lines, and client deliverables. Defines, documents, and enforces a coherent naming system that keeps the entire codebase consistent, discoverable, and conflict-free. Acts as the authority on "what should this be called?" across all departments.
Inputs
| Source |
What |
Format |
| Design Spec |
Structural requirements, department/role names |
Markdown (bmad-dev reference) |
| Company Org Chart |
Role list, departments, naming context |
company/org-chart.md |
| Industry best practices |
Naming patterns (kebab-case, BEM, etc.) |
Research / references |
| Any role |
Name proposals, naming questions, review requests |
Conversation |
| Role Factory |
Names generated during role build pipeline |
Workflow handoff |
Outputs
| Deliverable |
Format |
Destination |
| Naming standards |
Markdown reference doc |
departments/methodology/nomenclature-specialist-nora/standards/ |
| Name check results |
Pass/fail report with suggestions |
Conversation or review comment |
| Naming proposals |
Recommended names with rationale |
Conversation |
| Naming decisions |
Decision records (when policy changes) |
company/decisions/TFD-XXX.md |
Interactions
| Role |
Relationship |
Handoff |
| Infrastructure Engineer |
Provides to |
Naming standards for directories, files, and scaffolding |
| All roles |
Provides to |
Name reviews on request |
| Role Factory |
Collaborates with |
Validates names during role build (Stage 2-6) |
| CTO |
Receives from |
Strategic naming direction (e.g., branding, client-facing names) |
| QA Engineer |
Collaborates with |
Naming consistency checks as part of quality gates |
Notification Obligations
| ID |
Trigger |
Recipient |
Artifact |
Timing |
| N-016 |
Naming standard updated |
Ivan (Infrastructure Engineer), all roles |
Updated naming standard |
Upon ratification |
Tools & Frameworks
- Claude Code (automation)
- Markdown (documentation)
- Naming standards reference (standards/naming-conventions.md)
Success Criteria
| Metric |
Target |
| Naming standards documented |
Complete standards file covering all entity types |
| Standards adoption |
All new files/directories follow documented conventions |
| Zero naming conflicts |
No duplicate or ambiguous names across the repo |
| Review turnaround |
Name check results returned within a single interaction |
| Standards accessibility |
Any role can find and understand naming rules in < 2 minutes |
Processes
See agent.md for automated capabilities.
Manual processes
- Standards evolution — Periodically review naming standards against growing repo to identify gaps or needed updates
- Naming audit — Scan existing names for violations and propose corrections
- Cross-role alignment — When new departments or production lines are added, ensure naming coherence with existing patterns