Dadmin88/hermes-agency - Page 12

change-control

Control consequential release changes by making scope, revision, evidence, approvals, timing, exceptions, and post-approval drift explicit without turning every small change into bureaucracy.

post-release-validation

Validate a release after deployment using revision-specific health, critical user flows, data integrity, migrations, observability, error budgets, and rollback criteria before declaring it complete.

release-checklist

Build and execute a release checklist from the actual release surface, required evidence, owners, dependencies, approvals, rollout steps, and recovery conditions rather than a generic template.

release-readiness

Assess whether a release is ready to ship using evidence from scope, testing, security, operations, documentation, rollback, and stakeholder approvals.

rollback-plan

Design a release rollback or forward-recovery plan from failure modes, state changes, data compatibility, trigger conditions, authority, execution steps, and validation evidence.

audience-segmentation

Segment release-note information by the readers whose actions or workflows differ, such as end users, administrators, developers, operators, or integrators, without duplicating the entire release for each audience.

breaking-change-callout

Document a breaking or behaviorally incompatible release change with affected users, old and new behavior, required migration, deadlines, mixed-version implications, recovery, and exact references.

changelog-curation

Curate repository and product changes into a user-meaningful changelog by selecting externally relevant behavior, grouping related changes, verifying versions and scope, and excluding internal noise.

release-notes

Turn verified shipped changes into concise release notes organized around user impact, upgrade implications, fixes, and compatibility concerns.

upgrade-summary

Summarize an upgrade for existing users through benefits, changed behavior, prerequisites, compatibility, migration effort, validation, rollback or recovery, and post-upgrade differences.

acceptance-criteria

Turn requirements into precise, observable acceptance criteria covering success, failure, permissions, boundaries, states, and constraints without dictating unnecessary implementation details.

ambiguity-review

Review requirements for undefined actors, terms, states, timing, ownership, limits, conflicts, assumptions, and hidden implementation choices before ambiguity turns into divergent work.

edge-case-analysis

Identify and classify requirement edge cases across boundaries, invalid or missing input, permissions, concurrency, timing, partial failure, state transitions, limits, recovery, and unusual but plausible user behavior.

requirements-specification

Convert approved product and business intent into precise functional, non-functional, interface, data, and acceptance requirements.

traceability

Maintain requirement-level traceability from source need through decisions, product behavior, acceptance evidence, implementation references, and change history so scope and validation remain auditable.

evidence-brief

Produce a concise decision brief that presents the research question, strongest evidence, contrary evidence, confidence, implications, and unresolved gaps with citations.

fact-verification

Verify consequential factual claims through primary or authoritative sources, exact dates/versions, cross-checks, and context review.

literature-synthesis

Synthesize multiple papers, reports, standards, and primary sources into a coherent evidence map that preserves differing definitions, methods, and results.

research-question-framing

Convert a broad question into answerable subquestions, evidence requirements, scope limits, source hierarchy, and stop criteria.

source-quality-assessment

Assess a source for authority, proximity, methodology, incentives, currency, completeness, reproducibility, and fit to the specific claim.

crm-data-governance

Govern CRM and revenue-system data through field definitions, ownership, required evidence, deduplication, identity resolution, access, change control, and quality monitoring.

pipeline-health-review

Review pipeline health using stage aging, conversion, coverage, source quality, slippage, loss reasons, capacity, and data completeness without treating booked value as guaranteed.

revenue-forecast-operations

Produce an operational revenue forecast by reconciling pipeline evidence, historical conversion/velocity, renewals/expansion, owner commits, timing risk, and scenario ranges.

revenue-handoff-automation

Design reliable automation for marketing-sales-CS handoffs with eligibility rules, enrichment, routing, SLA timers, deduplication, retries, and exception queues.

revenue-lifecycle-design

Design a shared revenue lifecycle from audience/lead through qualification, opportunity, customer, expansion, renewal, and exit with explicit entry/exit rules and ownership.

demo-script

Write a product demo script that proves one or more capabilities through a realistic user goal, exact setup, visible actions, narration, proof points, transitions, and recovery from likely live-demo failure.

explainer-script

Write an explainer script that moves an unfamiliar audience from problem and context through a simple mental model, concrete example, proof, and next action using visuals to carry complexity wherever possible.

revision-pass

Revise a script in deliberate passes for structure, clarity, character or voice, timing, visual opportunity, factual accuracy, production feasibility, and line economy instead of rewriting everything at once.

scene-writing

Write a scripted scene around character goals, conflict, change, subtext, visual action, setting, pacing, and a clear turn so the scene earns its place in the larger narrative.

script-development

Develop a script from purpose, audience, beat structure, visual action, spoken language, pacing, and production constraints.

script-outline

Outline a video, explainer, demo, trailer, scene, or spoken script through audience, objective, hook, beats, evidence, visual or audio support, timing, and payoff before drafting dialogue or narration.

backlog-health

Review a delivery backlog for clear outcomes, ordering, dependencies, readiness, stale work, oversized items, and decision ownership without turning refinement into mandatory ceremony.

flow-metrics

Measure iterative delivery flow using throughput, lead/cycle time, work age, work in progress, blocked time, and predictability without turning metrics into individual performance scores.

impediment-removal

Remove delivery impediments by identifying the actual blocked condition, decision owner, dependency, authority, and smallest intervention that restores flow without taking over another specialist's work.

iteration-health

Diagnose and improve the health of an iterative delivery cycle by exposing blockers, work-in-progress, unclear commitments, and process friction.

retrospective

Facilitate a retrospective that turns recent delivery evidence into a small number of owned process experiments or decisions without becoming a blame session or ritual complaint list.

authentication-review

Review an authentication system or change across identity proof, credential handling, sessions or tokens, recovery, revocation, abuse resistance, logging, and negative-path validation.

authorization-review

Review authorization for complete server-side enforcement of roles, permissions, ownership, tenant boundaries, object access, privileged actions, and policy changes.

dependency-risk

Assess software dependency and supply-chain risk using inventory, provenance, advisories, reachability, install/build behavior, maintenance signals, update impact, and compensating controls.

incident-analysis

Analyze a security incident from detection through containment, evidence preservation, scope, timeline, root cause, credential and data impact, remediation, validation, and durable prevention.