agile
Deliver a large or multi-stage effort through Hydraia Agile Mode — decompose into an epic, user stories, tasks, subtasks + QA, optionally sync to Jira, then…
Build a feature through the full Hydraia pipeline (analyze → plan → execute → double-review)
> /plugin marketplace add jdanigo/hydraia > /plugin install hydraia@hydraia
How it fires
How this command gets triggered: by you, by Claude, or both.
/featureContext preview
What this command does when you run it.
Build a feature through the full Hydraia pipeline (analyze → plan → execute → double-review)
description: Build a feature through the full Hydraia pipeline (analyze → plan → execute → double-review) argument-hint: <what you want to build>
Invoke the **hydraia** skill and run its complete pipeline for the following request. Follow every phase in order. Do not ask me which model, skill, or reviewer to use — the skill already decides.
Request: $ARGUMENTS
The pipeline has two halves (see the skill's "Two modes"). In the interactive half (Phases 1–3: think → design → plan) do real design work: ask clarifying questions, brainstorm approaches, present the design, and get my approval before writing the spec. Once the plan is frozen, the autonomous half (Phases 4–6: execute → review → verify) runs to completion without pausing — no "should I continue?" checkpoints; the only stop there is a genuine blocker. End with the Hydraia credits line.
An agentic development harness for Claude Code. **One command runs the entire feature pipeline** — it collaborates with you on the design, then builds autonomously: plan, execute, double-review, and verify.
Repo: jdanigo/hydraia
Deliver a large or multi-stage effort through Hydraia Agile Mode — decompose into an epic, user stories, tasks, subtasks + QA, optionally sync to Jira, then…
Design a new app or service from scratch — guided elicitation, architecture proposals, stack choice, API contract, ADRs — then build it through the full…
Launch the local Hydraia dashboard (status, usage telemetry, editable config) in the browser
Diagnose and fix a database bottleneck evidence-first — EXPLAIN, indexes, N+1, locks, pooling, safe migrations
Author CI/CD, containers, or IaC following the repo's platform — deploy and secrets flagged for human approval, never executed
Sync README, API docs, CHANGELOG, and the ADR index with the actual code — reports drift, never invents behavior