skills.rest
HypoxanthineOvO
HypoxanthineOvOCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reject

Reject pending Hypo-Workflow Cycle work with structured feedback and reopen the Cycle.

24|3|Updated Apr 22, 2026
Search Tags:#workflow#feedback#state-management#audit-trail#cycle#reject
One-click install
npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill reject-hypoxanthineovo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reject
Source: https://github.com/HypoxanthineOvO/Hypo-Workflow/tree/main/skills/reject
Command: npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill reject-hypoxanthineovo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reject pending Hypo-Workflow Cycle work with structured, auditable feedback and reopen the Cycle for revision.

Core Features & Use Cases

  • Structured rejection artifacts: writes rejection details to .pipeline/acceptance and creates a compact feedback reference for the Cycle.
  • Cycle/state updates: marks cycle.status as active and acceptance.state as rejected, with timestamps and feedback_ref to trace the decision.
  • Audit trails & recovery: appends derived refresh records to .pipeline/log.yaml and updates .pipeline/PROGRESS.md to reflect the rejection path; supports atomic submissions and rollback if refresh fails.

Quick Start

Invoke the /hw:reject command on a pending Cycle to apply structured feedback and reopen it for revision.

Frequently Asked Questions about reject

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

FAQPage Schema
How do I reject pending workflow cycle work with structured feedback?▼

To reject pending workflow cycle work, invoke the reject command on a pending cycle to write structured feedback to .pipeline/acceptance, update cycle and state metadata, and reopen the cycle for revision.

What happens to workflow cycle status when a rejection is submitted?▼

Submitting a rejection marks the cycle.status as active and acceptance.state as rejected, appending timestamps and a feedback reference to trace the decision and guide the next revision steps.

How does the rejection process maintain an audit trail for state management?▼

The rejection process maintains an audit trail by appending derived refresh records to .pipeline/log.yaml and updating .pipeline/PROGRESS.md to reflect the rejection path with atomic submissions and rollback support.

Can I rollback a cycle rejection if the state refresh fails?▼

Yes, the rejection process supports atomic submissions and rollback if the state refresh fails, ensuring your workflow cycle metadata and audit trails remain consistent and recoverable.

When should I use a formal rejection cycle instead of directly editing workflow state files?▼

Use a formal rejection cycle when pending work requires auditable feedback to guide revision, ensuring structured artifacts and state updates rather than manual edits to .pipeline/cycle.yaml and .pipeline/state.yaml.

Does the reject workflow require any specific cycle status to apply feedback?▼

Yes, the reject workflow applies when cycles are awaiting acceptance or in pending status, requiring formal feedback to formally reopen the cycle for subsequent revision.

Related Skills

Explore More Product & Management Skills→
HypoxanthineOvOHypoxanthineOvO
24

plan-extend

Append milestones to an active Cycle in a YAML workflow.

Community
Advanced
HypoxanthineOvOHypoxanthineOvO
24

accept

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

Community
Advanced
HypoxanthineOvOHypoxanthineOvO
24

skip

Skip the active pipeline prompt while preserving recoverable state.

Community
Intermediate
HypoxanthineOvOHypoxanthineOvO
24

plan-generate

Generates .pipeline config, prompts, and cycle metadata from an approved milestone plan.

Community
Advanced