skills.rest
uzumaki-inc
uzumaki-incOFFICIAL
Explore all skills by this author →
GitHub

plan-devex-review

Plan structured developer experience reviews for APIs, CLIs, SDKs, or platforms.

Updated Apr 25, 2026
Search Tags:#planning#onboarding#personas#benchmarks#developer-experience#journey-design#devex
One-click install
npx skills add https://github.com/uzumaki-inc/uzustack --skill plan-devex-review-uzumaki-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-devex-review
Source: https://github.com/uzumaki-inc/uzustack/tree/main/_upstream/gstack/plan-devex-review
Command: npx skills add https://github.com/uzumaki-inc/uzustack --skill plan-devex-review-uzumaki-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a structured method to evaluate and improve developer experience across APIs, CLIs, SDKs, or platforms. This skill provides a repeatable framework to identify friction points, map opportunities, and align DX work with strategic goals.

Core Features & Use Cases

  • Three modes: DX EXPANSION (scope expansion and differentiation), DX POLISH (tactical polish across onboarding, docs, and tooling), and DX TRIAGE (focus on critical gaps).
  • It analyzes developer personas, benchmarks against competitors, designs magical moments, and traces friction points to generate actionable recommendations.
  • Proactively suggests developer-experience improvements when planning new APIs, CLIs, SDKs, or platforms.

Quick Start

Invoke the DX plan review to kick off a developer experience assessment for your API, CLI, SDK, or platform project.

Frequently Asked Questions about plan-devex-review

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

FAQPage Schema
How do I plan a developer experience review for my API or SDK?▼

To plan a developer experience review, structure your assessment around persona analysis, competitive benchmarking, and friction mapping to identify bottlenecks across the product lifecycle from onboarding to adoption.

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

Developer experience friction mapping identifies obstacles in developer journeys across APIs, CLIs, or platforms. You need it when developers struggle with onboarding or long-term adoption, requiring structured triage to pinpoint critical gaps.

What is the best way to improve developer onboarding for a new platform?▼

The best way to improve developer onboarding is applying a DX POLISH mode to tactically refine documentation and tooling, while designing magical moments to elevate the overall developer journey and reduce initial friction.

How do I benchmark my CLI or API against competitors for developer experience?▼

Benchmark your CLI or API by conducting a competitive analysis within a structured DX EXPANSION review, evaluating competitor developer journeys to identify scope expansion opportunities and strategic differentiation for your platform.

When should I focus on developer experience triage instead of scope expansion?▼

Focus on developer experience triage instead of scope expansion when your API or SDK has critical gaps causing immediate developer friction, requiring rapid assessment to stabilize the platform before planning broader improvements.

Related Skills

Explore More Software Engineering Skills→
ShaheerKhawajaShaheerKhawaja
8

ux-genie

Derive personas, user stories, and journey maps from UI guidelines.

Community
Advanced
BradliebsBradliebs

deepen-plan

Orchestrate parallel research agents to deepen project plans with actionable recommendations.

Community
Advanced
sencersoylusencersoylu

mixed-methods

Design mixed-methods studies integrating quantitative and qualitative data.

Community
Intermediate
tony30552001tony30552001

plan-devex-review

Map developer personas, benchmarks, and friction points to score DX readiness.

Community
Intermediate