# Develop Platform Product Thinking

> Apply platform and API product thinking to define developer experience, extensibility, and ecosystem strategy. Use this skill when a team is building a platform, API, or developer-facing product.

- Skill: `alexe-ev/develop-platform-product-thinking` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add alexe-ev/develop-platform-product-thinking`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alexe-ev/develop-platform-product-thinking/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: alexe-ev (https://skillmd.com/u/alexe-ev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alexe-ev/develop-platform-product-thinking

---


# Develop Platform Product Thinking

## Purpose
Help teams apply platform product thinking to define a clear developer experience, extension model, and ecosystem strategy.

## Skill type
Conceptual skill

## Use this skill when
- A product is evolving into a platform with external developers or partners
- An API product needs developer experience strategy
- A team is deciding how much to expose vs. internalize in a platform
- An ecosystem or marketplace strategy needs to be defined

## Do not use this skill when
- The goal is technical API design (a technical, not product, skill)
- The goal is internal tool or workflow automation

## Required inputs
- Product type and current capabilities
- Developer or partner audience

## Optional inputs
- Current API or integration surface
- Developer feedback
- Competitive platform landscape
- Business model for the platform

## Upstream context
Works best when:
- Product strategy is defined
- Target developer segment is identified

## Downstream handoff
Output can feed:
- prioritize-architecture-aware (platform strategy informs architectural priorities)
- develop-positioning-messaging (platform needs developer-facing positioning)

## Instructions
1. Define the platform layer: what does it expose, to whom, and why?
2. Identify the developer/partner value proposition.
3. Define the developer experience principles.
4. Assess the extensibility model: open / controlled / hybrid.
5. Identify ecosystem opportunities and risks.
6. Define the build vs. partner vs. ecosystem boundary.

## Output
Provide:
- Platform layer definition
- Developer/partner value proposition
- Developer experience principles
- Extensibility model recommendation
- Ecosystem opportunity and risk assessment
- Build vs. partner boundary decision
- Open questions

## Risks / caveats
- Platform products have two customers: end users and developers — both must win
- Over-opening a platform creates quality and support risks
- Developer adoption requires excellent documentation — factor it into the platform plan