API Proposal Skill

Create complete, terse, and empirically grounded API proposals for dotnet/runtime. The output should have a high chance of passing the API review process.

Prototype first, proposal second. Proposals without working prototypes are speculative — they get sent back because reviewers can't verify the design works. The prototype IS the evidence.

When to Use This Skill

Use this skill when:

• Asked to propose a new API for dotnet/runtime
• Given a vague API idea or incomplete sketch that needs to be turned into a complete proposal
• Given an existing underdeveloped api-suggestion issue to refine
• Asked to prototype an API and draft a proposal
• Asked to "write an API proposal", "draft an api-suggestion", or "improve this proposal"

Core Principles

1. TERSENESS: Proposals are reviewed live by humans during API review meetings who often lack prior context. Long text is counterproductive unless warranted by design complexity. Focus on WHAT problem and HOW to solve it.