plan-devex-review

Evaluate plan-based developer experience artifacts across eight assessment passes.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill plan-devex-review-akiyoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-devex-review
Source: https://github.com/akiyoshi/gstack-copilot-jp/tree/main/.github/skills/plan-devex-review
Command: npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill plan-devex-review-akiyoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework to evaluate and improve the developer experience of plans, guiding teams through comprehensive DX audits across discovery, installation, usage, and post-launch phases.

Core Features & Use Cases

  • Structured eight-pass DX assessment (Pass 1 through Pass 8) to uncover friction and actionable improvements.
  • Integration of empathy narratives, competitive benchmarks, magical moment design, and hall-of-fame references for concrete guidance.
  • Supports decision gates, design doc checks, and evidence-based scoring to align teams on DX priorities such as onboarding, error messaging, UX, and documentation quality.

Quick Start

Start by running /office-hours to generate a structured DX problem statement and empathy narrative.

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 for API and onboarding plans?

A structured eight-pass DX assessment evaluates developer experience across discovery, install, usage, and upgrade stages to uncover friction. The review integrates empathy narratives, competitive benchmarks, and hall-of-fame references to generate concrete remediation steps and measurable developer experience improvements.

What is a developer experience design review and when do I need it?

A developer experience design review systematically evaluates API, CLI, SDK, and documentation workflows to identify friction across the developer journey. You need one when planning onboarding guides or design docs to ensure teams align on DX priorities like error messaging, UX, and documentation quality.

How do I start a DX plan review using the office-hours approach?

Start a DX plan review by running the office-hours command to generate a structured problem statement and empathy narrative. This establishes the baseline context needed before applying the standardized eight-pass evaluation process to assess onboarding and API design artifacts.

Does this DX review process support CLI and SDK planning workflows?

Yes, the DX review process explicitly covers API, CLI, and SDK planning alongside onboarding guides and documentation workflows. It applies decision gates and design doc checks to validate developer experience quality across these specific technical surfaces.

What is the best way to measure developer experience improvements in plan reviews?

The best way to measure developer experience improvements is through evidence-based scoring combined with competitive benchmarks and hall-of-fame references. This standardized evaluation process enforces concrete remediation steps that raise scores toward best-in-class developer experiences.