plan-devex-review

Plan and execute an 8-pass developer experience review across API design, SDKs, docs, onboarding, and tooling.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill plan-devex-review-alejandrofigini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-devex-review
Source: https://github.com/AlejandroFigini/artist-portfolio/tree/main/.agent/skills/plan-devex-review
Command: npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill plan-devex-review-alejandrofigini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and prioritizes developer experience gaps across product touchpoints, enabling teams to close friction efficiently.

Core Features & Use Cases

  • Structured 8-pass DX framework to surface usability, onboarding, tooling, and documentation gaps.
  • Actionable deliverables: prioritized improvements, quick wins, and a reusable DX scorecard for stakeholders.
  • Use Case: run a full plan-devex-review on a new API surface to align onboarding, docs, and tooling before release.

Quick Start

Run the DX review using the plan-devex-review skill in your project to begin the eight passes and generate a DX score.

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 gaps in my API and SDK tooling?

A developer experience review systematically surfaces friction across API design, SDKs, docs, onboarding, and tooling. Running an 8-pass DX review identifies usability gaps and generates a prioritized action plan to improve the overall developer experience.

What is a DX score and how does it help prioritize onboarding improvements?

A DX score quantifies developer experience quality across product touchpoints using a reusable scorecard. It helps stakeholders align on friction points by providing prioritized findings and highlighting quick wins to close onboarding and tooling gaps efficiently.

How do I run a developer experience review before releasing a new API surface?

Running a full DX review on a new API surface applies an eight-pass framework to evaluate usability, documentation, and tooling. This process outputs a DX score and a prioritized improvement plan to align onboarding and docs before release.

Can I assess developer friction across documentation and onboarding without external dependencies?

Yes, a structured DX review can operate without external dependencies to evaluate documentation and onboarding workflows. It systematically surfaces developer friction across multiple touchpoints and generates actionable, prioritized improvements for the project.

What's the best way to identify quick wins for developer experience in a software project?

The best way to identify DX quick wins is executing a multi-pass developer experience review across API design, SDKs, docs, and tooling. This approach surfaces actionable improvements and outputs a prioritized plan to close friction efficiently.

When should I not use a structured 8-pass developer experience review?

An 8-pass DX review may be excessive for minor patches or single-component updates lacking API, SDK, or onboarding changes. It is designed for comprehensive evaluations across multiple product touchpoints rather than isolated feature additions.