正在打开每日关注
正在打开每日关注
主张用带交付标准的并行工作单元驱动 Agent 任务，持续真实验证并以评审收尾。
𝟭. 𝗽𝗮𝗿𝗮𝗹𝗹𝗲𝗹 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 𝗴𝗼𝗮𝗹 task: {your task}. write yourself a full end-to-end goal first, then keep going until the architecture and the result both meet the bar. split: break that goal into independent pieces and run in parallel only as far as the work genuinely allows. every worker's goal carries its own deliverable, how to verify it, what counts as done, and which files it may touch. after every meaningful step: test the real thing for real, full end to end, plus computer use, browser, keystrokes, whatever it needs. auto review, then commit, then write progress somewhere sensible in the project. finish: one dedicated review pass over everything. done = production grade, a real user can walk in and use it. swap out {your task} and go. new feature, refactor, all the same. tip: don't hardcode the progress path. tell it to write somewhere sensible and it finds the spot on its own. rule: two workers that write files get 𝗼𝗻𝗲 𝘄𝗼𝗿𝗸𝘁𝗿𝗲𝗲 𝗲𝗮𝗰𝗵. sharing a checkout collides on files and on the git index. read-only workers can share. this is the goal wrapper. everything below runs through it. drop a task into the {your task} slot and it runs end to end.
是什么 这是一套给 Agent 任务套上的端到端目标包装器：先写清最终目标，再把任务拆成可独立交付的工作单元，允许并行推进，最后统一评审，并以真实用户可用作为完成定义。它不是某个软件框架，而是编排、验收和协作纪律的组合方法。
核心设计 关键是同时声明每个 worker 的目标、交付物、验证方式、完成条件和可修改文件，降低并行协作中的边界模糊；写文件的 worker 使用独立 worktree，避免 checkout 与 Git index 冲突。每个有意义的步骤都要求端到端测试、浏览器或计算机操作验证、自动评审、提交和进度记录，形成可追踪闭环。
关键洞察 并行不等于盲目拆分，只有真正独立的工作才适合并发；done 也不等于代码生成成功，而是架构与结果都达到生产级，并能被真实用户走通。它把 Agent 从一次性回答器推向具备计划、执行、验证和收尾能力的工程协作者。
边界与风险 这套规则偏流程治理，不能替代领域建模、测试设计或人工判断；频繁提交和全链路验证可能增加成本，且并行度受文件耦合限制。若目标本身模糊、验证脚本不足，包装器仍可能把低质量结果流程化。