autoresearchAutonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, sel
relentless-devloopRun the app and test it with Chrome DevTools MCP as a headless browser. Navigates routes, clicks elements, fills forms, captures screenshots, checks console/network errors. Returns structured pass/fail results. Usable standalone or delegated from validator/implementer.
relentless-gatesRead a PRD's Agent Handoff block and generate failing TDD gate tests for each machine-verifiable acceptance criterion. Run between relentless-prd and relentless-implement.
relentless-implementRun relentless auto-continuing implementation on a PRD or task description. Launches headless Claude sessions in the background with progress tracking.
relentless-orchestrateMaster orchestrator for the relentless pipeline. Chains implement → validate → remediate → re-validate in a loop until all gates pass and live execution is clean. Owns the circuit breaker and escalation decisions. Follows RelentlessAgent principles — fresh context per phase, first-person progress su
relentless-prdGenerate a structured PRD through interactive discovery. Outputs a markdown file with testable acceptance criteria and an agent handoff block, ready for `relentless` auto-continuing implementation.
relentless-preflightPre-flight environment check before running the relentless pipeline. Validates dependencies, Databricks profile, ports, PRD structure, and writes _relentless_config.json for downstream phases.
relentless-remediateTargeted code fixer. Reads _validation_report.json, patches only auto-fixable errors with minimal changes. Never runs tests or validates its own fixes — the validator re-checks independently.
relentless-validatePure QA agent. Runs live execution validation after TDD gates pass. Uses Chrome DevTools (frontend) and Databricks CLI (backend) to detect integration failures. Reports structured errors — never writes code fixes.