devlisted

Follow CLAUDE.md rules. ## Ultra Think Strategy Ultra think before each phase transition: - After exploration results: reflect on completeness before planning - Before implementation: consider edge cases, patterns to follow, potential issues - After validation: ensure the approach aligns with user intent --- ## 1. UNDERSTAND - Read spec: `$ARGUMENTS.spec` - Identify phase: `$ARGUMENTS.phase` - Phases completed: `$ARGUMENTS.done` - Extract from phase description: - **Scope**: backend / frontend / both - **Files** to create/modify - **Libraries** needed --- ## 2. EXPLORE (PARALLEL) Launch agents based on detected scope (single message, parallel execution): | Scope | Agents | |-------|--------| | backend | explore-codebase (backend/), explore-db (dev) | | frontend | explore-codebase (frontend/src/) | | both | All above | Add explore-docs for any external libraries mentioned. --- ## 2.5 POST-EXPLORATION CHECK After agents return, verify completeness: 1. Database info needed but missing? -> launch explore-db 2. Library docs needed but missing? -> launch explore-docs 3. Similar patterns not found? -> additional explore-codebase --- ## 3. SHOW PLAN Display enriched plan: ```markdown ## Phase $ARGUMENTS.phase ### Files to Create - `path/file` - [purpose] ### Files to Modify - `path/file:XX` - [what to change] ### Patterns to Reuse (from exploration) - [existing code patterns found] ### Order Backend: Domain -> Application -> Infrastructure -> Presentation F