Define changed behavior with a failing test, verify the failure reason, hand a bounded implementation contract to the code owner, then prove the fix with the affected suite and a boundary or failure case. Use for features, bug fixes, and behavior-preserving refactors where an automated test can provide useful…
Map user journeys, story maps, interaction flows, alternate paths, failure paths, release slices, and scenario-to-task links before decomposition. Use when a product workflow, UX flow, story map, persona path, acceptance scenario, or 09-user-story-map.md and 10-user-journeys.md artifact must be clarified before epics…
Design or review a web, mobile, desktop, game, CLI, voice, or conversational user experience. Use when a feature changes navigation, interaction, content, onboarding, or screen states. Produce information structure, flows, empty/loading/error/success behaviour, content guidance, accessibility requirements, design…