Workflow

Prompt

You are advising a solo founder building a mobile-first private club poker universe. Project core: - AAA-feel card interaction - invite-only club society - AI session/world layer - gangster luxury / old money atmosphere - psychological pressure - web admin system for club operators - 2D presentation is acceptable if the feel is premium Important truth: This is NOT just a poker app. The product wins only if feel, club structure, retention, and atmosphere stay aligned. Current state: - Backend can be handled separately - Frontend feel and workflow orchestration are the priority - First successful RN card swipe prototype baseline already exists - Founder works as the final decision-maker - Multiple AIs and tools are available, but context fragmentation is a risk What I need from you: Design the BEST practical workflow for running this project with multiple AI models and tools without losing context, direction, or quality. Focus on: 1. How to organize decision-making 2. How to collect answers from multiple models 3. How to compare and summarize them without sycophancy 4. How to preserve a single source of truth 5. How to move from idea -> verdict -> implementation -> proof 6. How to prevent feature creep 7. How to keep “feel-first” from being buried under system/process 8. How to assign roles across models/tools 9. How to automate repetitive workflow safely 10. What should stay manual under founder control Constraints: - Solo-founder control must remain - AI suggestions are not truth unless founder locks them - The workflow must stay simple enough to run daily - The workflow must support repeated short decision cycles - The workflow must protect premium card feel above all - Avoid generic startup/process answers Output format: Give a concrete operating system with these sections: A. Core principle B. Source of truth structure C. Daily workflow loop D. Multi-model polling method E. Decision protocol F. Automation opportunities G. Hard boundaries / what must not be automated H. Top 5 failure risks I. Recommended minimal stack J. First 7 days execution plan Be direct. Do not flatter. Do not give vague options unless necessary. If something is risky or wrong, say it clearly.