Dadmin88/hermes-agency - Page 9

systemic-storytelling

Design narrative that emerges through systems, environment, simulation, item/state changes, NPC behavior, and player action rather than exposition alone.

activation-analysis

Analyze onboarding activation by identifying the earliest behaviors that predict durable value, measuring time and path to those behaviors, and separating correlation from useful product signals.

dropoff-diagnosis

Diagnose onboarding dropoff by locating the first meaningful friction point and distinguishing comprehension, motivation, trust, technical failure, prerequisite, latency, and audience-fit causes using quantitative and qualitative evidence.

first-run-copy

Write and evaluate onboarding copy that helps a new user understand value, choose the next action, recover from uncertainty, and complete setup without unnecessary explanation or product jargon.

onboarding-experiment

Design onboarding experiments around a specific activation hypothesis using clear treatment, assignment, funnel instrumentation, experience guardrails, and downstream retention evidence.

onboarding-flow

Design onboarding that moves a new user from initial intent to first meaningful value with minimal friction and measurable activation.

contribution-triage

Triage open-source issues and pull requests by validity, reproduction, scope, project fit, duplication, risk, ownership, and next action while preserving contributor context.

contributor-onboarding

Create and operate a contributor path from project orientation through environment setup, issue selection, implementation expectations, review, and recognition.

maintainer-backlog-health

Manage maintainer backlog using age, impact, dependency, contributor expectation, security/release relevance, and capacity instead of letting queues decay invisibly.

open-source-release-stewardship

Coordinate open-source release-facing maintenance including dependency updates, contributor credit, changelog inputs, upgrade notes, compatibility signals, and post-release repository follow-up.

repository-governance

Define and maintain repository governance for decision rights, maintainers, contribution policy, security reporting, conduct, deprecation, releases, and conflict resolution.

capacity-planning

Plan operational team or process capacity from demand, service expectations, work mix, variability, constraints, and recovery margin without confusing organizational capacity with Fleet node scheduling.

cron-operations

Audit and operate scheduled Hermes work across profiles. Detect missed, failed, paused, degraded, or repeatedly unhealthy cron jobs; apply only bounded safe recovery; and route actionable evidence to the owning agent.

incident-coordination

Coordinate an operational incident by establishing command, impact, workstreams, communication, decision cadence, evidence, and recovery ownership without replacing the technical responders.

operating-rhythm

Design a recurring operating cadence that turns current priorities, metrics, risks, decisions, and follow-through into reliable organizational routines without creating meeting theater.

operational-metrics

Define operational metrics that connect service outcomes, demand, flow, quality, reliability, backlog, and cost to decisions without rewarding metric gaming.

operational-review

Review an operating process for reliability, ownership, bottlenecks, controls, handoffs, and measurable improvement opportunities.

process-design

Design or improve an operational process by mapping outcomes, actors, inputs, decisions, handoffs, controls, exceptions, evidence, and failure recovery before automating it.

dependency-planning

Plan multi-profile work as an explicit dependency graph so independent tasks run in parallel, dependent work waits for real prerequisites, and handoffs preserve the evidence consumers need.

escalation-routing

Route blockers, conflicts, missing decisions, and unacceptable residual risk to the role or user with actual authority to resolve them, with a compact evidence-backed decision request.

profile-routing

Route Agency work to the named Hermes profile whose professional ownership best matches the required outcome, then let Fleet resolve that stable profile identity to an eligible live node or place it when necessary.

result-synthesis

Synthesize completed specialist work into one coherent outcome by preserving evidence and ownership, resolving conflicts through the correct authority, and separating validated conclusions from open risk.

validation-planning

Design proportionate, independent validation for multi-role work by mapping important claims and risks to the specialist, evidence, environment, and gate capable of proving them.

work-decomposition

Decompose a multi-role goal into bounded specialist assignments with explicit ownership, dependencies, validation criteria, and handoffs.

negotiation-prep

Prepare a partnership negotiation by defining interests, priorities, authority, alternatives, ranges, trade variables, evidence, risks, and approval boundaries before entering the conversation.

outreach-plan

Plan partnership outreach around target partner fit, shared value, evidence, contact strategy, sequencing, personalization, follow-up, qualification, and outcome tracking without mass generic solicitation.

partner-success-plan

Operate an active partnership through shared goals, ownership, enablement, launch, reporting, issue escalation, opportunity development, renewal, and exit so the relationship creates measurable value after the agreement is signed.

partnership-evaluation

Evaluate a potential partnership for strategic fit, reciprocal value, execution burden, incentives, risk, and measurable outcomes.

partnership-proposal

Build a partnership proposal that defines shared objective, audience or customer value, scope, contributions, economics, responsibilities, success measures, governance, risks, and next-step validation.

employee-lifecycle-operations

Design and operate employee lifecycle workflows from accepted offer through onboarding, role changes, leave events, and offboarding with owners, access, records, and controls.

manager-enablement

Create practical manager enablement for recurring people processes such as onboarding, feedback cycles, role changes, leave coordination, and escalation.

people-policy-operations

Turn approved people policy into usable operational procedures, communications, acknowledgements, exceptions, records, review cadence, and escalation paths without independently interpreting law.

people-process-audit

Audit a people-operations process for missed handoffs, stale access, privacy/record gaps, inconsistent treatment, unclear ownership, unnecessary friction, and control failures.

performance-cycle-operations

Operate the logistics and evidence flow of a performance/feedback cycle with timelines, participant rules, templates, reminders, calibration inputs, access, and completion tracking without making personnel decisions.

benchmark-design

Design trustworthy performance benchmarks with a precise question, representative workload, controlled environment, warmup and sampling discipline, statistical comparison, correctness checks, and regression thresholds.

bottleneck-analysis

Identify the system bottleneck that limits an end-to-end performance objective by connecting queueing, utilization, dependency time, contention, critical paths, and workload scaling rather than optimizing components in isolation.

latency-budgeting

Allocate and validate an end-to-end latency objective across serial and parallel work, network, queues, dependencies, computation, rendering, retries, and tail behavior using measured service contributions.

load-testing

Design and run load tests that represent real demand, concurrency, data, arrival patterns, bottlenecks, saturation, recovery, and service objectives without turning a synthetic benchmark into a production claim.

memory-analysis

Diagnose memory growth, pressure, allocation cost, retention, leaks, cache behavior, fragmentation, and out-of-memory failures using workload reproduction and runtime-specific evidence.

performance-investigation

Diagnose a performance problem using measurement, profiling, workload reproduction, bottleneck isolation, controlled changes, and regression evidence.