reversa-researcher

Transform audience descriptions into structured personas with validated user journeys.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-researcher-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-researcher
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-researcher
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-researcher-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a raw target audience description from ideation into structured, decision-ready personas with clear user journeys for product planning.

Core Features & Use Cases

  • Persona deepening: Asks targeted questions per persona (daily context, technical level, and final objective) to refine ambiguity from ideation.
  • Jornada mapping: Builds a 5–7 step main journey per persona in an easy-to-validate format.
  • Deliverable generation: Writes the confirmed personas and journeys into <output_folder>/personas.md using doc language for the final artifact.

Quick Start

Ask it to run for /reversa-new by providing ideation.md in the configured output folder, then choose the number of personas to generate and confirm the proposed journeys.

Frequently Asked Questions about reversa-researcher

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

FAQPage Schema
How do I turn raw ideation into structured personas for a PRD?

To turn raw ideation into structured personas for a PRD, you need to refine target audience descriptions by defining daily context, technical level, and final objectives, then map these into validated step-by-step user journeys.

What is the best way to map user journeys for product planning?

Mapping user journeys for product planning works best when you build a 5–7 step main journey per persona in an easy-to-validate format, ensuring each step aligns with the user's final objective before generating the final artifact.

Does persona generation require a specific ideation file format?

Persona generation requires reading an existing ideation.md file located within your configured output folder, loading the raw audience description to transform it into decision-ready user profiles and validated journeys.

Can I specify the number of user profiles generated from market research?

Yes, you can specify the number of user profiles generated from market research by prompting for the desired persona count, allowing the system to iterate on journey validation and deepening details for each individual profile.

How are confirmed personas and user journeys written to the output folder?

Confirmed personas and user journeys are written atomically to personas.md in your output folder, ensuring the deliverable uses the designated doc language for a structured, decision-ready PRD artifact.