plan-devex-review

Benchmark developer experience against industry gold standards and identify actionable gaps.

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill plan-devex-review-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-devex-review
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/plan-devex-review
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill plan-devex-review-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developer-facing products like APIs, CLIs, SDKs, and documentation often have hidden friction points that block adoption, increase support requests, and frustrate users. This Skill eliminates guesswork by running structured, benchmark-backed reviews to surface exactly what's broken in your developer experience, so you can fix the issues that matter most instead of relying on anecdotal feedback.

Core Features & Use Cases

  • Three review modes: Choose DX EXPANSION to find competitive advantages, DX POLISH to bulletproof every user touchpoint, or DX TRIAGE to focus only on critical gaps that block users.
  • Industry benchmark comparisons: Measures your product against gold-standard developer experiences from Stripe, Vercel, Clerk, and other top tools to identify where you fall short.
  • Actionable scoring and recommendations: Traces friction points across onboarding, API design, error handling, docs, and tooling, then delivers prioritized fixes tied to real user outcomes.
  • Use case: Use this Skill before launching a new public API to catch design flaws that would otherwise lead to low adoption and high support costs, or to audit an existing CLI tool to reduce onboarding time for new users.

Quick Start

Use the plan-devex-review skill to run a full developer experience audit of your new public API and get a prioritized list of improvements to boost developer adoption.

Frequently Asked Questions about plan-devex-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit developer experience for my API to improve adoption?

To audit developer experience for an API, run a structured review that benchmarks onboarding, API design, and error handling against industry gold standards to identify friction points and prioritize fixes.

What is developer experience friction analysis and when do I need it?

Developer experience friction analysis systematically traces unresolved points across user touchpoints like SDKs, CLIs, and docs. You need it when anecdotal feedback shows poor tool adoption or rising support requests.

How do I benchmark my SDK onboarding against top developer tools?

Benchmark SDK onboarding by comparing your product's magical moments and touchpoints against gold-standard developer experiences from tools like Stripe and Vercel to identify competitive gaps.

Can I use this to review developer experience for a CLI tool?

Yes, you can review developer experience for a CLI tool to reduce new user onboarding time by tracing critical friction points and delivering prioritized fixes tied to real user outcomes.

What's the best way to triage critical developer experience gaps?

The best way to triage critical developer experience gaps is using a focused review mode that scores and prioritizes only the friction points that directly block users from succeeding.

Why does my developer-facing product have low adoption despite good documentation?

Low adoption despite good documentation often stems from hidden friction points in API design or error handling, requiring a benchmark-backed developer experience audit to surface and fix unresolved issues.