Surface OrderWhich integration surface to build next - by reversal cost and audience, not novelty.
Answer a short interview, mark the surfaces you have today, then paste your demand signals and the order you had in mind. Your browser ranks the lead posture from your buyer, puts the spec before anything derived from it, weighs blocked deals over telemetry over community asks, keeps MCP last until agent signals move it, and sequences the surfaces in waves your team can carry. Then the plan, and the handoff cards.
Try a sample:
1 The platform, and a short interview free
2 The surfaces you have today free
How deep each one goes. Partial means the API exists but some step of the flow still needs a person.
3 Demand signals and your draft order free
4 The build order and the checks free
What the page flags
The gates
The lead posture
The build order
Signals, your draft and the audiences
Area by area
5 Your gate sheet free
The skill's measurement gates, filled in from this plan - coverage, derivation, concurrency, groundwork and the review date. Re-run it at the review.
The run did not finish. Nothing was saved and what you entered is still here - press the button to try again.
The reply could not be read. Here it is as it came back:
NOT RUN YET
Caveats
Keep it handy:
Caveats
The page's check of this reply
7 Saved plans
How it works - and what is sourced
The order follows the skill: reversal cost plus audience, never novelty. Once outside developers depend on a surface, every behaviour of it is depended on, so commit early to the cheap-to-unwind surfaces - additive REST and webhooks - and delay GraphQL schemas and SDK signatures until the contract underneath is stable. A non-technical buyer who needs value in hours gets embedded components first, still on an API foundation.
SDKs, MCP and generated docs all derive from one spec, so a drifting spec is fixed first. A blocked deal outweighs telemetry, which outweighs community asks. MCP is a thin layer generated from an existing API, scheduled by RFPs or agent traffic. Build no more surfaces at once than the team can support for years. Reversal-cost tiers are the skill's synthesis; the gRPC, SQL, CLI and Terraform tiers are not in its table and are marked so.