Skill Claude CodeCodex
Turn an unstructured stakeholder conversation, Slack thread, or meeting transcript into a structured spec (problem, goals, non-goals, success metrics, open questions). Use whenever a PM has raw conversational input and needs a first-draft spec, or when someone says "can you turn this into a doc" after a discussion.…
Skill Claude CodeCodex
Translate the same underlying project status into audience-appropriate versions (exec-brief, engineering-detail, customer-facing) without changing the underlying facts. Use when a PM needs to write a status update, especially when the same update needs to go to multiple different audiences. Pairs with…
Skill Claude CodeCodex
Decision framework for whether a blocker, risk, or conflict is actually worth escalating to leadership versus resolving at the working level. Use when a PM is unsure whether to "loop in" a director/VP, when a team is stuck and someone suggests escalating, or when reviewing whether a past escalation was warranted. Also…
Skill Claude CodeCodex
Decision framework for what to cut when a spec, sprint, or launch is too big for the time or team available. Use whenever a PM says a scope needs to shrink, a deadline is fixed and the work isn't, or someone asks "what can we cut" or "what's the MVP version of this." Also trigger when reviewing a spec that feels…
Skill Claude CodeCodex
Decision framework for whether a product/customer communication should actually be sent, not just how to write it. Use this whenever a PM is drafting an incident update, release announcement, policy change notice, deprecation warning, or any customer-facing message, and especially when someone asks "should we tell…