web-feature-iteration

Web feature iteration during sprint planning involves assessing current capabilities, deciding the next actionable item, and updating WEB-TASKS.md. It keeps the active backlog between 3 to 5 items to focus on high-value tasks and drop low-priority ones.

Maintaining UI consistency during web feature iteration requires coordinating with guard skills. These skills enforce coherent UI and copy guidelines across new capabilities, ensuring the implemented features form a connected closed loop.

Yes, you need WEB-TASKS.md as the centralized entry point to coordinate agile feature iteration. It provides a unified tracking file to monitor the active backlog, replace completed items, and guide the execution of subsequent web capabilities.

The best way to handle backlog reduction for a web application team is to enforce a 3 to 5 item active backlog. This method prioritizes the most valuable tasks, removes completed ones immediately, and adds new items to maintain focus.