keel-work-block

Process GitHub issue queues through structured work blocks with operator control.

4|Updated May 23, 2026

Search Tags:#workflow #project management #issue tracking #work block #operator guided

Ready to run

npx skills add https://github.com/berkayturanci/keel --skill keel-work-block

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keel-work-block
Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-work-block
Command: npx skills add https://github.com/berkayturanci/keel --skill keel-work-block

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines multi-issue workflow processing, enabling a structured approach to work block management, while providing operator oversight and control.

Core Features & Use Cases

Controlled Workflow Execution: Facilitates sequential processing of issues in a queue with operator-intervention points.
Issue Isolation: Isolates work on each issue, ensuring clean separation between tasks.
Operator-Driven: Allows an operator to pause, cancel, or alter workflow progress during the run.

Quick Start

Activate the 'keel work-block' skill by executing the command /keel:work-block with the necessary arguments.

Frequently Asked Questions about keel-work-block

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

FAQPage Schema

How do I process issue queues with operator-guided work blocks in GitHub?▼

Processing issue queues with operator-guided work blocks involves sequentially executing tasks while allowing an operator to pause, cancel, or alter progress. This workflow requires a valid project.yaml configuration file within the GitHub Issue tracking environment.

What is an operator-guided work block for multi-step workflows?▼

An operator-guided work block is a structured execution process for issue queues that isolates individual tasks and provides operator-intervention points. It ensures clean separation between issues during multi-step workflow processing.

Do I need a project.yaml configuration file to track issues sequentially?▼

Yes, a valid project.yaml configuration file is required to track issues sequentially. The workflow operates within the GitHub Issue tracking environment and relies on this file to process queues through controlled work blocks.

Can I pause or cancel workflow progress during issue tracking?▼

Yes, operator-driven control allows you to pause, cancel, or alter workflow progress during an active run. This ensures controlled progression and provides oversight when processing multi-issue queues.

How do I start a work block for issue queue management?▼

To start a work block for issue queue management, execute the command /keel:work-block with the necessary arguments. This activates the skill and begins processing your GitHub issue queue sequentially.

When do I need controlled workflow execution for issue queues?▼

Controlled workflow execution is needed when processing multi-issue queues requires clean task isolation and operator oversight. It is ideal for multi-step workflows where decisions must be made during progression.