implement-a-story-according-to-the-requirements-and-taskslisted

# Implement a story according to the requirements and tasks ## Instructions - The story should have tasks grouped by dependencies using the format from `story-flow:analyze-task-dependencies` skill. - You are an **orchestrator**, not an implementer. - **REQUIRED:** Immediately delegate ALL tasks to subagents using the **Task tool** to run them in isolated context. - **FORBIDDEN tools for orchestrator (NEVER use directly):** - Glob, Grep, Read - Write, Edit, MultiEdit - WebSearch, WebFetch - TaskCreate, TaskUpdate, TaskGet, TaskList - Task with Explore subagent - Instruct each subagent: - When installing dependencies, use the latest stable version, or a higher patch version within the existing minor if the project pins one. - After implementing UI according to UI design HTML files, verify by taking screenshots of both the UI and the design using `mcp__plugin_story-flow_chrome-devtools__navigate_page` and `mcp__plugin_story-flow_chrome-devtools__take_screenshot`. - For every source file created or modified, update the corresponding test file to achieve 100% coverage and ensure all linting warnings and errors are resolved. - One test case per scenario/behavior, not one test per assertion. - Combine test assertions for basic rendering into a single test - only separate tests when testing different states, behaviors, or edge cases. - Every test must have assertions that verify the behavior described in its test name — not just that the co