What problem does it solve? Companies debate "should we open source this?" as one question and get it wrong: they open the wrong asset, pick a license instead of a value-capture mechanism, publish with no maintainer, or reverse course later and pay the reputational cost in forks. This Skill turns that debate into an asset-by-asset decision with a named motive, a named decider, and a public non-reversal commitment. ## Core Features & Use Cases - Asset-by-asset verdicts: Inventories SDKs, specs, infrastructure, tooling, and product cores separately, then runs each through five gates (irreversibility, differentiating-vs-context, value capture, contribution viability, ownership) to produce Open, Closed, or Not-yet verdicts. - Candidate line ranking: Presents and ranks interface-open, infrastructure-only, and buyer-tiered open-core boundary options, calibrated to company type (startup, public software company, non-software company) and B2B versus B2C buyers. - Decision rights and commitments: Separates the business call from compliance review, names who decides and who can veto, and drafts a published commitment stating what the company will never close. - Use Case: A Series A founder asks whether to open source the core product before a board meeting. The Skill interviews for motive and constraints, rejects decorative motives like "competitors did it", ranks candidate lines, deletes buyer-tiered open core on the stated irreversibility constraint, and delivers an executive brief with verdicts, owners, annual cost, and a re-evaluation trigger. ## Quick Start Ask the assistant to decide what your company should open source, describing what you sell, the candidate assets, and who can approve the decision.
