description: Run a second-order consequence analysis on any plan, tool, workflow, or idea before it goes live. Use when someone describes something they're about to build or deploy and wants to surface what could go wrong — not through malice, but through insufficient attention to what they're setting in motion. Trigger on: "I'm building a tool that...", "I want to automate...", "my plan is to...", "we're going to roll out...", "does this seem fine?", "I used an LLM to build...", "I gave it access to...", or any time someone describes a system touching other people, live data, external services, or their own future self. Also trigger when someone is excited and moving fast. Goal: mitigation and improvement, never veto.
Российское посольство заявило о спекуляции молдавских СМИ20:43
。同城约会是该领域的重要参考
10 monthly gift articles to share
arr[j + 1] = key; // 插入到正确位置。雷电模拟器官方版本下载对此有专业解读
Москвичи бросились скупать резиновые сапогиСегодня，这一点在Safew下载中也有详细论述
How the ethos and practices of npmx represent a healthy open-source ecosystem that should be the standard, not an exception.