vertical-slice-delivery
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseVertical Slice Delivery
垂直切片交付
This skill defines the default delivery methodology for planning and shipping
work as independently valuable, reviewable vertical slices.
txt
Skateboard → Scooter → Bicycle → Motorcycle → CarLoad and obey its that lives next to this .
AGENTS.mdSKILL.md本Skill定义了规划和交付工作的默认方法论，将工作拆分为具备独立价值、可评审的垂直切片。
txt
滑板 → 踏板车 → 自行车 → 摩托车 → 汽车加载并遵循与本同级的文件。
SKILL.mdAGENTS.mdWhen to Apply
适用场景
Use this skill whenever work is being:
- planned
- split into tasks or steps
- delivered incrementally
- resumed after interruption
Any deviation from vertical slice delivery MUST be explicit and justified.
在以下工作场景中使用本Skill：
- 规划工作时
- 将工作拆分为任务或步骤时
- 增量交付工作时
- 中断后恢复工作时
任何偏离垂直切片交付的做法必须明确说明并给出理由。
Core Loop
核心循环
Each slice = one commit + one review. No slice begins until the previous is approved.
- IMPLEMENT — one behavioral slice only
- COMMIT — with slice ID and conventional message
feat(scope): [S1] description - STOP — mandatory review (do not proceed)
- WAIT — approved → next slice, blocked → fixup and re-review
每个切片 = 一次commit + 一次评审。前一个切片获得批准后，才能开始下一个切片。
- 实现 — 仅完成一个行为切片
- 提交 — 包含切片ID和规范提交信息
feat(scope): [S1] description - 停止 — 必须进行评审（不得继续推进）
- 等待 — 批准后进入下一个切片，若被阻塞则修复后重新评审
Key Concepts
关键概念
| Concept | Summary |
|---|---|
| Behavioral Slices | Deployable behaviors, not technical tasks. "Can a user demo this alone?" |
| Role Separation | Delivery writes code; Review audits and approves. Self-approval prohibited. |
| Git Discipline | Status before work, explicit paths, fixups for amendments |
| Code Guidelines | Improve touched code only, no speculative abstraction |
| 概念 | 概述 |
|---|---|
| 行为切片 | 可部署的功能行为，而非技术任务。需自问：“用户能否单独演示这个功能？” |
| 角色分离 | 交付人员负责编写代码；评审人员负责审核和批准。禁止自我批准。 |
| Git规范 | 工作前明确状态，清晰路径，通过修复提交修正问题 |
| 代码准则 | 仅改进涉及的代码，不得进行投机性抽象 |
Full Document
完整文档
All rules with examples and details:
AGENTS.md包含所有规则及示例和细节的完整内容：
AGENTS.md