ado-tasks

Generates Azure DevOps task breakdowns from approved ICEA documents per architecture layer.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill ado-tasks-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ado-tasks
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/ado-tasks
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill ado-tasks-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an approved ICEA (Intent, Context, Examples, Acceptance Criteria) document into a complete, sprint-ready Azure DevOps task list is manual and error-prone — tasks get missed, layers get skipped, and estimates are inconsistent. This Skill automates that decomposition so every Acceptance Criterion maps to concrete tasks across every active layer. ## Core Features & Use Cases - Per-AC, per-layer task generation: Creates one task per Acceptance Criterion for each active layer (backend, frontend, middleware, database, QA, infra), with layers resolved from .claude/architecture/architecture.md or detected stack state. - ADO fallback fetch: When no ICEA file exists, it fetches the work item directly from the Azure DevOps REST API using a PAT, with corporate-network-safe curl flags and Node.js-based JSON parsing. - Structured planning output: Produces a summary table, full paste-ready task cards, an effort estimate summary, an ADO story description block, and a Definition of Ready checklist. - Use Case: A tech lead pastes an approved ICEA for story ADO #1847 and receives a complete task breakdown — frontend component tasks, backend endpoint tasks, DB migration, QA test cases, and effort estimates — ready to create in Azure DevOps before sprint planning. ## Quick Start Ask the assistant to break down ADO work item 1847 into tasks using the approved ICEA document.

Frequently Asked Questions about ado-tasks

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

FAQPage Schema
How do I break down a user story into Azure DevOps tasks?

Provide an approved ICEA document or an ADO work item ID, and the skill generates one task per Acceptance Criterion for each active layer — backend, frontend, middleware, database, QA, and infra. Output includes a summary table, full task cards, and effort estimates ready to paste into Azure DevOps.

How to fetch Azure DevOps work items with a PAT from the command line?

Set the AZURE_DEVOPS_PAT environment variable, build a Basic auth header with base64, then call the ADO work items REST API with curl. On corporate networks always include the --ssl-no-revoke and -4 flags to avoid silent connection failures.

Does this work with stacks other than .NET and Angular?

Yes, the task breakdown is stack-agnostic. Active layers are read from architecture.md or detected stack state, covering .NET, Spring Boot, FastAPI, Django, Flask, Node.js, Angular, and React, with tasks named in the project's actual framework.

Why does my Azure DevOps curl request return an empty response?

Empty responses on corporate networks are usually caused by missing curl flags. Certificate revocation checks are blocked by the proxy, requiring --ssl-no-revoke, and IPv6 is unreachable, requiring -4. Run curl with -v to see the full handshake for diagnosis.

What happens if no ICEA document exists for the work item?

The skill falls back to fetching the work item description and acceptance criteria directly from Azure DevOps and treats them as the ICEA content. It flags the output with a prompt to run the icea-feature skill to formalize the ICEA before the next sprint.