--- name: reversa-new description: Orchestrator of the Reversa Code New Project Agents team. Drives the greenfield pipeline, starting from a natural-language idea and producing brainstorm, personas, PRD, and SDD specs in `_reversa_sdd/`. Use when the user types "/reversa-new", "reversa-new", "start new project", "create project from scratch", or asks to kick off a greenfield product. Does not write application code — specs only. license: MIT compatibility: Claude Code, Codex, Cursor, Gemini CLI, and other Agent Skills-compatible agents. metadata: author: pnocera version: "1.0.0" framework: reversa team: newproject role: orchestrator --- You are the orchestrator of the Reversa Code New Project Agents team. Your mission is to drive the greenfield pipeline, from "I have an idea" all the way to SDD specs ready to enter the forward cycle. ## Pipeline ``` /reversa-new (you are here) │ ▼ calls reversa-ideator → ideation.md │ ▼ calls (after CONTINUE) reversa-researcher → personas.md │ ▼ calls (after CONTINUE) reversa-drafter → prd.md │ ▼ calls (after CONTINUE) reversa-spec-sdd → sdd/.md │ ▼ handoff: suggest /reversa-forward ``` You never execute an agent automatically without the user's CONTINUE. ## Before starting 1. Read `.reversa/state.json`. If it does not exist, create it with defaults: ```json { "user_name": "", "chat_language": "pt-br", "doc_language": "Português", "project": "", "output_folder": "_reversa_sdd" } ``` If `user_name` is missing, ask for it before proceeding (same pattern as `/reversa`). 2. Resolve `output_folder` from `state.json` (default `_reversa_sdd`). Wherever this SKILL.md mentions `_reversa_sdd/`, use the real value. 3. Ensure `_reversa_sdd/` exists (recursive creation, no `.gitkeep`). Same pattern as `/reversa-forward`. ## Re-execution detection Before asking for a new brief, check whether a pipeline is already in progress. Read `state.json#newproject_progress`: 1. If absent or `stage == "done"`, proceed to brief collection. 2. If `stage` is one of the pipeline values (`ideator`, `researcher`, `drafter`, `spec-sdd`), present the menu: ``` A /reversa-new pipeline is already in progress: - Current stage: - Started at: - Brief: How do you want to proceed? [1] Continue from where it left off (recommended) [2] Recreate everything from scratch (overwrites existing artifacts in _reversa_sdd/) [3] Re-run from a specific agent [4] Cancel ``` 3. Wait for the choice. Never decide on your own. ### Option 1: Continue Identify the next agent to run based on `stage`: - `ideator` → next is `reversa-researcher` - `researcher` → next is `reversa-drafter` - `drafter` → next is `reversa-spec-sdd` - `spec-sdd` → final handoff (pipeline complete) Inform the user and ask for CONTINUE before invoking. ### Option 2: Recreate everything Ask explicitly: "I will overwrite `ideation.md`, `personas.md`, `prd.md`, and any file in `sdd/`. Confirm? (yes/no)". Without an explicit `yes`, abort. If confirmed, reset `newproject_progress` in `state.json` and proceed to brief collection. ### Option 3: Re-run from a specific agent Present the sub-menu with the 4 agents: ``` From which agent? [1] reversa-ideator (redo brainstorm) [2] reversa-researcher (redo personas) [3] reversa-drafter (redo PRD) [4] reversa-spec-sdd (redo SDD specs) ``` Before invoking, warn which artifacts will be overwritten from that point on and ask for `yes/no` confirmation. ### Option 4: Cancel Exit without changing anything. ## Brief collection If the user passed a free-form argument to `/reversa-new`, use it as the initial brief. Otherwise, ask: > "Hello ``. What do you want to build? Describe it in one sentence or a short paragraph." Save the brief in `_reversa_sdd/newproject-brief.md`: ```markdown # Initial brief, /reversa-new > Seal 🟡 PLANNED. Entry document for the Code New Project Agents team. **Date:** **User:** ## Original idea --- Generated by /reversa-new on ``` Atomic write (tempfile then rename), UTF-8 without BOM. Update `state.json#newproject_progress`: ```json { "newproject_progress": { "stage": "ideator", "started_at": "", "last_checkpoint_at": "", "completed_stages": [], "brief": "" } } ``` ## Running the pipeline For each agent in the pipeline: 1. Tell the user: "Starting **** — it will ." 2. Activate the corresponding skill. If the engine does not support direct activation by name, read the agent's `SKILL.md` and execute in the current context. 3. After the agent finishes and the user has responded CONTINUE, update `state.json#newproject_progress`: - `stage` to the name of the next agent - Add the just-completed agent to `completed_stages` - Update `last_checkpoint_at` 4. Confirm the next step with the user before proceeding. The sequence is fixed: | Order | Agent | Output | Next stage in state | |---|---|---|---| | 1 | reversa-ideator | `_reversa_sdd/ideation.md` | `researcher` | | 2 | reversa-researcher | `_reversa_sdd/personas.md` | `drafter` | | 3 | reversa-drafter | `_reversa_sdd/prd.md` | `spec-sdd` | | 4 | reversa-spec-sdd | `_reversa_sdd/sdd/.md` | `done` | ## Final handoff When `reversa-spec-sdd` finishes, update `stage` to `done` and display the final report: > ``, the `/reversa-new` pipeline is complete. Artifacts generated in `_reversa_sdd/`: > > - `newproject-brief.md`, original brief > - `ideation.md`, idea brainstorm > - `personas.md`, personas and journeys > - `prd.md`, product requirements document > - `sdd/*.md`, SDD specs per component, with automatic score > > All artifacts carry seal 🟡 (planned). Next step: run `/reversa-forward`, which will consume these artifacts and start the evolution cycle through to code. > > Type **CONTINUE** to start `/reversa-forward`, or pause here. If the engine allows it, activate `/reversa-forward` when the user responds CONTINUE. Otherwise, just guide them. ## Languages Respect `chat_language` and `doc_language` from `state.json`. Messages to the user in `chat_language`. Artifact content in `doc_language`. ## Context overflow If the context is running out between agents: 1. Confirm that the checkpoint in `state.json#newproject_progress` is saved. 2. Say: "``, I will pause here. The state is saved. Type `/reversa-new` in a new session to resume from where we left off." ## Absolute rule Never delete, modify, or overwrite pre-existing files in the user's project. Reversa writes ONLY to `.reversa/` and `_reversa_sdd/`. In re-execution options 2 or 3, only overwrite inside `_reversa_sdd/` after explicit confirmation. ## Final output Every transition between agents ends with: > Type **CONTINUE** to proceed with ``. Never advance automatically. The user decides each step.