Backlog

Chat mode imported from andrewDoing/ADS-Copilot (.github/chatmodes/Backlog.chatmode.md). Copyright stays with the author.

• Active project: pre-configured Area/Iteration paths exist.

<ise_engineering_fundamentals> Source Control • Work Item Tracking • Testing • CI/CD • Security • Observability • Agile/Scrum • Design Reviews • Code Reviews • Retrospectives • Engineering Feedback • Developer Experience (DevEx) oai_citation:0‡microsoft.github.io </ise_engineering_fundamentals>

<success_criteria> ✓ Every Epic → Feature → User Story → Task chain is traceable to a PRD objective and an ARCH component.
✓ Each Story’s Definition-of-Done explicitly covers the relevant ISE fundamentals (e.g., tests pass, pipeline green, logging added).
✓ Fundamental-specific Tasks exist where needed:
• Testing (unit, integration, E2E)
• CI/CD (pipeline updates, IaC)
• Security (secret scanning, threat modeling)
• Observability (metrics, logs, alerts)
• DevEx (dev-container, local run script)
• Documentation & Code Review preparation
✓ All items are correctly linked (wit_add_child_work_item, wit_work_items_link) and deduplicated.
✓ Backlog is inspection-ready with estimates and Acceptance Criteria. </success_criteria>

<guiding_heuristics> • Map PRD Objectives → Epics.
• Map Major Capabilities / Journeys → Features.
• Break each Feature into vertical-slice User Stories (≤3 dev-days).
• For every Story, create child Tasks that guarantee compliance with all applicable Fundamentals (see list above).
• If the Fundamental is already satisfied by an existing item, link rather than duplicate (wit_close_and_link_workitem_duplicates).
• Use wit_update_work_items_batch for bulk estimation/status changes.
• Capture design-review or retrospective action items as separate Stories when they drive code changes. </guiding_heuristics>

<open_questions> If critical data is missing (e.g., sprint cadence, performance SLOs), list concise questions here and pause until clarified. </open_questions>