Posted Mar 7, 2026
NPM CLI for Azure DevOps Boards
Scrum is genuinely good if used properly. But 99.999% of the time, from my personal experience, it's so misused it became quite a Scam to me.
If you feel like Homer Simpson backing into bushes right before sprint review, you are in the right place.
We’ve all been there. You’re very busy into actual work and then someone reminds you that your user stories need descriptions, acceptance criteria, t-shirt sizes, and business value fields filled in before tomorrow’s ceremony. The first time I heard “ceremony” I genuinely thought it was some kind of cult initiation.
Don’t get me wrong Scrum and the job of Scam Masters are genuinely good when used properly. But let’s be honest: most of us have seen it applied in ways that create more overhead than value, especially for architecture and infrastructure work where the real complexity lives in the system design, not in a Jira ticket template.
After nearly 20 years in the industry, I noticed something: the time spent writing and grooming work items is often disproportionate to the value they deliver. So inspired by git cli commands I built a tool to fix that.
adoboards is a CLI that pulls your Epics, Features, and User Stories from Azure DevOps Boards, organizes them locally as markdown files, and optionally lets AI handle the tedious writing for you.
You can quickly:
- Work from CLI with git-like commands (
clone,push,pull,status,diff,add) - Create work items from templates manually - no AI required, no corporate restrictions
- Optionally generate Epics, Features, and User Stories with Claude, ChatGPT, or Gemini - API keys safely stored in KeePass
- Let AI optimize existing items so you stop guessing “what do I pick for t-shirt size or business value?”
- Plan entire sprints with AI-powered capacity distribution
- Generate sprint reports from local state in seconds - ready to paste into emails or meetings
The CLI is fully functional without AI. Clone, edit, push, pull, status - all work with just your ADO PAT. AI features (gen, optimize, plan) are there when you want them, but never mandatory. If your org restricts API access, you lose nothing - the core workflow stands on its own.
Less time writing about work, more time doing the work.
If it saves you from one more sprint planning nightmare, it was worth building. Star the project on GitHub and if you want invite me for a coffe.