plan-devex-review

Analyze developer experience plans across eight evaluation passes.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/abhishekmmgn/didactic-invention --skill plan-devex-review-abhishekmmgn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-devex-review
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/plan-devex-review
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill plan-devex-review-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable developer experience (DX) review process to surface friction, gaps, and opportunities across a project’s developer-facing journey, enabling teams to ship better APIs, docs, and tools faster.

Core Features & Use Cases

  • Eight-pass DX evaluation workflow covering Getting Started, API/CLI/SDK, Error Messages, Documentation, Upgrade Path, Dev Environment, Community, and DX Measurement streams.
  • Interactive, goal-oriented collaboration that surfaces friction points, records decisions, and generates actionable implementation tasks with traceable outcomes.
  • Generates a plan-ready DX scorecard and a concrete improvement backlog to align product, design, and engineering teams.

Quick Start

Provide a structured developer experience review by loading the plan and launching the eight passes for the target 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 conduct a developer experience review for a software project?

You conduct a developer experience review by running a multi-pass evaluation across eight streams like getting started, documentation, and error messages to identify friction and generate a DX scorecard with actionable improvement tasks.

What is a DX scorecard and how does it improve developer adoption?

A DX scorecard is an evaluation output that quantifies developer experience gaps and risks across a project, aligning engineering and product teams with a concrete task list to accelerate developer adoption.

How do I identify gaps and friction in my project's API and CLI documentation?

You identify API and CLI documentation gaps through an eight-pass DX evaluation that analyzes error messages, upgrade paths, and developer environments to log decisions and produce traceable improvement tasks.

Can I use a plan-mode DX review to generate actionable engineering tasks?

Yes, a plan-mode DX review logs decisions across eight evaluation passes and generates a concrete improvement backlog, providing traceable implementation tasks that align product, design, and engineering teams.

What areas does a multi-pass developer experience evaluation cover?

A multi-pass developer experience evaluation covers eight streams: getting started, API/CLI/SDK, error messages, documentation, upgrade paths, dev environments, community, and DX measurement.

When should I run a structured DX evaluation instead of ad hoc feedback?

Run a structured DX evaluation when your project requires multi-pass analysis of developer-facing friction, ensuring repeatable logging of gaps and risks across eight streams rather than relying on isolated feedback.