packaging

Design product packages or tiers by grouping customer outcomes, capabilities, limits, service levels, and expansion paths into understandable offers that support segmentation without arbitrary feature hostage-taking.

Ir para a instalação

Repositório: Dadmin88/hermes-agency
Última atividade na origem: 16 de agosto de 2026 às 06:25
Idioma detectado do SKILL.md: inglês
Estrelas: 8
Forks: 2

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/Dadmin88/hermes-agency --skill packaging

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

accessibility-audit

Perform a structured accessibility audit of a product experience or implementation and produce prioritized remediation guidance.

2026-08-16

accessible-design-review

Review product design artifacts before implementation for accessibility of information, interaction, focus, input, error recovery, responsive/reflow behavior, motion, contrast, content alternatives, and assistive-technology semantics.

2026-08-16

keyboard-testing

Validate a user flow with keyboard or equivalent non-pointer input by checking reachability, order, focus visibility, activation, escape, shortcuts, custom widgets, and recovery from dynamic UI changes.

2026-08-16

Ver todas deste repositório

Packaging

Use when deciding which capabilities, limits, support levels, or usage allowances belong together in plans or editions.

Procedure

Define target segments, their core jobs, willingness to pay, usage patterns, maturity, and reasons they may need different offers.

Inventory capabilities, usage limits, service levels, compliance or administrative features, and cost drivers that could form meaningful packaging dimensions.

Group around complete customer outcomes rather than randomly distributing essential workflow pieces to manufacture tiers.

Choose fences that correlate with segment value or cost, such as scale, governance, collaboration, advanced workflow, or service level.

Ensure each package has a clear audience, coherent promise, upgrade reason, and usable baseline without needing sales explanation for every distinction.

Model common customer journeys through trial, initial purchase, expansion, downgrade, and plan migration.

Check operational complexity across billing, entitlement, support, documentation, sales, analytics, and engineering before adding variants.

Validate comprehension and conversion with customer research or experiments and simplify tiers that create confusion without segmentation value.

Decision rules

Packaging is customer segmentation expressed as offers, not a feature-storage exercise.

Do not break a core workflow merely to create an upgrade gate.

More plans increase operational and cognitive cost.

Good upgrade paths follow growing customer value or needs.

Quality gate

Packaging is ready when each offer serves a recognizable segment and complete use case, fences are defensible, upgrade and downgrade paths make sense, entitlement complexity is manageable, and customers can understand the differences without a matrix of arbitrary exceptions.