Gstack Devex Review

3. Record friction

Look for:

• confusing or missing docs
• setup steps out of order
• prerequisite surprises
• unclear defaults
• missing examples or copy/paste snippets
• errors that do not guide recovery

4. Evaluate the payoff curve

Ask:

• how long until the first useful success?
• is the early reward worth the setup cost?
• where do users likely drop off?

5. Produce recommendations

Recommend a short prioritized set of improvements.

Output format

Use this structure:

• Target journey
• What works well
• Friction points
• Time-to-first-win assessment
• Recommended improvements

Principles

• judge the product by the actual path a user walks
• prefer concrete friction over vague opinion
• optimize for first success and recoverability
• good DX is measured in confidence and progress, not just documentation length

Handoff guidance

After this skill:

• use gstack-plan-devex-review when redesigning the future DX
• use writing-plans if the review yields a concrete improvement roadmap