vertical-slice

Coordinate end-to-end Librova feature work across domain logic, Qt adapters, and UI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/EvgeniiFenita/Librova --skill vertical-slice-evgeniifenita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vertical-slice
Source: https://github.com/EvgeniiFenita/Librova/tree/main/.agents/skills/vertical-slice
Command: npx skills add https://github.com/EvgeniiFenita/Librova --skill vertical-slice-evgeniifenita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end feature integration for Librova is managed via a structured playbook that ensures new features are planned, implemented, tested, and documented across all touched layers.

Core Features & Use Cases

  • End-to-end feature slice for read-side, mutation-use-cases, and UI-shell workflows
  • Guides back-to-back planning, testing, and documentation updates aligned with AGENTS.md and CodebaseMap.md
  • Ensures pre-start governance and close-out validation before marking tasks complete

Quick Start

Identify a backlog item, classify the slice type, and follow the entry-point checklist in docs/CodebaseMap.md.

Frequently Asked Questions about vertical-slice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an end-to-end feature slice in software development?

This approach coordinates end-to-end feature work by providing a comprehensive playbook spanning from read-side queries to UI shell workflows. It guides planning, testing, and documentation updates across all touched layers for safe, reproducible delivery.

How do I plan and implement an end-to-end feature slice with tests?

To implement an end-to-end feature slice with tests, identify a backlog item, classify the slice type, and follow the entry-point checklist in the repository's CodebaseMap. Apply cross-layer checkpoints and close-out validation before marking tasks complete.

Do I need specific repository documentation to use end-to-end feature slices?

Yes, end-to-end feature slices require alignment with repository governance in docs/CodebaseMap.md and AGENTS.md. These files provide the entry-point checklists, module navigation, and pre-start governance needed for safe delivery.

When should I use an end-to-end feature slice for new features?

Use an end-to-end feature slice when new features require cross-cutting changes to domain logic, Qt adapters, and UI. It ensures structured backlog mapping, cross-layer checkpoints, and documentation updates for complex integrations.

What are the limitations of using a feature slice approach for software development?

The feature slice approach is limited to features requiring cross-cutting changes across domain logic, Qt adapters, and UI. It mandates explicit test coverage and governance alignment, which may not suit smaller, isolated code modifications.