正在打开每日关注
正在打开每日关注
一套面向 Codex 的端到端提示词，强调并行分工、持续验证与最终闭环。
ok this one is stupidly good. try it on 5.6 sol extra high in codex! it plays straight into codex's new strengths, parallel subagents and computer use, and lets 5.6 sol carry a goal all the way to done. the prompt 👇 I have one complete task to push end to end: [your spec doc, or the full task in detail]. treat it as one end-to-end goal: 𝘁𝗮𝗸𝗲 𝘁𝗵𝗲 𝘄𝗵𝗼𝗹𝗲 𝗽𝗹𝗮𝗻 𝘁𝗼 𝗱𝗼𝗻𝗲, until architecture, implementation, tests, review and the final result all clear the bar. break the goal into independent parts, spawn as many parallel agents as it takes, and give each one its own goal with a clear deliverable, a verification method, and done criteria. then run it like an operator: schedule the agents in parallel, track progress, synthesize what comes back, resolve conflicts, keep implementing, verify live after every important step, review when it matters, commit when it's ready, and close with a final summary. verification must cover the real end-to-end path: browser and computer use, clicks, keyboard, whatever it takes. don't stop at partial progress unless you're blocked by missing credentials, destructive ambiguity, or conflicting requirements.
是什么 这是一段面向 Codex 的端到端任务编排提示词。它要求把规格文档或完整需求当作单一目标，持续推进架构、实现、测试、评审与最终交付，而非停留在局部进展。内容是纯观点与方法分享，价值在于代理执行流程的组织方式。
核心设计 方法包含三层：先拆解独立工作并行分派，再为每个子代理定义交付物、验证方法和完成标准，最后由主代理跟踪、汇总、冲突消解并继续实施。它还把浏览器、点击、键盘和计算机操作纳入关键步骤后的真实验证，形成“执行—检查—修正”的循环。
关键洞察 这实际上把提示词写成一份轻量执行协议，把目标、调度、状态、质量门槛和收尾串起来。对复杂研发任务而言，并行化可减少等待，明确验收条件则更容易合并多代理产出，也能降低“看似完成、实际不可用”的风险。
边界与风险 “尽可能多的代理”并非总能提速；共享文件、依赖和冲突会增加协调成本。计算机操作还依赖权限、凭证与稳定环境，提交代码或执行高风险变更应有明确边界。它不能替代需求澄清、架构判断和人工最终验收，遇到缺失信息或冲突要求应暂停。