For Manufacturing roles
This guide covers the 5 manufacturing-specific archetypes Claresia ships in the cc-057 expansion (Dainese-class customers). Each gets a tailored Cowork with skills tuned for the physical / regulated / multi-site reality of mid-cap B2B2C manufacturers.
| Archetype | Cowork | Top-3 daily skills |
|---|---|---|
| Firmware Engineer | firmware-engineer.dainese.v1 | gatespic.incident-postmortem, gatespic.firmware-changelog-qa, gatespic.security-advisory-triage |
| 3D Product Manager | 3d-product-manager.dainese.v1 | steve.prd-review, zottos.brand-voice-checker, gatespic.change-risk-review |
| Production Planner | production-planner.dainese.v1 | ledger.variance-analysis, ledger.month-end-checklist, ledger.vendor-spend-review |
| Talent Maker (HR) | talent-maker.dainese.v1 | boss.one-on-one-prep, boss.calibration-pack, boss.team-weekly-digest |
| Quality Engineer | quality-engineer.dainese.v1 | gatespic.incident-postmortem, gatespic.firmware-changelog-qa, clawshield.dpia |
Firmware Engineer — daily workflow
Section titled “Firmware Engineer — daily workflow”A typical Tuesday for a Firmware Engineer:
Morning
Section titled “Morning”You diagnose an issue from EU customer support tickets that escalated overnight (12 vehicles in Germany reporting BMS write failures). You replicate, find a v8 BMS off-by-one, ship a hotfix.
After lunch
Section titled “After lunch”You run:
@claresia.gatespic.incident-postmortem INC-2026-04-1873The model assembles the timeline from your commit log + the SRE telemetry +
your support ticket commentary. You review, edit, capture as a decision.
End of day
Section titled “End of day”You’re shipping a firmware changelog for the v8.4 release. You type:
@claresia.gatespic.firmware-changelog-qaParameters:
- Changelog draft: (paste)
- JIRA filter:
project=FIRM and fix-version=v8.4
Returns:
- JIRA tickets in v8.4 that aren’t mentioned in your changelog (3 missed)
- Tickets mentioned in changelog without a closed JIRA (0 — clean)
- Clarity issues (1 ambiguous wording)
- Suggested ordering by user-facing impact
You add the missed tickets, re-publish.
Maturity bar
Section titled “Maturity bar”You’re now at L1 65% — three more weeks of the Tuesday + Friday cadence puts you at L1 100%.
3D Product Manager — daily workflow
Section titled “3D Product Manager — daily workflow”You’re a 3D Product Manager — owning the digital twin of a new product line through CAD review, supplier qualification, brand-voice gate for product naming, and the change-risk gate for any production-affecting decision.
You receive a PRD from a downstream team. You run:
@claresia.steve.prd-reviewThe model checks structural soundness, feasibility, and dependency mapping.
A naming proposal lands. You run:
@claresia.zottos.brand-voice-checkerParameters:
- Content:
Smart Lock SC1 — Adaptive - Channel:
product naming
Returns brand-voice match score + suggestions if needed.
The naming is locked. You’re about to commit a CAD change that affects manufacturing tooling. You run:
@claresia.gatespic.change-risk-reviewParameters:
- Change:
CAD revision 8.4 — adds 3 mounting points to spine plate - Affected lines:
tooling A4, tooling B2
Returns risk score + suggested rollout sequence + downstream-team checklist.
Production Planner — daily workflow
Section titled “Production Planner — daily workflow”You manage the planning cadence across factories (Italy, Romania, Tunisia, Vietnam — Dainese-style). Your week is a series of variance reviews, month-end checks, and vendor spend reconciliations.
Monday morning flash
Section titled “Monday morning flash”@claresia.ledger.variance-analysisYou review variance vs plan for the previous week’s production output, drill into the top 3 drivers, message the affected line managers.
Mid-month
Section titled “Mid-month”@claresia.ledger.month-end-checklistDay-by-day list tailored to your role: inventory adjustments, tooling write-offs, vendor invoices, capacity review.
Quarterly
Section titled “Quarterly”@claresia.ledger.vendor-spend-reviewReviews your top 25 vendors by spend, flags variances, suggests RFQ candidates.
Talent Maker — daily workflow
Section titled “Talent Maker — daily workflow”You’re an HR business partner / People Ops specialist. Your week is individual coaching prep, calibration data assembly, and team-level health readouts.
1:1 prep
Section titled “1:1 prep”@claresia.boss.one-on-one-prepParameters:
- Direct report:
Marco Mazzolin - Period:
last 2 weeks
Returns a structured agenda with: recent wins, recent ships, 1 open question, suggested follow-up topic.
Calibration cycle
Section titled “Calibration cycle”@claresia.boss.calibration-packReturns a pre-cycle pack: distribution of recent ratings, outliers worth discussing, fairness check across protected groups, suggested talking points.
Weekly digest
Section titled “Weekly digest”@claresia.boss.team-weekly-digestReturns a team-level digest of the week’s ships, blockers, and asks. You forward to the team’s manager + skip-level.
Quality Engineer — daily workflow
Section titled “Quality Engineer — daily workflow”You own quality across hardware + firmware + supplier. Your week is incident diagnosis, changelog QA, and DPIA / regulatory write-ups.
After any field issue
Section titled “After any field issue”@claresia.gatespic.incident-postmortemYou assemble the full lineage: complaint → root cause → remediation.
Pre-release QA
Section titled “Pre-release QA”@claresia.gatespic.firmware-changelog-qaSame as Firmware Engineer’s flow.
Regulatory review
Section titled “Regulatory review”@claresia.clawshield.dpiaParameters:
- Processing activity:
New BMS telemetry write-back to cloud (v8.4) - Data subjects:
End users (vehicle owners) - Categories:
Vehicle ID, location (city level), battery state of health
Returns a DPIA structured to your tenant’s template. You forward to your Privacy team for sign-off.
Maturity progression for manufacturing roles
Section titled “Maturity progression for manufacturing roles”L0 → L1 in ~4–6 weeks (slightly slower than office archetypes due to physical gating between digital actions).
L2 markers:
- Author at least one custom skill specific to your factory or product
- Use 5+ skills in a typical week
- Pass the Agent Operator Certification (Forge)
Why manufacturing-specific Coworks?
Section titled “Why manufacturing-specific Coworks?”Your work has unique characteristics:
- Multi-site coordination (factories in different countries, different time zones)
- Physical constraints (you can’t ship a hotfix to a stamping press as easily as to a cloud service)
- Regulatory weight (CE, ECE, ISO, BSI — depending on your products)
- Long product lifecycles (a part designed in 2026 may still be manufactured in 2032)
The cc-057 manufacturing Coworks ship cadence calendars + artifact templates tuned to these constraints.
@claresia.forge.coaching-session- Your CSM channel
- This docs site
- Your tenant’s “Real Incumbents” mapping (per cc-057 standing rule) — your Cowork is named after archetypes drawn from your actual roster