I'm working on a system with the following moving parts: - Inputs: - Outputs: - Dependencies: - Failure modes I've noticed: (paste bullets, messy is fine) Task: Normalize this into a clear system model. Output requirements: 1. A concise system description (5–7 sentences) 2. A table of components with responsibility + owner 3. A list of hidden coupling risks 4. One diagram described in text that I could hand to an engineer or designer Constraints: - Do not suggest tools or vendors - Do not optimize yet - Favor clarity over completeness
Context: Here is how I currently do this task (inefficient, inconsistent, tribal knowledge): (paste steps, notes, screenshots descriptions, whatever) Goal: Turn this into a repeatable process that works even if I'm not available. Output: 1. A step-by-step process with clear entry and exit conditions 2. What information must be present before starting 3. Where automation or AI helps vs hurts 4. A short checklist version I could pin in a repo or Notion Rules: - Assume a small team - Avoid perfection - Optimize for resilience, not speed
Context: I'm considering the following decision: (decision + why now) Known constraints: - Time: - Money: - Team skillset: - Things I cannot change: Task: Pressure-test this decision. Output: - 3 strong reasons to proceed - 3 non-obvious reasons this could fail - What would make this decision obviously wrong in hindsight - A reversible version of this decision, if possible Tone: Direct, skeptical, and practical