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.