plan-devex-review

Score developer experiences across APIs, CLIs, SDKs, and docs.

Updated May 14, 2026
One-click install
npx skills add https://github.com/lemig/transcriptor --skill plan-devex-review-lemig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-devex-review
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack/plan-devex-review
Command: npx skills add https://github.com/lemig/transcriptor --skill plan-devex-review-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-devex-review provides a structured, repeatable process to evaluate and improve the developer experience across APIs, CLIs, SDKs, and docs.

Core Features & Use Cases

  • Maps developer personas, benchmarks competitors, identifies magical moments, and traces friction points to score impact.
  • Supports three modes: DX EXPANSION for competitive advantage, DX POLISH for end-user excellence, and DX TRIAGE for critical gaps.
  • Proactively suggests improvements when the user asks for developer-facing product plans (APIs, CLIs, SDKs, libraries, platforms, docs).

Quick Start

Provide a concise prompt context and select a DX mode; the skill then guides the review workflow and outputs a prioritized action plan.

Frequently Asked Questions about plan-devex-review

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

FAQPage Schema
What is the best way to map developer personas for product roadmap planning?

Developer experience (DX) review is a structured process to evaluate and improve how developers interact with APIs, CLIs, SDKs, and docs. It maps personas, benchmarks competitors, and traces friction points to generate prioritized action plans for smoother onboarding.

How do I plan and score developer experience across multiple developer platforms?

To score developer experience, provide concise context about your APIs, CLIs, or SDKs and select a DX mode. The framework then maps personas, identifies magical moments, and traces friction points to output a quantifiable impact score and actionable recommendations.

When should I use DX triage versus DX expansion for API documentation improvements?

Use DX triage to identify and fix critical friction gaps in API documentation, and use DX expansion to build competitive advantage. DX polish is best when optimizing for end-user excellence across existing developer workflows and platforms.

Can I benchmark competitor developer onboarding workflows and identify friction points?

Yes, you can benchmark competitors by mapping their developer onboarding workflows against your own. The framework traces specific friction points across APIs and docs to score impact and suggest targeted improvements.

Does this developer experience framework work for CLI and library design reviews?

Yes, the framework applies directly to CLI and library design reviews. It evaluates developer interactions across CLIs, SDKs, and docs to proactively suggest improvements for developer-facing product plans.

What is the best way to map developer personas for product roadmap planning?

The best way to map developer personas for product roadmaps is to use a structured DX framework that scores impact based on benchmarking and friction tracing. This ensures roadmap planning aligns with actual developer onboarding needs.