better-coding-plan
减少返工，适用于复杂功能与架构变更。
在编码前产出设计文档与精确任务列表，规范实现前的决策过程。
在动手写代码前把想法变成可执行的设计文档和有序任务清单：通过问答澄清需求、探索 2–3 种方案、画出架构并拆成带 TDD 步骤的细粒度任务，还会给出验证计划和依赖顺序。适用于新特性、重构或复杂系统改动的规划阶段，能让实现阶段按部就班。特点是只产出文档和任务，不写生产代码，降低设计风险。
▸ 展开 SKILL.md 英文原文
Plan, design, and spec any non-trivial feature, refactor, or system change before code is written. MUST be used when planning a feature, designing an architecture, evaluating approaches, breaking down complex work, or creating a spec — even if the user does not explicitly say plan. Runs Socratic clarification, 2-3 approach exploration, architecture design, bite-sized task breakdown with TDD steps, and a verification plan; produces a design document plus a dependency-ordered task list for implementation. Writes documents only, never production code. Trigger: /better-coding-plan
帮我安装这个 skill：https://raw.githubusercontent.com/janschachtschabel/better-coding-skills/main/skills/better-coding-plan/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/janschachtschabel/better-coding-skills/main/skills/better-coding-plan/SKILL.md"# Better Coding Plan The skill between "I have an idea" and "I'm writing code." A capable agent jumps straight to implementation, produces 400 lines that almost work, and discovers the real requirements three commits later. This skill forces the design conversation first. **Primary objective:** produce a design document and a task list precise enough that `better-coding-workflow` can execute each task without rediscovering the requirements. The plan is the contract between intent and implementation. --- ## Activation Begin the first response after loading with exactly this line: ▸ better-coding-plan active — design first, then plan, then build Emit it once, then proceed. Do not repeat