devex-review

Audits documentation and onboarding flows to produce an evidence-based DX scorecard.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Live developer experience auditing surfaces onboarding friction by actively using docs, getting started flows, and CLI cues to reveal blockers the user would encounter.

Core Features & Use Cases

  • Hands-on DX testing: Navigate docs, test onboarding, and verify CLI flows to build a comprehensive DX scorecard with concrete evidence.
  • Evidence-driven improvements: Collect screenshots, error messages, timing data, and observed pain points to guide improvements.
  • Use Case: A developer new to a project follows the onboarding guide, reports friction points, and the team uses the DX scorecard to triage fixes.

Quick Start

Navigate the docs, test the onboarding flow, and produce a DX scorecard with evidence.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I audit developer onboarding friction in documentation?

Audit developer onboarding by actively navigating docs, testing getting-started flows, and verifying CLI cues to surface blockers. It captures screenshots, error messages, and timing data to produce an evidence-driven DX scorecard for triaging friction points.

What is a developer experience scorecard and how does it work?

A DX scorecard synthesizes onboarding and documentation clarity issues into a repeatable evaluation. It works by capturing timing data, observed pain points, and error messages during hands-on testing to guide evidence-driven improvements for the development team.

Can I test CLI cues and getting-started flows end-to-end?

Yes, you can test CLI cues and getting-started flows end-to-end. The evaluation requires a browser or browse tool to navigate pages, capture screenshots, record error messages, and measure time to first meaningful hit during the onboarding process.

How do I measure time to first meaningful hit during onboarding?

Measure time to first meaningful hit by actively testing the documentation and getting-started flow. The process requires a browse tool to navigate pages, capture timing data, and record observed pain points to evaluate toolchain interactions and documentation clarity.

What is the best way to evaluate documentation clarity for new developers?

Evaluate documentation clarity by simulating a new developer's journey through the onboarding guide. Actively navigate the docs, test toolchain interactions, and collect concrete evidence like error messages and screenshots to build a comprehensive DX scorecard.

Does developer experience testing require a browser to navigate pages?

Yes, developer experience testing requires a browser or browse tool to navigate pages. This access is necessary to actively test onboarding flows, verify CLI cues, capture screenshots, and collect timing data for the DX scorecard.