start

Start Hypo-Workflow runs from local config and state files.

24|3|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill start-hypoxanthineovo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/HypoxanthineOvO/Hypo-Workflow/tree/main/skills/start
Command: npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill start-hypoxanthineovo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a reliable, local entry point to start Hypo-Workflow execution, resume unfinished runs, or trigger the first prompt in the pipeline.

Core Features & Use Cases

  • Orchestrates starting and progressing a local Hypo-Workflow run from project config and state, with safe lock management.
  • Supports resuming paused work, clean restarts, and immediate prompt execution to bootstrap pipelines.
  • Ensures auditable execution with state, logs, and provenance preserved across runs.

Quick Start

Initiate a local Hypo-Workflow run from the workspace using the start command to begin the pipeline.

Frequently Asked Questions about start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a local workflow pipeline execution from a project config?

To start a local workflow pipeline execution, initiate a run from your workspace, which reads .pipeline/config.yaml, validates configuration, and initializes state from .pipeline/state.yaml before processing.

Can I resume a paused workflow pipeline without losing previous state?

Yes, resuming a paused workflow pipeline restores state from .pipeline/state.yaml, allowing you to continue unfinished runs while preserving logs and provenance across sessions.

How does local orchestration manage concurrent pipeline locks?

Local orchestration manages pipeline locks by creating a structured lease with a .pipeline/.lock file, safely coordinating subagents and watchdog processes during execution.

What is the best way to bootstrap a pipeline with an initial prompt?

The best way to bootstrap a pipeline with an initial prompt is to trigger immediate execution, which initializes workflow state and coordinates subagents to process the entry point.

Do I need a specific local workspace setup to run workflow milestones?

You need a local workspace containing .pipeline/config.yaml to run workflow milestones, as configuration is loaded and validated locally before state initialization or execution occurs.

Why does my local pipeline run fail to initialize state correctly?

A local pipeline run may fail to initialize state if .pipeline/config.yaml is invalid or missing, preventing proper creation of .pipeline/state.yaml and the .pipeline/.lock lease.