accept

Validate Hypo-Workflow cycle readiness and enforce required worker evidence before acceptance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a gatekeeper for Hypo-Workflow cycles, validating readiness and enforcing evidence requirements before final acceptance.

Core Features & Use Cases

  • Validate cycle readiness and ensure all required evidence is present before acceptance.
  • Enforce worker lifecycle constraints and audit-ready updates to cycle state.
  • Provide guardrails to prevent acceptance when critical conditions are missing or inconsistent.
  • Use Case: When a Cycle has pending acceptance but missing key test or review artifacts, automatically halt and surface remediation steps.

Quick Start

Review the current cycle's readiness, ensure all required worker evidence is present, then approve the cycle to move to the next stage.

Frequently Asked Questions about accept

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

FAQPage Schema
How do I enforce workflow acceptance criteria before completing a cycle?

To prevent premature cycle completion, enforce worker lifecycle constraints and audit readiness before final acceptance. This gatekeeper halts the process and surfaces remediation steps when critical evidence is missing.

What happens if a cycle is pending acceptance but missing required evidence?

When a cycle is pending acceptance with missing evidence, the validation process automatically halts. It then surfaces specific remediation steps to ensure required test or review artifacts are provided before approval.

How does cycle acceptance governance handle worker lifecycle constraints?

Cycle acceptance governance enforces worker lifecycle constraints by validating required evidence across all workers. It records acceptance decisions and updates the cycle state to maintain audit readiness.

Can I use workflow guardrails to halt acceptance when critical conditions are inconsistent?

Yes, you can use workflow guardrails to halt acceptance when critical conditions are missing or inconsistent. These guardrails validate cycle readiness and enforce evidence requirements before final approval.

What is the step-by-step process to validate and approve a workflow cycle?

To validate and approve a workflow cycle, review the current cycle readiness, ensure all required worker evidence is present, then approve the cycle to move it to the next lifecycle stage.