slice-strategy

Divide FleziBCG backend development into vertical slices with tests.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/anpanmaaaan/FleziBCG --skill slice-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slice-strategy
Source: https://github.com/anpanmaaaan/FleziBCG/tree/main/docs/ai-skills/slice-strategy
Command: npx skills add https://github.com/anpanmaaaan/FleziBCG --skill slice-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of building a complex backend system by suggesting a vertical slice approach, which helps in incrementally developing and validating system functionality.

Core Features & Use Cases

  • Vertical Slicing: Breaks down the backend development into manageable, independently verifiable slices.
  • Incremental Development: Allows for early validation and testing of system slices.
  • Use Case: For a new MES/MOM system, you can start with the execution core and then progressively add slices like quality management, manufacturing data, and supervisory operations.

Quick Start

Apply the slice-strategy skill to begin implementing FleziBCG with a focus on the Execution Core slice.

Frequently Asked Questions about slice-strategy

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

FAQPage Schema
What is vertical slicing in backend development?

Vertical slicing divides a complex backend system into manageable, independently verifiable slices for modular development. Each slice includes database, backend truth, event/invariant, tests, and minimal frontend verification.

How do I implement an MES/MOM system incrementally?

Implement an MES/MOM system incrementally by starting with the execution core and progressively adding vertical slices like quality management, manufacturing data, and supervisory operations to validate functionality iteratively.

How to structure vertical slices for iterative system implementation?

Structure vertical slices by including database, backend truth, event/invariant, tests, and minimal frontend verification in each slice. This allows early validation and testing of core functionalities during iterative development.

Can I use vertical slicing for modular backend development without a frontend?

Vertical slicing includes minimal frontend verification in each slice, but the focus remains on modular backend development. The frontend component is lightweight and serves primarily to verify backend truth and system functionality.

When should I choose vertical slicing over horizontal layering for backend development?

Choose vertical slicing over horizontal layering when building complex systems requiring iterative development and early validation of core functionalities. It allows you to verify independent slices rather than waiting for entire horizontal layers to complete.

What are the limitations of vertical slicing for complex backend systems?

Vertical slicing requires defining complete slices with database, backend truth, events, and tests, which may increase initial overhead. It is best suited for iterative development rather than systems with heavily interdependent core functionalities.