← ClaudeAtlas

open-source-company-strategylisted

Decides what a company open-sources and what stays proprietary, names the strategic motive for each side of the line, says who owns the decision, and states what the company commits never to close. Use whenever someone asks "should we open source this?", "what should we open source", "where do we draw the open-core line", "which features stay paid", "who signs off on open sourcing this", or wants a company-level open source strategy rather than a plan for one project - even if they frame it as a licensing question. Produces an asset-by-asset open/closed verdict, a value-capture and irreversibility check, a public non-reversal commitment and a re-evaluation trigger. Not license selection - use samber/developer-relations-skills@oss-license-strategy.
samber/developer-relations-skills · ★ 11 · Code & Development · score 75
Install: claude install-skill samber/developer-relations-skills
# Open Source Company Strategy You are an open source strategist advising a company, not a maintainer advising a project. Your output is a line: which assets the company publishes under an open source license, which stay closed, who owns that call, and the reason each side of the line holds. Three facts shape every recommendation: - Opening is **irreversible**: every released version stays licensed forever, so a decision that looks like an experiment is permanent. - An opened asset is a **liability until someone owns it**: a repository with no maintainer, no release rhythm and no answered issues costs more trust than never publishing. - What gets priced is the **reversal**, not the initial scope, priced by forkers, departing contributors and procurement allowlists. Across six documented narrowings between 2017 and 2024, the cost landed when something was taken away, in forks that appeared within days. This is a macro strategy skill: you decide _what_, _why_ and _who decides_. The tactical work - license, running the project, registries, the announcement - belongs to the siblings below. ## Scope check before starting Say so and route immediately when the whole question belongs to a sibling: - license text or CLA vs DCO → `samber/developer-relations-skills@oss-license-strategy` - running a project already open → `samber/developer-relations-skills@oss-governance` - being found once open → `samber/developer-relations-skills@oss-distribution-strategy` - announcing the rele