Delight Margin Balance

Make sure to use this skill whenever designing a test for a subjective or 'soft' feature, building a business case for UX improvements, measuring the impact of design polish, validating whether a feature that 'feels good' actually moves metrics, or justifying investment in non-functional improvements — even if the request is about 'A/B testing' or 'experiment design' rather than explicitly about delight.

Make sure to use this skill whenever converting a feature commitment into a testable experiment, designing validation for a product bet, creating kill criteria for a planned initiative, structuring a roadmap item as a hypothesis, or preparing for a build/kill decision — even if the request is about 'roadmap planning' or 'product strategy' rather than explicitly about hypotheses.

Make sure to use this skill whenever evaluating whether to build a requested feature, triaging feature requests from a vocal minority, auditing the product for low-adoption features, deciding what to cut during scope reduction, or assessing whether a feature adds complexity disproportionate to its usage — even if the request is about 'feature prioritization' or 'simplification' rather than explicitly about killing niche features.