organize-work-items

Group GitHub issues into work units by semantic similarity and code footprints.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/strawgate/agent-skills --skill organize-work-items
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organize-work-items
Source: https://github.com/strawgate/agent-skills/tree/main/organize-work-items
Command: npx skills add https://github.com/strawgate/agent-skills --skill organize-work-items

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of fragmented issue tracking by grouping related tasks into cohesive, manageable batches that are optimized for a single AI coding agent run.

Core Features & Use Cases

  • Semantic Batching: Uses similarity analysis to identify related bugs, docs, and refactors that share a common code footprint.
  • Scheduling Layer: Creates a dedicated work-unit layer that sits above your existing issue tree, ensuring clear execution paths without disrupting product intent.
  • Use Case: When a repository has dozens of scattered issues, use this skill to bundle them into a single work-unit ticket that covers a specific subsystem, ensuring the agent can complete the entire batch in one focused session.

Quick Start

Use the organize-work-items skill to analyze the strawgate/agent-skills repository and generate a new work unit for the pipeline subsystem.

Frequently Asked Questions about organize-work-items

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

FAQPage Schema
How do I batch GitHub issues into work units for an AI coding agent?

Batch GitHub issues into agent-ready work units by using semantic similarity analysis and shared code footprints to group related tasks into cohesive, manageable batches optimized for a single AI agent run.

What is semantic batching for GitHub issue tracking?

Semantic batching is the process of analyzing GitHub issues by similarity and shared code footprint to identify related bugs, docs, and refactors, bundling them into a single work-unit ticket for a specific subsystem.

Do I need Python and GitHub CLI to group repository issues automatically?

Yes, you need Python3 and GitHub CLI installed to group repository issues automatically, as the skill uses Python for data processing and similarity indexing alongside the GitHub CLI for issue access.

Can I create a scheduling layer above my existing GitHub issue tree without disrupting product intent?

Yes, you can create a dedicated work-unit scheduling layer that sits above your existing GitHub issue tree, ensuring clear execution paths for agent workflows without disrupting the original product intent.

What's the best way to organize scattered repository issues for automated agent workflows?

The best way to organize scattered repository issues for automated agent workflows is to analyze them for semantic similarity and bundle related tasks into a focused work-unit ticket covering a specific subsystem for one execution session.

Why group related bugs and refactors into a single work-unit ticket instead of handling them individually?

Grouping related bugs and refactors into a single work-unit ticket solves fragmented issue tracking by ensuring the AI coding agent can complete the entire batch of shared code footprint tasks in one focused session.