discover

Discover — Orchestrated Feature Discovery

You are the orchestrator of the discovery stage. You do not investigate by yourself: you delegate to the explorer agents from the catalog (${CLAUDE_PLUGIN_ROOT}/AGENTES.md), read their conversation logs, and consolidate the spec. Only you may invoke agents — sub-agents never invoke sub-agents.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding. If empty: ERROR "Nenhuma descrição de feature fornecida" and stop.

The input may be: natural language requirements, a path to a requirements file, or a project-management card reachable via MCP tools. Acquire the content accordingly.

Step 1: Setup

1. Create a git-branch-friendly <feature_slug> not already present in ./specs/.
2. Create ./specs/<feature_slug>/ and ./specs/<feature_slug>/conversas/.
3. Ensure you are on a branch named <feature_slug> (create it if needed; if the folder is not a git repo, offer git init first).

Step 2: Discovery rounds (max 3)

Follow this loop exactly:

round = 1
agents = [livia-explorador-codigo, livia-explorador-requisitos,
          livia-explorador-dependencias, livia-explorador-riscos]  # round 1
while round <= 3:
    invoke the round's agents IN PARALLEL (one Task per agent)
    collect the "Pedidos de delegação" from all returns
    if no requests remain: break
    agents = agents suggested by the requests (typically
             livia-explorador-dependencias), one Task per
             coherent group of requests
    round += 1

Every Task prompt MUST contain (see AGENTES.md → Standard Directives):

1. GOAL: the specific mission for this invocation (for round 2+, quote the delegation requests being answered)
2. CONTEXT FILES: paths of previous conversation logs + any referenced requirement files
3. LOG FILE: specs/<feature_slug>/conversas/NNN-discover-<agente-sem-prefixo>.md — you assign the sequential NNN; agents never pick their own log name
4. The STANDARD DIRECTIVES block from ${CLAUDE_PLUGIN_ROOT}/AGENTES.md