devex-review

Audit developer documentation by navigating, timing workflows, and generating a scorecard.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/miko06/MedicineSimulator --skill devex-review-miko06
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/miko06/MedicineSimulator/tree/main/.opencode/skills/gstack-devex-review
Command: npx skills add https://github.com/miko06/MedicineSimulator --skill devex-review-miko06

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a live developer experience audit, testing the developer experience (DX) by navigating documentation, timing workflows, and producing a DX scorecard.

Core Features & Use Cases

  • DX Testing: Uses the browse tool to test developer experience, navigating documentation, timing workflows, and capturing error messages.
  • Scorecard Generation: Produces a DX scorecard with evidence of the audit.
  • Comparison with Plans: Compares actual DX against pre-defined plans if they exist.
  • Use Case: Ideal for post-implementation checks, when requested to test DX, or for proactively suggesting improvements after feature deployment.

Quick Start

Invoke the skill by saying 'dx audit' or 'test the developer experience'.

Frequently Asked Questions about devex-review

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

FAQPage Schema
What is a developer experience audit and how does it work?

A developer experience (DX) audit tests developer documentation by navigating workflows, timing execution, and capturing errors to produce a DX scorecard with evidence of friction points.

How do I test developer onboarding workflows for friction?

Test developer onboarding workflows by using a browsing tool to navigate documentation, timing each step, and capturing error messages to identify friction points in the setup process.

Can I generate a DX scorecard after deploying a new feature?

Yes, you can generate a DX scorecard after feature deployment by running a live audit that navigates documentation, times workflows, and compares actual results against pre-defined plans.

Do I need access to developer documentation to run a DX audit?

Yes, running a DX audit requires access to developer documentation and an execution environment to actively navigate workflows, time processes, and capture error messages accurately.

What's the best way to proactively improve developer experience?

Proactively improve developer experience by performing live audits post-deployment, testing navigation and error handling, then comparing the results against pre-defined plans to identify gaps.

Does the DX audit compare actual workflows against pre-defined plans?

Yes, the DX audit compares actual developer experience against pre-defined plans if they exist, measuring live navigation and timing against expected outcomes to generate a scorecard.