validationlisted

# $validation — Full Validation Phase Orchestrator **YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.** ## DAG — Execute This Sequentially ``` mkdir -p .agents/rpi detect complexity from execution-packet or --complexity flag (default: standard) detect ao CLI availability ``` ### Step 0: Load Prior Validation Context Before running the validation pipeline, pull relevant learnings from prior reviews: ```bash if command -v ao &>/dev/null; then ao lookup --query "<epic or goal context> validation review patterns" --limit 5 2>/dev/null || true fi ``` **Apply retrieved knowledge (mandatory when results returned):** If learnings are returned, do NOT just load them as passive context. For each returned item: 1. Check: does this learning apply to the current validation scope? (answer yes/no) 2. If yes: include it as a `known_risk` — what pattern does it warn about? does the code exhibit it? 3. Cite applicable learnings by filename when they influence a validation finding After applying, record each citation: ```bash ao metrics cite "<learning-path>" --type applied 2>/dev/null || true ``` Skip silently if ao is unavailable or returns no results. **Run every step in order. Do not stop between steps.** ``` STEP 1 ── Skill(skill="vibe", args="recent [--quick]") Use --quick for fast/standard. Full council for full. PASS/WARN? → continue FAIL? → write summary, output <promise>FAIL</promise>, stop