workflow-methodologylisted

## Step 0 - figure out what we're building (do this FIRST, before anything else) Look at what was passed in: `$ARGUMENTS` - If it already clearly states a project name, a real description of what to build, AND the platform/stack (e.g. "React Native non-Expo", "Python backend service", "LLM agent pipeline"), confirm your understanding back to me in one or two sentences and proceed to the section below. - If any of those three are missing or vague, **stop and ask me**: 1. What are we building? (be as comprehensive as you want me to be - the more detail, the better Phase 1 will be) 2. What platform/stack is this for? (e.g. mobile app - React Native/Expo/native, backend service, LLM/agent pipeline, web frontend, CLI tool, etc. - this changes what Phase 1's library/service analysis actually looks like) 3. What short project name should identify it? (used for the `.workflow/<slug>/` folder, e.g. `article-quality-widget`) Do not guess or invent a feature, and do not assume a default platform/stack (do not assume React Native or anything else) to analyze. Do not proceed past this point until I've answered. Also ask (can be part of the same question round): what services/infra already exist in this project that Phase 1 should treat as "Existing Services" (e.g. a specific backend, database, auth provider, third-party APIs already wired up) - versus what's clearly new and would count as "Proposed Services". If I say I'm not sure or there's nothing e