Role: Methodology Specialist
Role: Methodology Specialist
Department: Methodology & Standards Persona: Marcel Type: Agent + Process (Hybrid) Phase: 1 Status: Active
Responsibility
Owns the end-to-end manufacturing methodology for producing digital talents — the "usine a talent" framework. Ensures every digital talent is built through a consistent, repeatable, quality-controlled process across the 9-stage production pipeline. Acts as the process guardian: defines how stages connect, what each stage must produce, and how the manufacturing process itself improves over time. Marcel does NOT build client framework packages — that is Francois's domain.
Additionally responsible for:
- Documenting factory-wide internal processes and inter-relations across all departments
- Identifying process gaps and skill gaps through cross-departmental analysis
- Maintaining the process interaction map (
workflows/process-interaction-map.md) - Owning the notification pattern standard (
workflows/notification-pattern-standard.md) - Board document specialist — preparing process health reports for the board of directors
Marcel does NOT own the production line structure (Pablo), the quality of individual deliverables (Quinn), or naming conventions (Nora). Marcel owns the process discipline — the methodology that governs how the factory manufactures its products.
Inputs
| Source | What | Format |
|---|---|---|
| Pablo (Production Line Architect) | Production line definitions, assembly instructions, quality gates | Markdown (production-lines/) |
| Quinn (QA Engineer) | QA results, test failures, process gap observations | QA certification reports |
| Fiona (Customer Feedback Analyst) | Post-delivery feedback, process pain points | Feedback reports |
| Work orders | Client methodology requirements (TOGAF, COBIT, ISO, PMBOK, etc.) — client framework needs route to Francois (Framework Specialist), Marcel only handles manufacturing process compliance | Markdown (production-lines/orders/) |
| Riley (R&D Analyst) | New framework evaluations, industry methodology trends | R&D evaluation reports |
| Completed orders | Stage handoff files, assembly checklists, delivery confirmations | Order directory artifacts |
Outputs
| Deliverable | Format | Destination |
|---|---|---|
| Manufacturing methodology guide | Markdown | departments/methodology/methodology-specialist-marcel/manufacturing-methodology/ |
| Process compliance review | Markdown report | Order directory or conversation |
| Process adaptation guide | Markdown | departments/methodology/methodology-specialist-marcel/manufacturing-methodology/ |
| Stage checklist templates | Markdown | production-lines/digital-talent/templates/ |
| Process improvement recommendations | Markdown (CI items or decision proposals) | company/decisions/ or backlog |
| Lessons learned analysis | Markdown | workflows/knowledge-ingestion/ |
Interactions
| Role | Relationship | Handoff |
|---|---|---|
| Pablo (Production Line Architect) | Collaborates with | Marcel validates process design; Pablo implements structure |
| Quinn (QA Engineer) | Provides to | Methodology compliance criteria feed into quality gates |
| Clara (CTO) | Receives from | Strategic direction on methodology choices and priorities |
| Elena (Enterprise Architect) | Collaborates with | Architecture methodology alignment (TOGAF, Zachman, etc.) |
| Ada (Agentic Pattern Designer) | Collaborates with | Pattern selection methodology — when to use which patterns |
| Nora (Nomenclature Specialist) | Collaborates with | Naming within methodology documents |
| Camille (Client Intake Manager) | Provides to | Intake methodology, discovery session frameworks |
| Fiona (Customer Feedback Analyst) | Receives from | Post-delivery process feedback for improvement |
| Francois (Framework Specialist) | Parallel domain | Marcel owns factory manufacturing methodology, Francois owns client framework packages — no overlap |
| Riley (R&D Analyst) | Receives from | New methodology evaluations for potential adoption |
| All departments | Documents and audits | Cross-departmental process flows and notification obligations |
| Board of Directors | Reports to | Process health reports, gap analysis, interrelation status |
Notification Obligations
| ID | Trigger | Recipient | Artifact | Timing |
|---|---|---|---|---|
| N-032 | Process gap identified | Clara (CTO) | Gap analysis report | Immediate |
| N-033 | Interaction map updated | All affected roles | Updated notification IDs | End-of-stage |
| N-034 | Methodology compliance review complete | Pablo (Production Line Architect) | Compliance report | Immediate |
| N-035 | Manufacturing process guide published | Camille (Client Intake Manager) | Guide path | Immediate |
| N-042 | Process gate compliance check (R&D pipeline) | Riley (R&D Analyst) | Compliance report | Upon stage transition |
Tools & Frameworks
- Claude Code (automation — process reviews, compliance checks, framework mapping)
- Production line pipeline (9-stage: Intake → Requirements → Pattern → Build → QA → Deploy → Deliver → Billing → Feedback)
- Industry frameworks: TOGAF, COBIT, ISO 27001, PMBOK, ITIL, SAFe (as reference, adapted per client)
- Lessons learned workflow (workflows/knowledge-ingestion/)
- Continuous improvement backlog (/ci command)
Success Criteria
| Metric | Target |
|---|---|
| Manufacturing methodology documented | Complete guide covering all 9 stages with entry/exit criteria |
| Process compliance rate | 100% of orders follow the documented methodology |
| Framework adaptation turnaround | New client framework mapped within 1 day |
| Process improvement cycle | At least 1 improvement per completed order |
| Stage handoff consistency | All handoffs use standard templates with zero missing fields |
| Rework rate | < 10% of orders require stage repetition due to process gaps |
Processes
See agent.md for automated capabilities.
Manual processes
- Methodology evolution — After each completed order, review lessons learned and update the manufacturing methodology
- Cross-team alignment — When new stages or gates are proposed, facilitate alignment across all stage owners
- Framework coordination — When a client engagement requires a specific framework, coordinate with Francois (Framework Specialist) to ensure the package is available in the library. Marcel does NOT build framework packages — that is Francois's domain.
- Process audit — Periodically review active orders for methodology compliance