persona-review

Evaluate D&D adventure designs against five canonical personas into structured reviews.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/giodl73-repo/QUEST --skill persona-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-review
Source: https://github.com/giodl73-repo/QUEST/tree/main/.claude/skills/persona-review
Command: npx skills add https://github.com/giodl73-repo/QUEST --skill persona-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams evaluate adventure designs against five canonical design personas to surface blind spots and actionable improvements.

Core Features & Use Cases

  • Design-persona scoring across five personas on eight axes
  • Output per-persona review files and a SUMMARY.md
  • Pre-conditions and pipeline integration with module-binder and playtest rubric

Quick Start

Provide a compiled adventure module.md and run the persona-review pipeline to generate per-persona reports

Frequently Asked Questions about persona-review

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

FAQPage Schema
How do I run a persona-based design review on a D&D adventure module?

To run a persona-based design review, provide a compiled adventure module.md and execute the persona-review pipeline to evaluate the design against five canonical D&D personas, generating structured per-persona review files.

What files do I need to set up before running an adventure design review?

You need a compiled adventures/<slug>/module.md file, a reviews directory, and the personas rubric context located at personas/playtest-rubric.md to execute the adventure design review workflow.

How does design-persona scoring evaluate an RPG adventure module?

Design-persona scoring evaluates an RPG adventure module by processing the compiled design against five canonical D&D personas across eight axes, outputting per-persona review files and a SUMMARY.md to surface blind spots and actionable improvements.

When should I use a persona review in the RPG design pipeline?

You should use a persona review after compiling your module with module-binder and before the actual playtest phase, ensuring the adventure design is evaluated against the playtest rubric to identify structural blind spots.

Can I review adventure designs without a compiled module.md file?

No, you cannot review adventure designs without a compiled module.md file because the persona-review workflow specifically requires this compiled input and the playtest-rubric.md context to generate structured per-persona reports.

What is the best way to identify blind spots in tabletop adventure designs?

The best way to identify blind spots in tabletop adventure designs is to evaluate the compiled module against five canonical design personas across eight axes, generating per-persona reports and a SUMMARY.md for actionable improvements.