vertical-slicing
Rules for cutting work into vertical slices where each PR defines only what it uses. Use when splitting a spec or plan into tickets or PRs, deciding which ticket a function, constant, class, type or schema change belongs to, or when another skill needs the slicing rules.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- vertical-slicing
- description
- Rules for cutting work into vertical slices where each PR defines only what it uses. Use when splitting a spec or plan into tickets or PRs, deciding which ticket a function, constant, class, type or schema change belongs to, or when another skill needs the slicing rules.
02 资源文件 1
- 参考文档agents/openai.yaml121 B
03 SKILL.md 正文
Vertical Slicing
One ticket is one PR, and a human reviews each PR alone: no earlier PR fresh in mind, no later PR in sight. A PR earns its merge from what is inside it. Cut the work so each is a vertical slice, and place every definition by first use.
Vertical slice
- A slice cuts a narrow but COMPLETE path through every layer it needs (schema, API, UI, tests): vertical, NOT a horizontal slice of one layer.
- Merged alone, a slice is demoable or verifiable through behaviour it makes work.
- A slice fits in a single fresh context window.
Thin a slice by behaviour, never by layer: one case, one field, the happy path first. The next case is the next slice.
First use
A definition is anything a PR adds that other code can refer to: a function, constant, class, type, field, column, table, endpoint, config key, flag, dependency.
Every definition lands in the slice that first uses it. A use is a path from the behaviour the slice delivers to the definition; a test alone is not a use. So at each slice's merge, deleting any definition it added would break behaviour it delivers, and the reviewer sees why it exists without opening another PR. The deletion test from codebase-design applies PR by PR.
What follows:
- Layers grow slice by slice. The first slice adds only the columns, fields and parameters its one case reads or writes; later slices add theirs.
- A ticket whose job is the helpers, the types or the foundation does not exist. Its contents move into the slices that use them.
- When two slices need the same definition, the one that lands first defines it and blocks the other. The shared definition is the blocking edge; the ticket says so.
- A prefactor reshapes code that is already called, and every name it introduces is used when it merges. A seam or parameter that only a later slice needs belongs to that slice.
- A wide refactor's expand ships with its first migrate batch, so the new form lands with a caller.
When a cut cannot be vertical
Some work has no thin end-to-end path: a contract two teams meet at, a build or infrastructure step with no user-visible surface. Then cut horizontally on purpose:
- The ticket says it is a horizontal cut, why, and which ticket consumes it, in words the PR body carries to the reviewer.
- What lands unused is the one interface that consumer needs, no wider.
- That consumer is blocked on it, so the unused interface lives for one merge.
Check
Before a breakdown is shown, for every slice:
- Name the behaviour that works once it merges alone.
- For every implementation decision the spec assigns to it (module, interface, schema change, contract), name the path inside the slice that uses it. One without a path moves to the slice that has one, or shrinks to the part this slice uses.
- Confirm each blocking edge is a definition or behaviour the slice uses, and that every such definition has an edge.
Done when every slice passes all three, or carries the horizontal-cut note.
04 同仓库更多 Skills
improve
暂无简介
create-verification-skill
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
maintain-verification-skill
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
verdict
The Reviewer's Verdict on a PR: re-run the repo's verification skill at the PR's head, hold the PR's Evidence against it, and record pass or fail with nico-agent.
research
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.