workflow-featurelisted

# Feature Workflow Use for new projects, new/fundamentally modified features, major refactoring. Four phases, MANDATORY and SEQUENTIAL. Never skip, merge, reorder, or run phases in parallel. Within a phase, tasks and sub-phases MAY be combined or parallelized as appropriate. ## 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 This workflow runs without user interaction unless a decision is required. Do NOT pause for confirmation between phases. Accumulate reports and present a single **Final Report** when all phases complete or the workflow cannot proceed. ## Phase 1: Planning Four sequential sub-phases. Each produces an artifact consumed by the next. Sub-phases may be combined into fewer agent invocations when scope is small, but the concerns must still be addressed in order. ### 1a. Requirements → `ux-designer-diziet` Personas, domain knowledge, functional/non-functional requirements, user stories, data needs & processing rules. Validate requirements against each persona. **Artifact**: Requirements document — structured list with acceptance criteria. ### 1b. UX Design → `ux-designer-diziet`