integration-slice-orchestration

Orchestrate FE/BE feature integration through incremental vertical slices with frozen contracts.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill integration-slice-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-slice-orchestration
Source: https://github.com/Luis-ERP/dev-agent-crew/tree/main/skills/integration-slice-orchestration
Command: npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill integration-slice-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams align frontend, backend, and contracts by delivering features in small, vertical slices, reducing integration risk and rework.

Core Features & Use Cases

  • Define a minimal set of vertical slices that touch both FE and BE and rely on frozen contracts.
  • Coordinate slice ownership, HANDOFF sequence, and verification per slice.
  • Track visibility of progress and risk across slices and gates.

Quick Start

Define the first integration slice by outlining the contract surface, backend and frontend responsibilities, and the verification signal; then record it in HANDOFF.

Frequently Asked Questions about integration-slice-orchestration

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

FAQPage Schema
How do I coordinate frontend and backend integration to reduce rework?

Frontend and backend integration is coordinated by delivering features in small, vertical slices that rely on frozen contracts, reducing integration risk and rework. Each slice touches both FE and BE, generating per-slice verification signals and recorded HANDOFF transitions.

What is a vertical slice in FE-BE feature integration?

A vertical slice in FE-BE integration is a minimal, incremental feature unit that touches both frontend and backend, relies on frozen contract surfaces, and produces a standalone verification signal to track progress and risk.

How do I manage handoffs during parallel frontend and backend development?

Handoffs during parallel FE and BE development are managed by recording HANDOFF transitions for each integration slice, tracking ownership and verifying that contract surfaces remain frozen before passing responsibilities between teams.

When should I use incremental slicing for feature integration?

Incremental slicing for feature integration should be used when a feature touches both frontend and backend, contracts are frozen, and parallel FE/BE work is planned to minimize integration risk and ensure per-slice verification.

How do I define the first integration slice for a new feature?

To define the first integration slice, outline the frozen contract surface, specify backend and frontend responsibilities, and define the verification signal, then record the transition as a HANDOFF to track progress and ownership.