plan-devex-review

Reviews developer-facing product plans for APIs, CLIs, SDKs, and docs against DX benchmarks.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill plan-devex-review-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-devex-review
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/plan-devex-review
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill plan-devex-review-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Plans for developer-facing products often ship with onboarding friction, weak error messages, and slow time-to-hello-world that cause developers to abandon the tool. This Skill audits a plan's developer experience before implementation, scoring it against proven DX benchmarks and forcing concrete decisions on personas, magical moments, and friction points. ## Core Features & Use Cases - Interactive DX Investigation: Interrogates developer personas, writes an empathy narrative of the actual getting-started path, and benchmarks time-to-hello-world against competitors via web search. - Three Review Modes: DX EXPANSION for competitive advantage, DX POLISH for bulletproofing every touchpoint, and DX TRIAGE for critical gaps only. - Journey Friction Tracing: Walks each stage (discover, install, hello world, real usage, debug, upgrade) with evidence from actual README, docs, and CLI help files, resolving each friction point individually. - Use Case: Before building a new CLI tool, run this review on your plan to discover that your install step assumes Docker without checking for it, then fix the plan before writing any code. ## Quick Start Ask the assistant to run a DX review on the current plan for your developer-facing API, CLI, SDK, or documentation.

Frequently Asked Questions about plan-devex-review

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

FAQPage Schema
How do I review developer experience of a product plan?

Run a DX review that traces the actual getting-started path from your README and docs, defines a target developer persona, and scores each journey stage against benchmarks like Stripe's sub-2-minute time-to-hello-world. Fix friction points in the plan before implementation.

What is a good time to hello world for developer tools?

Under 2 minutes is champion tier and correlates with 3-4x higher adoption. Two to five minutes is competitive baseline, while over 10 minutes causes 50-70% of developers to abandon the tool.

When should I use DX review versus engineering plan review?

Use DX review when the plan has developer-facing surfaces like APIs, CLIs, SDKs, or docs and you need to evaluate onboarding, error messages, and adoption friction. Use engineering review for architecture, testing strategy, and internal code quality.

Does DX review apply to non-developer products?

No. The review auto-detects developer-facing surfaces and exits gracefully if none exist, recommending design review or engineering review instead for consumer-facing or internal-only plans.

What are the review modes in a developer experience audit?

Three modes exist: DX EXPANSION proposes ambitious improvements for competitive advantage, DX POLISH bulletproofs existing touchpoints without scope additions, and DX TRIAGE covers only adoption-blocking gaps for urgent ships.