reversa-brainstorm

Orchestrates a five-stage ideation pipeline that clarifies raw ideas before development.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding with vague ideas, leading to rework and misaligned solutions. This Skill structures the pre-development phase by guiding a raw idea through framing, divergence, premortem risk analysis, and convergence before any artifact is built. ## Core Features & Use Cases - Multi-Stage Ideation Pipeline: Routes an idea through five specialized agents (framer, explorer, challenger, arbiter, pre-spec), each producing a Markdown artifact in _reversa_sdd/brainstorms/. - Session State Management: Tracks active ideation sessions in .reversa/active-ideation.json, detects in-progress sessions, and resumes from the correct stage based on files on disk. - Greenfield and Legacy Detection: Adapts the ideation context depending on whether a reverse-engineering extraction already exists in the output folder. - Use Case: A developer has a rough feature idea for an existing codebase. The Skill opens a numbered session, captures the literal idea, and walks it through problem framing, option exploration, risk premortem, and a final decision document ready to hand off to requirements or migration pipelines. ## Quick Start Ask the assistant to run /reversa-brainstorm and describe your idea in one or two sentences to start a guided ideation session.

Frequently Asked Questions about reversa-brainstorm

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

FAQPage Schema
How do I structure brainstorming before writing code?▼

Run the ideation pipeline with your raw idea as input. It creates a numbered session folder and guides the idea through framing, option exploration, premortem risk analysis, and a final decision document, each saved as a separate Markdown file.

What artifacts does a structured ideation workflow produce?▼

The pipeline produces five Markdown artifacts: framing.md separating problem from solution, options.md with divergent paths, risks.md from the premortem, decision.md with a recommended option and trade-offs, and pre-spec.md bridging to development.

Can I resume an interrupted ideation session?▼

Yes. Session state is stored in .reversa/active-ideation.json and the actual stage is detected from files on disk. When a session is in progress, you can continue where you stopped, start a parallel session, or reopen a specific stage.

Does ideation work without an existing codebase analysis?▼

Yes. The workflow detects whether a reverse-engineering extraction exists in the output folder. Greenfield sessions operate only on the idea you provide, while legacy sessions anchor ideation in the previously mapped documentation.

What are the limitations of an orchestrated brainstorm pipeline?▼

The orchestrator never writes the pipeline documents itself and never advances stages automatically; each handoff requires explicit user confirmation. It also never produces code during ideation, so implementation must happen in downstream pipelines.