Atomic Team Scaling

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 a product decision trades customer delight against business margin, pricing changes are being evaluated for customer perception impact, or the team debates investing in a 'nice to have' feature vs improving unit economics — even if the request is about 'pricing' or 'product strategy' rather than explicitly about delight vs margin.

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.