What problem does it solve? Teams often start coding features before requirements are agreed, causing rework, scope creep, and PR disputes. This Skill intercepts feature requests and produces a complete ICEA document (Intent, Context, Examples, Acceptance) plus a stack-specific Tech Spec, blocking code generation until the plan is explicitly approved. ## Core Features & Use Cases - Gated planning workflow: Collects ADO work item, release, and sprint identifiers, then enforces sequential plan, ICEA, and Tech Spec gates with SAVE commands before any implementation proceeds. - Stack-aware Tech Specs: Selects framework overlay templates (ASP.NET MVC + jQuery, ASP.NET Web API + Angular, Angular + Node.js) based on detected project stacks, producing files-changed tables, AC coverage matrices, and reviewer checklists. - Architecture-grounded drafting: Reads the codebase knowledge graph and architecture docs (deployment, security, data) to write precise acceptance criteria, flagging missing context with visible warnings instead of guessing. - Use Case: A developer says "add export to CSV on the report page, ADO #1847, R4, S14" and receives a reviewed plan, an approved ICEA saved to docs/Release4/Sprint14/UserStory1847/, and a Tech Spec with test cases — all before any code is written. ## Quick Start Ask the assistant to run /icea-feature with your ADO work item number, release, and sprint to draft a gated ICEA plan for your new feature.
