gateway-bookkeeper

Tracks, reconciles, and audits Azure DevOps work items, sprints, and backlog hygiene.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/koala-man-64/helpful-scripts --skill gateway-bookkeeper-koala-man-64
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gateway-bookkeeper
Source: https://github.com/koala-man-64/helpful-scripts/tree/main/.claude/skills/gateway-bookkeeper
Command: npx skills add https://github.com/koala-man-64/helpful-scripts --skill gateway-bookkeeper-koala-man-64

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Azure DevOps backlogs drift out of sync with actual delivery work: orphaned tasks, missing estimates, stale items, and untracked repo changes make reporting unreliable. This Skill acts as an operational bookkeeper that keeps Epics, Features, User Stories, Tasks, and Bugs clean, current, and auditable across one or more Azure DevOps projects. ## Core Features & Use Cases - Work Item Tracking & Rollups: Reconstructs parent/child hierarchies, rolls up progress from Tasks to Epics, and detects orphaned, stale, or incomplete items using WIQL queries. - Sprint & Assignment Bookkeeping: Produces sprint health summaries, standup digests, carryover analysis, and per-assignee workload reports with risk flags. - Governed Writes: Creates and updates work items only through preview-and-confirm gates, enforcing required metadata such as StackRank, Story Points, repo tags, and agent-role description sections. - Use Case: Ask "Show me the current sprint health" to get completion counts, story point progress, blocked items, top risks, and cleanup recommendations with direct Azure DevOps links. ## Quick Start Ask the agent to show the current sprint health for your Azure DevOps project and it will query the active sprint and return a structured risk and completion summary.

Frequently Asked Questions about gateway-bookkeeper

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

FAQPage Schema
How do I track Azure DevOps work items across multiple repos?▼

The Skill resolves the Azure DevOps organization, project, and repo from git remotes, then creates or links Tasks and User Stories tagged with repo:<repo-slug> per touched repo. It rolls up progress from Tasks through Stories, Features, and Epics for cross-repo visibility.

How to generate a sprint health report in Azure DevOps?▼

Ask for the current sprint health and the Skill queries the active sprint via WIQL, then summarizes committed versus completed stories, story points, remaining work, blocked items, unassigned work, and top risks with direct work item links.

Can the Skill create or update Azure DevOps work items automatically?▼

Writes are gated by mode: read-only is default, confirm-before-write previews every change with previous and new values, and approved automation allows only pre-approved low-risk updates. It never deletes work items or bulk-updates without a preview.

What Azure DevOps process templates does it support?▼

It defaults to the Agile process with Epic, Feature, User Story, and Task hierarchy, using Microsoft.VSTS.Common.StackRank for ordering. For other templates it discovers valid states and backlog-ordering fields from live project metadata before writing.

Why does work item creation stop with ADO_TRACKING_BLOCKED?▼

Creation halts when required metadata cannot be resolved, such as a missing backlog-ordering field, absent Story Points estimate, or unverifiable agent-role and repo-scope description sections. The blocker message names the exact missing evidence and smallest fix.

What tools does it use to access Azure DevOps?▼

It prefers MCP or connector tools for work items, repos, and builds, falling back to Azure CLI commands like az boards and az devops, then the REST API with approved auth. Manual bookkeeping updates are a last-resort temporary fallback.