Verified:GitHub

reversa-new

Orchestrate a greenfield product pipeline from natural-language ideas to PRD and SDD outputs.

1|Updated Dec 20, 2025

Search Tags:#ideation #requirements #orchestration #SDD #handoff #greenfield #product specs

One-click install

npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-new-rdinda

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: reversa-new
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-new
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-new-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a vague product idea into structured, actionable documentation that can move forward to implementation without losing clarity.

Core Features & Use Cases

Greenfield product pipeline orchestration: Drives a fixed sequence from ideation to requirements and SDD specs suitable for the next forward cycle.
Multi-agent spec artifact generation: Produces brainstorm, personas, PRD, and component-level SDD files inside the _reversa_sdd/ output folder.
Safe, user-controlled execution flow: Never advances automatically; it supports continue/recreate/re-execute-from-step with explicit user confirmation and preserves prior work unless you approve overwriting.

Quick Start

Start a new product spec pipeline by asking the AI to run /reversa-new and briefly describe your idea in one paragraph.

Frequently Asked Questions about reversa-new

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

FAQPage Schema

How do I turn a product idea into SDD-ready specs and a PRD?▼

The pipeline orchestrates greenfield product ideation by producing brainstorm notes, personas, PRD, and component-level SDD files inside a dedicated output folder for forward-cycle handoff.

Can I automatically generate product specifications without confirming each step?▼

It preserves prior work unless you explicitly approve overwriting, preventing accidental data loss during the ideation-to-specification workflow.

What is the best way to manage requirements and handoff for a new product cycle?▼

It advances through ideation, requirements, and component-level specifications only after explicit user confirmation, ensuring structured handoff.

Does generating greenfield product specs require any specific environment files?▼

The pipeline maintains state in a JSON file and stores all brainstorm, persona, PRD, and SDD artifacts in a dedicated folder during the specification workflow.