Objective
Create two new documentation pages covering work-queue and batch operation patterns for agentic workflows.
Context
Issue #22001 has been open since March 2026. The docs/src/content/docs/patterns/ directory contains daily-ops.md, issue-ops.md, and task-ops.md but has no coverage for work-queue or batch processing patterns — a common agentic use case.
Files to Create
docs/src/content/docs/patterns/workqueue-ops.md — work-queue patternsdocs/src/content/docs/patterns/batch-ops.md — batch operation patterns
Update the patterns index/sidebar if one exists.
Approach
workqueue-ops.md — Work Queue Operations
Document approaches for processing a queue of work items:
- Issue checklist as queue: use GitHub issue checkboxes as a simple work queue; agent checks off items as it processes them
- Sub-issues as queue: create sub-issues per work item; process open ones, close when done
- Cache-memory queue: store queue state in cache-memory JSON, process items across runs
- Discussion-based queue: use GitHub Discussions to track pending work
Include: when to use each approach, a complete workflow example (frontmatter + prompt), and caveats (concurrency, idempotency).
batch-ops.md — Batch Operations
Document strategies for processing large batches:
- Chunked processing: split work into pages/batches using
GITHUB_RUN_NUMBER or timestamps
- Fan-out with matrix: use GitHub Actions matrix to parallelize batch jobs
- Rate-limit-aware batching: throttle API calls in batch workflows
- Result aggregation: collect results from batch runs back into a summary issue or report
Include: when to use batch vs sequential processing, error handling (partial failures), and a complete example for a real-world scenario (e.g., updating labels across 100+ issues).
Acceptance Criteria
Generated by Plan Command for issue #25041 · ● 360.6K · ◷
Objective
Create two new documentation pages covering work-queue and batch operation patterns for agentic workflows.
Context
Issue #22001 has been open since March 2026. The
docs/src/content/docs/patterns/directory containsdaily-ops.md,issue-ops.md, andtask-ops.mdbut has no coverage for work-queue or batch processing patterns — a common agentic use case.Files to Create
docs/src/content/docs/patterns/workqueue-ops.md— work-queue patternsdocs/src/content/docs/patterns/batch-ops.md— batch operation patternsUpdate the patterns index/sidebar if one exists.
Approach
workqueue-ops.md— Work Queue OperationsDocument approaches for processing a queue of work items:
Include: when to use each approach, a complete workflow example (frontmatter + prompt), and caveats (concurrency, idempotency).
batch-ops.md— Batch OperationsDocument strategies for processing large batches:
GITHUB_RUN_NUMBERor timestampsInclude: when to use batch vs sequential processing, error handling (partial failures), and a complete example for a real-world scenario (e.g., updating labels across 100+ issues).
Acceptance Criteria
workqueue-ops.mdis created and covers at least 3 queue strategies with examplesbatch-ops.mdis created and covers at least 3 batch strategies with examplesworkqueue-ops.md,batch-ops.md, and related pages (task-ops.md,cache-memory.md,repo-memory.md)Related to [Daily Report] Documentation Quality Report — April 7, 2026 #25041