Here is a possible breakdown of 10 workdays for tackling a design feature:

Day 1-2: Research and ideation During these two days, the team should understand the epic/task brief. Conduct research on the user's needs and preferences. They should also ideate and brainstorm different design solutions that could solve the problem. Ideally on a Wednesday, the PO should check in with the design team, or attend the design sync and see progress made so far.

Day 3: Design Sync & Feedback Ideally on a Wednesday, the PO should check in with the design team, or attend the design sync and see progress made so far. The design team should showcase rough sketches of the idea and how they plan to tackle it. Gather input/feedback and reflect in wireframes.

Day 4-5: Sketching and wireframing During these two days, the team should begin to sketch out their design ideas and create basic wireframes. This helps them to visualize how the design will work and identify any potential issues. There should be an end-of-the-week presentation on what has been done so far and wireframes. Either through sharing of links or live video call presentation.

Day 6: User testing, Stakeholder engagement, and feedback During these two days, the team should conduct user testing on their wireframes to gather feedback, from customers, new users, devs, consultants, PM, etc. As much that can be gotten. However, arrangements for this should happen a week before. This feedback can be used to refine the design further.

Day 7-9: Iteration, Refinement, Finalization During these 3 days, the team should iterate on their design based on the feedback they received from user testing. They should focus on making improvements to the design and addressing any issues that were identified. They should account for all screen breakpoints, components, and style guide alignment ahead of handoff. Move designs speedily to Axure.

Day 10: Handoff & Sign Off On the final day, the UX team should handoff designs to the development team. The UX team should also communicate to the PO and PM and have the ticket signed off and closed.

Of course, the exact breakdown of tasks will depend on the complexity of the design feature and the specific needs of the project. However, this general framework can be used as a starting point for tackling a design feature over a 10-day period.