Use this skill when the user needs to organize teams, intake, prioritization, collaboration, or stakeholder management around outcomes instead of feature silos. Apply it for team topology, cross-functional workflow, backlog reset, trust rebuilding, defining "done" for outcomes, or shifting from handoff-driven delivery to collaborative outcome work. For defining outcomes or OKRs, prefer `outcome-thinking`. For roadmap reframing and journey maps, prefer `outcomes-based-planning`. For internal change programs and adoption experiments, prefer `outcomes-driven-transformation`.
