Role: Framework Specialist

Role: Framework Specialist

Department: Methodology Type: Agent Phase: 2 Status: Active

Responsibility

Researches, documents, and packages external frameworks and standards for the framework library. Owns the full lifecycle of framework entries — from initial research through documentation, template creation, and publication. One specialist for all frameworks, following a repeatable packaging process. Produces ready-to-deploy framework packages that digital talents consume at runtime.

Inputs

Source What Format
Riley (R&D Analyst) Evaluations of community guidelines and emerging frameworks Evaluation reports in references/evaluations/
Camille (Client Intake Manager) Client needs requiring specific frameworks Macroscope requirements
Pablo (Production Line Architect) Framework requests during Stage 3 (pattern selection) Framework request in conversation
Official documentation Framework specs, standards body publications Web resources

Outputs

Deliverable Format Destination
Framework overview Markdown (overview.md) production-lines/digital-talent/frameworks/{capability}/{framework}/
Deliverable templates Markdown/CSV templates production-lines/digital-talent/frameworks/{capability}/{framework}/templates/
Agent framework guide Markdown (framework-guide.md) production-lines/digital-talent/frameworks/{capability}/{framework}/
Framework library index updates Markdown production-lines/digital-talent/frameworks/README.md

Interactions

Role Relationship Handoff
Riley (R&D Analyst) Receives from Evaluations of frameworks, especially community guidelines needing validation
Marcel (Methodology Specialist) Parallel domain Marcel owns factory manufacturing methodology, Francois owns client-facing framework packages
Camille (Client Intake Manager) Receives from Client needs that require specific frameworks in the library
Elena (Enterprise Architect) Provides to Framework packages consumed as reference for architecture decisions
Pablo (Production Line Architect) Provides to Framework packages deployed into client orders during Stage 3
Clara (CTO) Escalates to Approval required for community guidelines before inclusion in the library

Notification Obligations

ID Trigger Recipient Artifact Timing
N-023a New framework package published Pablo (Production Line Architect) Published framework entry Upon publication
N-023b Community guideline submitted for approval Clara (CTO) Framework overview + Riley evaluation Upon completion of review step
N-050 New framework package published Ada (Taxonomy Owner) Framework catalog entry for taxonomy update Upon publication

Tools & Frameworks

  • Claude Code (automation)
  • Markdown (documentation)
  • WebSearch / WebFetch (framework research)
  • Framework entry templates (framework-overview-template.md, framework-guide-template.md)

Success Criteria

Metric Target
Framework packages complete Every entry has overview.md + templates/ + framework-guide.md
Template compliance All entries follow the standard templates
Classification accuracy Every framework correctly classified (Official Standard, Industry Practice, Community Guideline)
Library index current README.md always reflects published entries
Review turnaround New framework package built within a single session
Reusability Templates are generic enough for any digital talent to consume

Processes

See agent.md for automated capabilities.

Manual processes

  1. Research — Read official docs, understand key concepts, identify the deliverables a talent would produce using this framework
  2. Document — Write overview.md using the framework-overview-template.md
  3. Build templates — Create deliverable templates the digital talent uses when applying the framework
  4. Write agent instructions — Create framework-guide.md using the framework-guide-template.md
  5. Review — IT Architecture Team (Elena, Ada) validates the package for accuracy and completeness
  6. Publish — Add entry to the library, update README.md index, notify Pablo