to-issues

仓库创建 2026年6月26日最近提交 22 天前SkillHot 收录 22 天前

▸ 精选理由

把宏观需求分解为可执行工单，极大减少产品与开发的沟通成本。

这个 Skill 做什么

将对齐后的功能拆分为一组可直接提交的、独立的 GitHub issue。

把已经对齐好的功能拆成一组小而独立的 GitHub issue，每条都能让新的 agent 会话从零把它做完。常在 /vision-align 之后或有人说“把计划拆成工单”时用，目标是把大任务分成可交付、互不依赖的工作单元。重点是以“单次 agent 会话能完成”为单位划分，同时明确边界、归属和执行顺序，减少模糊交接。

▸ 展开 SKILL.md 英文原文

Turn an aligned feature into a set of small, self-contained GitHub issues, each buildable cold by a fresh agent session. Use right after a `/vision-align` session, or when asked to "split this into issues", "break this plan into tickets", or "decompose this work". Not for shaping the feature itself — that's `/vision-align` — and not for building an issue, which is `/implement`.

开发编程任务拆解GitHub工程管理通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/Svendsys/agent-skills/master/skills/to-issues/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/Svendsys/agent-skills/master/skills/to-issues/SKILL.md"

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

# To Issues

Run in the same window as the `/vision-align` session — the reasoning behind the
decisions is input. Ask the human when a split isn't forced by what's on the
table; questions here are about decomposition (boundaries, seam ownership,
ordering), not re-opening the feature.

## 1. Decide the split

Read the repo first. The unit is one agent session's worth of work — don't split
below it; coordination costs more than it saves. Two issues are parallel only if
the file sets they touch are disjoint (verify against the repo, don't assume);
everything else is sequential, ordered by dependency. Where two meet at an
interface, define the seam — types, signatures, contract — now, and write

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