
Vertical Slice
- 1 installs
- Updated June 5, 2026
- ahze667/kasandra
vertical-slice is a Claude Code skill that delivers one bounded end-to-end change across a project's cli, sources, processing, storage, and outputs layers in a single branch.
About
vertical-slice drives a single small end-to-end change across the CLI, sources, processing, storage, and outputs layers of the Kasandra project within one task/<slug> branch. It keeps scope bounded to the layers that must change and requires parallel updates to docs and examples in the same change set. It mandates that uv run poe check passes before closing the task and uses one commit per task in a conventional format. The SKILL.md is written in Polish.
- Delivers one bounded end-to-end slice across cli/sources/processing/storage/outputs
- Keeps code, tests, docs and examples consistent in one change set
- Requires uv run poe check to pass and one commit per task
Vertical Slice by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,479 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 7, 2026 (Skillselion catalog sync)
vertical-slice capabilities & compatibility
- Capabilities
- vertical slice · scoped change · docs sync
- Use cases
- planning · refactoring
- Pricing
- Free
What vertical-slice says it does
Fires when the user asks for a small end-to-end change across CLI/sources/processing/storage/outputs.
Jeden maly slice end-to-end dowieziony w jednym branchu `task/<slug>`
`uv run poe check` musi przechodzic zanim zamkniesz task
npx skills add https://github.com/ahze667/kasandra --skill vertical-sliceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | June 5, 2026 |
| Repository | ahze667/kasandra ↗ |
What it does
Deliver one bounded end-to-end change across cli/sources/processing/storage/outputs with tests and docs in a single branch.
Who is it for?
Skip if: Adding a new data source (use source-integration) or broad architecture refactors, which the non-goals exclude.
When should I use this skill?
You want a small, bounded end-to-end change across the CLI/sources/processing/storage/outputs layers delivered in one branch with tests and docs.
What you get
One coherent slice landed on a task branch with code, tests, docs, and examples kept consistent.
- one bounded slice with code, tests, docs and examples updated
- single conventional commit
By the numbers
- 5 layers in scope (cli, sources, processing, storage, outputs)
- one commit per task
Files
Vertical slice
Cel
Jeden maly slice end-to-end dowieziony w jednym branchu task/<slug>, zachowujacy spojnosc miedzy kodem, testami, docs/ i docs/examples/.
Constraints
- scope nie rozlewa sie poza warstwy ktore naprawde musza sie zmienic (
cli,sources,processing,storage,outputs) - zmiana kontraktu wymaga rownoleglej aktualizacji
docs/idocs/examples/w tym samym change secie uv run poe checkmusi przechodzic zanim zamkniesz task- commit w formacie
<typ>(<scope>): <opis>, jeden commit na task (wyjatek: schema + kod)
Non-goals
- nie dodaje nowego zrodla w ramach zwyklego slice'a — do tego jest
source-integration - nie staje sie szerokim refactorem architektury
- nie wprowadza ciezkiej infrastruktury "na zapas"
Gotchas
- sources i storage w
src/kasandra/sa dzis w wiekszosci stubami; przed zmiana sprawdz czy kontrakt juz istnieje, czy go wprowadzasz var/jest runtime — nie commituj niczego co tam trafi- testy siedza w
tests/unititests/integration; integration test dla CLI juz istnieje jako wzorzec
Related skills
FAQ
What must pass before closing the task?
uv run poe check must pass before you close the task.
Is adding a new data source in scope?
No. A new source belongs to the source-integration skill, not a normal vertical slice.