reversa-framer

Separates problems from disguised solutions and produces a structured framing.md document.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-framer-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-framer
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.agents/skills/reversa-framer
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-framer-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often start ideation from a solution disguised as a problem, leading to building the wrong thing. This Skill acts as the Framer agent of the Ideation Team, interrogating the real pain behind an idea before any exploration begins. ## Core Features & Use Cases - Problem vs. Solution Classification: Analyzes the session's idea.md and flags when the input is a solution rather than a genuine problem. - Structured Framing Interview: Asks five targeted questions covering the pain, who suffers, when it hurts, the cost of inaction, and the job to be done, with follow-ups for vague answers. - Framing Document Generation: Writes a framing.md file with all sections stamped as planned, explicit [INDEFINIDO] markers for unanswered items, and legacy anchors when working on existing projects. - Use Case: A product team kicks off an ideation session with "we need a dashboard." The Framer challenges this framing, uncovers that analysts actually lose two hours daily reconciling spreadsheets, and records the validated problem statement for the next pipeline stage. ## Quick Start Start an ideation session with reversa-brainstorm, then invoke the Framer to interview me about my idea and generate the framing.md document.

Frequently Asked Questions about reversa-framer

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

FAQPage Schema
How do I validate a product idea before building a solution?▼

Run a framing interview that classifies the input as problem or solution, then asks five questions about the pain, who suffers, when it occurs, the cost of inaction, and the job to be done. The result is recorded in a framing.md document for downstream stages.

What is a job to be done statement in product discovery?▼

A job to be done statement follows the format: when a situation occurs, I want a motivation, so I can achieve a result. The Framer asks the user to complete this sentence to capture the underlying need rather than a feature request.

What happens if my idea is a solution instead of a problem?▼

The Framer tells you directly that you brought a solution, then asks what is behind it. If the solution turns out to be the right decision, that is recorded in framing.md and the pipeline continues without blocking.

Does the Framer work on existing legacy projects?▼

Yes. When the session context is legacy, the Framer reads existing soul.md, architecture files, and relevant specs as anchors. These references inform the framing but are never treated as ready-made answers.

What are the limitations of the framing stage?▼

The interview is limited to 10 turns and one follow-up per vague answer, after which the Framer synthesizes with available information. Unanswered sections are marked as undefined for later validation rather than being invented.