oss-strategy
Evaluate an open-source business and community strategy. Triggers on "open source strategy", "OSS 策略".
SKILL.mdskills/01-product/oss-strategy/SKILL.md
GitHubOpen Source Strategy
When to use
- Evaluate an open-source business and community strategy.
Not for: oss-polish for repository presentation.
Steps
Identify users, buyer, maintenance capacity and commercialization constraints.
Compare suitable business models against current primary evidence; avoid universal revenue ratios or launch-time claims.
Distinguish open-source licenses from source-available restrictions; verify obligations and leave adoption to the user.
Propose a bounded distribution experiment with success and stop criteria, costs and uncertainties.
Output: Suggested paths, subject to human audit: docs/research/strategy.md when durable strategy is requested.
Verify
- Recommendation matches real resources; license and commercial claims are sourced and adoption is explicit.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- product-principles.md — product discipline (opportunity = demand × giant blind spot ÷ difficulty, the real competitor is the current workaround).
- human-audit.md — document consent, readability and human review.
- references/commercialization-models.md — general pricing (subscription/freemium/usage/per-seat), value-based pricing, AI-product pricing trap, GTM motions (PLG/sales-led/product-led sales), indie-developer revenue ladder.
- GitHub README/Topics/About beautification:
08-ship/oss-polish.