hydraialisted

Use whenever the user asks to build, add, implement, or change a feature or functionality — or brings a user story or ticket to analyze, reports a bug or unexpected behavior, asks for a branch review, or wants a new app or service designed from scratch. Phase -1 triages the intent and routes it. Runs the complete non-negotiable development pipeline end to end — deep analysis and planning, sub-agent execution, and a double code-review loop — without asking the user which model, skill, or step to use. This is the default way features get built.
jdanigo/hydraia · ★ 8 · AI & Automation · score 78

Install: claude install-skill jdanigo/hydraia

# Hydraia — Agentic Development Pipeline This skill defines the ONLY approved way to build a feature. Run every phase, in order, automatically. **Never ask the user which model, skill, or reviewer to use — those decisions are already made here.** Never skip a phase. Never pause for "should I continue?" between phases. Announce once at the start: "Running the Hydraia pipeline." Then proceed silently through the phases, narrating at most one short line per phase. ## Phase -1 — Intent triage (before everything) Classify the request into exactly ONE route before any other guard runs. Explicit commands skip classification and force their route (`/hydraia:feature` → feature · `/hydraia:story` → user story · `/hydraia:plan` → feature, stopping after Phase 3 · `/hydraia:review` → review · `/hydraia:perf` → performance · `/hydraia:db` → performance, DB-shaped · `/hydraia:architect` → greenfield · `/hydraia:e2e` → E2E suite · `/hydraia:devops` → DevOps config · `/hydraia:observability` → instrumentation · `/hydraia:docs` → docs sync). Plain-language requests are classified by signals: | Intent | Signals | Route | |---|---|---| | Feature / change | "add / build / implement / change X" | Phases 0–6 as written below | | User story | "As a … I want … so that …", acceptance-criteria lists, ticket text or a Jira/PDF export | Run the **story-analysis** skill FIRST (interactive PO pass → story artifact with numbered ACs), then Phases 0–3 with that artifact as the primary design input; con