impl-slice

Coordinate vertical slice planning, worker assignment, and progress tracking.

2|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/dayvidpham/aura-plugins --skill impl-slice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impl-slice
Source: https://github.com/dayvidpham/aura-plugins/tree/main/skills/impl-slice
Command: npx skills add https://github.com/dayvidpham/aura-plugins --skill impl-slice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating complex, multi-slice implementation plans is difficult without a repeatable process to decompose work, assign ownership, and monitor progress across slices.

Core Features & Use Cases

  • Create and manage vertical slices with identifiers, names, specifications, and ownership.
  • Assign workers, track progress, and enforce dependencies between slices to avoid bottlenecks.
  • Aggregate slice completion to gate downstream reviews and delivery, including support for follow-up slices.

Quick Start

Create and assign the first slice to a worker using the provided CLI workflow.

Frequently Asked Questions about impl-slice

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

FAQPage Schema
How do I coordinate vertical slice planning and track progress across multiple workers?

Vertical slice planning is coordinated by decomposing an end-to-end implementation plan into structured slices, assigning them to workers, and monitoring progress to enforce dependencies. This prevents bottlenecks and aggregates slice completion to gate downstream delivery.

What is the best way to manage dependencies between tasks in an agile workflow?

Managing dependencies in an agile workflow requires enforcing relationships between vertical slices during task tracking. The system monitors progress across assigned workers and gates downstream reviews until dependency requirements are fully satisfied.

How do I decompose a project plan into vertical slices for implementation?

Decomposing a project plan into vertical slices involves creating structured-slice data with identifiers, names, and specifications. A supervisor-led phase assigns these slices to workers, enabling dynamic bonding and progress aggregation.

Can I aggregate task completion to gate downstream delivery and reviews?

Aggregating task completion to gate downstream delivery is supported by tracking slice progress and enforcing dependencies. Once assigned workers complete their slices, the aggregated state gates downstream reviews and supports follow-up slices.

Does this vertical slice tracking approach require any external dependencies or components?

This vertical slice tracking approach requires no external dependencies or components. It operates independently to coordinate structured-slice data, dynamic bonding, and progress updates within an end-to-end implementation workflow.

When should I not use vertical slice coordination for project management?

Vertical slice coordination should not be used when a project plan cannot be decomposed into discrete, dependent slices. It requires a supervisor-led workflow to assign workers, monitor progress, and aggregate completion data for delivery gating.