workflow-simplifiedlisted

# Simplified Workflow Use for bug fixes, small changes (≤200 lines), small local refactorings. Same mandatory phase order as workflow-feature, lighter ceremony. Phases are SEQUENTIAL — never skip, merge, reorder, or run phases in parallel. Within a phase, tasks and sub-phases may be combined or parallelized. ## Before You Start Search project and global memories for relevant context before planning or dispatching agents: 1. `search_memories(query="<topic>", project="<repo>")` — discover what past sessions learned about this area 2. `get_memories(memory_id="<id>")` — read full details of relevant memories found in step 1 These are MCP tools on the MemCan server. Use them if available. Skip silently if not. ## Unattended Operation Runs without user interaction unless a decision is required. Accumulate reports and present a single **Final Report** when all phases complete. ## Phase 1: Planning Lighter than workflow-feature — sub-phases may be combined into fewer agent invocations for small scope, but the concerns must still be addressed in order. ### 1a. Requirements + UX Design → `ux-designer-diziet` Understand the problem, gather domain knowledge. For bug fixes: reproduce, identify root cause. For small features: requirements, user journey, DX impact. **Artifact**: Brief requirements + UX notes. ### 1b. Test Case Specification → `qa-engineer-marvin` Write test case SPECIFICATIONS (not code) covering the change. Each test case: description, expected outcome, requi