Development
Command
/resume
Resume an interrupted Hydraia pipeline from the last incomplete phase
> /plugin marketplace add jdanigo/hydraia> /plugin install hydraia@hydraia
Command definition
resume.mddescription: Resume an interrupted Hydraia pipeline from the last incomplete phase
argument-hint: [optional run-log name; defaults to the most recent]
Invoke the **hydraia** skill in resume mode.
0. Resolve the artifacts base first (in-repo `docs/hydraia/` or the external dir the user chose at the storage gate) and inherit that run's **storage location** and **auto-commit** choice from the run log if recorded; if neither is recorded, re-run the Storage & commit gate. Every `docs/hydraia/...` path below is relative to the resolved base. 1. Find the run log: if $ARGUMENTS names one, use `<artifacts base>/runs/$ARGUMENTS`; otherwise use the most recently modified file in `<artifacts base>/runs/`. 2. Read it to recover the original request, the linked plan under `docs/hydraia/plans/`, and the phase checklist. Do NOT re-plan — reuse the frozen plan and spec. Also recover the recorded **run-controls** — execution routing (Balanced/Economy/Max-quality/Hand-off), review depth, summary depth, and E2E strategy — and honor them for the remaining phases. If the run stopped at Phase 3 (a `plan`/`story` route or Hand-off) and no routing/E2E choice was recorded, run the Phase-3 run-controls picker ONCE now — before entering the autonomous half — so execution proceeds without pausing afterward.
2a. **Agile Mode run?** If an epic exists under `<artifacts base>/epics/<slug>/` with a `sprint-status.yaml`, this is an Agile run. Do NOT re-decompose — reuse the frozen tree (`epic.md`, `epic-context.md`, `stories.yaml`, the per-story files). Read `sprint-status.yaml` to find `current` and its `phase`, and continue `phases/agile-orchestrator.md` from that story's first incomplete phase, honoring each story's recorded `tier` and `routing` and the epic's Jira target. Re-sync Jira (`phases/jira-sync.md`) for any story whose local `status` advanced while Jira was unreachable. Tier-L / risky stories still pause for approval on resume. 3. Continue the pipeline from the FIRST unchecked phase, obeying the continuous-execution rule (do not stop until the plan is complete or a genuine blocker appears). 4. Update the run log's checkboxes as phases complete. 5. On completion, print the credits line, exactly: `— Harness By José Daniel Garcés Ospina | Spec Drive Design First —`
Read more
description: Resume an interrupted Hydraia pipeline from the last incomplete phase argument-hint: [optional run-log name; defaults to the most recent]
Invoke the **hydraia** skill in resume mode.
0. Resolve the artifacts base first (in-repo `docs/hydraia/` or the external dir the user chose at the storage gate) and inherit that run's **storage location** and **auto-commit** choice from the run log if recorded; if neither is recorded, re-run the Storage & commit gate. Every `docs/hydraia/...` path below is relative to the resolved base. 1. Find the run log: if $ARGUMENTS names one, use `<artifacts base>/runs/$ARGUMENTS`; otherwise use the most recently modified file in `<artifacts base>/runs/`. 2. Read it to recover the original request, the linked plan under `docs/hydraia/plans/`, and the phase checklist. Do NOT re-plan — reuse the frozen plan and spec. Also recover the recorded **run-controls** — execution routing (Balanced/Economy/Max-quality/Hand-off), review depth, summary depth, and E2E strategy — and honor them for the remaining phases. If the run stopped at Phase 3 (a `plan`/`story` route or Hand-off) and no routing/E2E choice was recorded, run the Phase-3 run-controls picker ONCE now — before entering the autonomous half — so execution proceeds without pausing afterward.
2a. **Agile Mode run?** If an epic exists under `<artifacts base>/epics/<slug>/` with a `sprint-status.yaml`, this is an Agile run. Do NOT re-decompose — reuse the frozen tree (`epic.md`, `epic-context.md`, `stories.yaml`, the per-story files). Read `sprint-status.yaml` to find `current` and its `phase`, and continue `phases/agile-orchestrator.md` from that story's first incomplete phase, honoring each story's recorded `tier` and `routing` and the epic's Jira target. Re-sync Jira (`phases/jira-sync.md`) for any story whose local `status` advanced while Jira was unreachable. Tier-L / risky stories still pause for approval on resume. 3. Continue the pipeline from the FIRST unchecked phase, obeying the continuous-execution rule (do not stop until the plan is complete or a genuine blocker appears). 4. Update the run log's checkboxes as phases complete. 5. On completion, print the credits line, exactly: `— Harness By José Daniel Garcés Ospina | Spec Drive Design First —`
Stats
8
Stars
0
Forks
Maintained
Maintenance
JavaScript
Language
MIT
License
Last commit
Created
Ships withhydraia
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.
852 skills27 agents
Stars on GitHub
Momentum
- stars in total
- 8
More commands from other plugins.
Auto-invoked
Auto-invoked
build
CommandImplement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
@addyosmaniInstall Command