planning-before-code

仓库创建 2026年7月27日最近提交 1 天前SkillHot 收录 1 天前

▸ 精选理由

适合触及多文件的改动，减少盲改与回滚成本。

这个 Skill 做什么

把已批准的目标拆成可执行的小任务并标注精确文件路径与检查点。

把已批准的目标拆成可执行的小任务，每步标注精确的文件路径、变更点和检查点并按步骤执行、回报进度。适用于会改动多于两三处文件、需要估算或做里程碑的工作场景。好处是避免盲改代码，预先看到会影响哪些文件和如何验证，方便评审与分工。

▸ 展开 SKILL.md 英文原文

Turns an approved goal into an executable implementation plan of small tasks with exact file paths, then executes with checkpoints. Use when starting non-trivial work, when the user says plan, break down, roadmap, or estimate, or before touching more than 2-3 files.

开发编程计划先行任务分解路径精确检查点通用

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/Ludenox-GIT/portable-agent-skills/main/skills/planning-before-code/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/Ludenox-GIT/portable-agent-skills/main/skills/planning-before-code/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Planning Before Code

## When to use

Use when:
- The task will touch more than 2-3 files.
- The user says "plan", "break down", "roadmap", "estimate", or "how would you approach".
- You cannot list, right now and from memory, every file the change will touch. That inability IS the trigger.

Do NOT use when:
- Single-file, single-concern edit (typo, rename, one-line fix). Just do it.
- The user handed you an already-approved written plan. Skip to step 5 (Execute).
- Pure investigation or Q&A with no edits.

## Iron Law

**NO CODE BEFORE AN APPROVED WRITTEN PLAN for any task touching more than 2-3 files.**

Not a sketch in your head. Not "I'll formalize as I go." A written plan, shown to th

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有