hitl

Resolve ready-for-human GitHub issues by extracting pending decisions and requeueing delegable work.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill hitl-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hitl
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/engineering/hitl
Command: npx skills add https://github.com/reddb-io/red-skills --skill hitl-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous agent workflows stall when issues get parked in a ready-for-human queue waiting on maintainer decisions. This Skill drains that queue one issue at a time by extracting the pending decision, recording the maintainer's answer as auditable Human guidance, and moving the issue back to ready-for-agent when it becomes delegable. ## Core Features & Use Cases - Queue triage: Selects the highest-priority open ready-for-human issue (excluding type:spec planning artifacts) using priority bands and age ordering, with --issue and --skip overrides. - Decision extraction: Reads the issue body, blocker-state blocks, directive comments, and AFK envelopes with trust-based precedence rules to identify the single pending decision. - Atomic transitions: Applies state changes through the rs_dev MCP tools (requeue, hitl_resolve) rather than manual label flips, keeping the audit trail intact. - Use Case: An AFK agent parked issue #412 on a blocked:validation state. Run this Skill to surface the pending decision, interview the maintainer for the answer, refresh the Agent brief, and requeue the issue for autonomous execution. ## Quick Start Ask the agent to run the hitl workflow to pick the top ready-for-human issue, extract its pending decision, and requeue it once I answer.

Frequently Asked Questions about hitl

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

FAQPage Schema
How do I resolve a ready-for-human GitHub issue in an agent workflow?▼

Run the HITL workflow to select the highest-priority ready-for-human issue, extract its pending decision from the body or blocker-state block, get the maintainer's answer, then apply the requeue or hitl_resolve MCP tool to transition it atomically.

What is the difference between hitl and retake for blocked issues?▼

Use hitl when the pending human decision still needs to be extracted and answered through an interview. Use retake when the decision is already made and you only need to return a parked blocked:validation or blocked:spec issue to the queue.

Can I flip GitHub labels manually instead of using the MCP tools?▼

No. Manual label flips are forbidden because AFK preflight re-reads the active blocker-state block in the issue body and re-parks the issue. All transitions must go through the requeue or hitl_resolve tools so body, labels, and audit comments stay consistent.

Why does an issue keep returning to ready-for-human after I requeue it?▼

The issue body likely still contains an active Current blocker block with status blocked. The requeue tool archives that block into Resolved blockers; if you edited labels by hand, the stale blocker causes preflight to re-park the issue.

Does the HITL workflow select spec issues?▼

No. Issues carrying the type:spec label are planning artifacts and are always filtered out during selection. Only open, non-spec issues labelled ready-for-human are candidates.