oss-growth
Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md.
⌘ K
Newest skills
79 skills
apm-strategy
Activate for changes to project positioning, release communication, community-facing artifacts, or breaking-change decisions in microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release workflows, and issue templates.
product-council
Convene the Product Development Council — six orthogonal product-delivery lenses anchored by a mandatory problem-validation gate. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
product-council-here
Convene the Product Development Council on the CURRENT conversation — the plan, roadmap, or scope decision built in this session. The INLINE counterpart to /product-council (which forks isolated and cannot see the chat). Use when you want the council to critique what we're working on right now.
positioning-critic
Competitive-differentiation reviewer that refuses to accept "the user wants this" as sufficient. Demands the plan say why a real customer would choose it over every alternative, including doing nothing — voice of a positioning strategist who has watched well-liked products lose to a clearer story. Use at any product checkpoint — plan, roadmap, go-to-market framing — when nobody can say why users would switch or pay, the competitive landscape is unaddressed, or "no one else does this" is asserted without checking: "why us, why this, why now?"
outcome-cartographer
Outcome-validity reviewer that refuses to count shipped work as progress until it maps to a measurable change in behavior. Hunts the gap between "we shipped it" and "we moved the number" — the output mistaken for an outcome. Use at any product checkpoint — plan, roadmap, PRD, ship review — when deliverables carry no metric, "done" is confused with "worked," or nobody can say how success will be measured: "what measurable outcome defines success, and how will we know we moved it?"
bet-sizer
Delivery-risk reviewer that sizes a plan's investment against the team's real confidence it will land. Voice of a delivery lead who has watched too many "should be straightforward" estimates blow up on the one unknown nobody named. Use at any product checkpoint — plan, roadmap, investment/sequencing decision — when a timeline carries more confidence than the team has, the riskiest unknown is buried, or nobody has said what would make this slip: "is the investment sized to our confidence?"