What problem does it solve? Teams building developer-facing products face pressure to become a platform - app marketplaces, extension points, partner integrations - without a disciplined way to decide whether outsiders should build on them, how far to open, and what permanent obligations that creates. This Skill turns that question into a gated decision with evidence, a chosen openness rung, and kill criteria. ## Core Features & Use Cases - Readiness gating: Scores counted demand, externalizable interfaces, identified builders, staffing, envelopment exposure, and complement readiness as pass, fail, or unknown before any design work. - Six-rung openness ladder: Ranks documented APIs, vendor-built integrations, partner-built integrations, extension points, installable apps, and runtime platforms by value per unit of effort, deleting rungs the organization cannot staff. - Complementor economics and obligations: Worksheets the business case per builder archetype, sets the value-share principle, and prices permanent obligations like deprecation policy, roadmap boundaries, and wind-down terms. - Use Case: A CEO whose board demands an app marketplace runs the workflow, fails the counted-demand gate, and ships a written decline memo with reopen conditions instead of a marketplace design. ## Quick Start Ask the assistant to decide whether your product should open an app marketplace or partner integration program, providing your customer count, requested integrations, and available team capacity.
