guide

Identify project state and propose the next Hypo-Workflow command path.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps new users understand the current project state and decide the next Hypo-Workflow command path, reducing setup time and confusion.

Core Features & Use Cases

  • Perceives project state from .pipeline artifacts and suggests a concise, executable command path.
  • Interprets user intent to route to the most appropriate starting flow, such as init, plan, or start.
  • Provides a safe, reversible first step by only proposing the initial command before execution.

Quick Start

Run the guide to receive a recommended first command path for Hypo-Workflow.

Frequently Asked Questions about guide

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

FAQPage Schema
How do I determine the current Hypo-Workflow state of my project?

To determine your current Hypo-Workflow state, this guide perceives existing `.pipeline` artifacts to identify the active cycle and suggests a concise, executable next command path.

What is the best way to route users to the correct Hypo-Workflow starting flow?

The best way to route users is by interpreting their intent against the project state, directing them to the most appropriate starting flow such as init, plan, or start.

How do I start onboarding a new project cycle with Hypo-Workflow safely?

To safely start onboarding a new cycle, the guide applies deterministic routing and safety checks to provide a reversible first step, proposing only the initial command before execution to minimize risk.

Does the Hypo-Workflow guide support both new and active project cycles?

Yes, the guide supports both new and active project cycles by evaluating the current state and routing users through the appropriate init, plan, or start flows based on their specific intent.

Why does the guide only propose the initial command before execution?

The guide proposes only the initial command before execution to ensure a safe, reversible first step during onboarding, minimizing potential risk and avoiding irreversible changes to the project state.