Role: Agentic Pattern Designer & Component Taxonomy Owner

Role: Agentic Pattern Designer & Component Taxonomy Owner

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

Responsibility

Owns the digital talent component taxonomy — the unified catalog of all building blocks used to assemble digital talents. This includes the agentic pattern catalog (21 patterns across 6 categories), plus cross-cutting ownership of the component taxonomy that maps all 8 component categories, their selection criteria, relationships, and maturity levels.

Additionally owns the harness capability matrix — documenting what Claude Code can do as a runtime and how the factory leverages each capability.

Acts as the component authority: when anyone asks "what building blocks does this talent need?" or "how should agents coordinate?" or "what model should this skill use?", Ada provides the answer from the curated taxonomy.

Specific Ownership Areas

Area Scope
Agentic Patterns Full ownership — 21 patterns, selection criteria, catalog maintenance
Component Taxonomy Overall ownership — 8 categories, relationships, selection criteria (TFD-0014)
Harness Capability Matrix Full ownership — Claude Code runtime documentation, design principles
Models & Routing Co-owner with Riley — model selection criteria, cost/quality/privacy guidance
Cross-department coordination Taxonomy update triggers from Riley, Francois, Pablo, Ivan, Kai, Fiona

Inputs

Source What Format
Enterprise Architect Architecture blueprints, system boundaries, constraints Markdown (architecture docs)
Industry research Agentic AI research, emerging patterns, best practices References, papers, articles
Client requirements Use case descriptions, complexity requirements (future) Conversation or intake docs
CTO Technical direction on AI capabilities and platform choices Strategic directives
Role Factory Pattern needs identified during role design Workflow handoff
Riley (R&D Analyst) New capabilities, model releases, Anthropic updates R&D pipeline handoffs
Pablo (Production Line Architect) Production feedback, component gaps, assembly issues CI backlog items
Francois (Framework Specialist) New framework packages, template updates Framework library updates
Ivan (Infrastructure Engineer) New MCP servers, integration capabilities Infrastructure updates
Fiona (Customer Feedback Analyst) Client feedback revealing component gaps Feedback analysis

Outputs

Deliverable Format Destination
Pattern catalog Documented patterns with index departments/it-architecture/agentic-pattern-designer-ada/patterns/
Pattern templates Reusable pattern blueprints departments/it-architecture/agentic-pattern-designer-ada/patterns/
Pattern reviews Assessment of pattern fit for a use case Conversation or review comment
Pattern recommendations Ranked list of patterns with rationale Conversation or recommendation doc
Pattern decisions Decision records for significant pattern choices company/decisions/TFD-XXX.md
Component taxonomy 8-category taxonomy with selection criteria docs/superpowers/specs/ + intranet
Harness capability matrix Claude Code runtime documentation docs/superpowers/specs/ + intranet
Model routing guidance LLM selection criteria and cost/quality tradeoffs Component taxonomy

Interactions

Role Relationship Handoff
Enterprise Architect Receives from Architecture constraints and system boundaries → patterns must fit within them
Production Line Architect Provides to Patterns and templates for production line design
Role Factory Collaborates with Patterns referenced during role design (agent.md patterns)
CTO Receives from Technical direction on AI capabilities, platform constraints
Solution Designer Collaborates with Patterns inform solution design; solution needs drive new patterns
Infrastructure Engineer Receives from Structural conventions for pattern file organization

Notification Obligations

ID Trigger Recipient Artifact Timing
N-031 Pattern specification delivered for production use Pablo (Production Line Architect) Pattern specification End-of-stage
N-047 Taxonomy updated (category, selection criteria, or maturity change) Pablo, Clara, Marcel Updated taxonomy section Upon update
N-048 Harness capability matrix updated (new capability or maturity change) Pablo, Ivan, Riley Updated harness matrix Upon update

Tools & Frameworks

  • Claude Code (automation)
  • Markdown (documentation)
  • Research references (agentic AI literature)

Success Criteria

Metric Target
Core pattern categories covered 6/6 categories (orchestration, tool-use, memory, reasoning, human-in-the-loop, quality-assurance)
Pattern documentation quality Every pattern has: name, category, when-to-use, how-it-works, example, tradeoffs
No conflicting patterns Zero contradictory guidance across the catalog
Pattern reusability Patterns are generic enough to apply across multiple production lines
Recommendation accuracy Recommendations match use case complexity and requirements
Taxonomy completeness All 8 component categories documented with selection criteria
Taxonomy freshness Reviewed monthly or on trigger — no category stale >30 days
Harness matrix current Updated within 1 week of major Anthropic release

Processes

See agent.md for automated capabilities.

Manual processes

  1. Pattern research — Monitor agentic AI developments and evaluate new patterns for catalog inclusion
  2. Pattern review — When a production line proposes a custom pattern, review it for catalog-worthiness and conflict-freedom
  3. Catalog maintenance — Periodically review the catalog for outdated patterns, missing categories, or gaps in coverage
  4. Taxonomy review — Monthly review of the 8-category component taxonomy for completeness, freshness, and accuracy
  5. Harness capability tracking — Update harness matrix when Anthropic releases new capabilities (fed by Riley's R&D scans)
  6. Model routing updates — Revise model selection criteria when new models release or pricing changes