reversa-new

Orchestrate a greenfield reverse-specification workflow into SDD artifacts with CONTINUAR checkpoints.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-new-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-new
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-new
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-new-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reversa-new turns a natural-language product idea into complete, traceable specification documents that an AI coding agent can safely use, instead of relying on vague intent or “vibe coding”.

Core Features & Use Cases

  • Greenfield orchestration: Coordinates the Code New Project agent pipeline from ideation to SDD-ready component specs.
  • Checkpointed, user-controlled execution: Prevents accidental reruns by tracking pipeline stage in .reversa/state.json and requiring explicit CONTINUAR between agents.
  • Structured outputs for forward engineering: Generates newproject-brief.md, ideation.md, personas.md, prd.md, and sdd/<componente>.md to support a later /reversa-forward evolution cycle.

Quick Start

Tell the skill what you want to build by running: /reversa-new "Describe your product idea in one or two paragraphs".

Frequently Asked Questions about reversa-new

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

FAQPage Schema
How do I generate SDD component specifications from a natural language product idea?

To generate AI-ready SDD artifacts from a product idea, use a greenfield reverse-specification workflow. It orchestrates named sub-agents to draft ideation, personas, PRDs, and component specs, preventing vague intent in forward engineering.

What is the best way to draft a PRD for greenfield planning without vibe coding?

Drafting a PRD for greenfield planning without vibe coding requires transforming your initial idea into structured, traceable documents. A checkpointed orchestration pipeline synthesizes research and ideation into an operational contract for AI agents.

How do I orchestrate AI agents to produce operational contracts for new products?

You orchestrate AI agents to produce operational contracts by coordinating named sub-agents in a fixed sequence. This pipeline tracks stages via state.json checkpoints, requiring explicit CONTINUAR confirmations to prevent accidental reruns during synthesis.

Does this greenfield specification workflow require checkpoint confirmations between stages?

Yes, this greenfield specification workflow requires explicit CONTINUAR confirmations between stages. It tracks the pipeline stage in a state.json checkpoint file and never auto-advances, ensuring user-controlled execution and preventing accidental reruns.

Can I use this orchestration pipeline to synthesize user personas and research data?

Yes, you can use this orchestration pipeline to synthesize user personas and research data. The workflow processes ideation and persona synthesis, outputting dedicated markdown files to support the later forward engineering evolution cycle.

What limitations should I expect when using checkpointed pipelines for product requirements?

A limitation of using checkpointed pipelines for product requirements is the strict manual intervention required. The workflow never auto-advances without explicit CONTINUAR confirmations, meaning you must actively manage transitions between the orchestrated sub-agents.