sell-slice

Orchestrate software slice delivery with subagent dispatch and multi-stage verification.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/steve-piece/bytheslice --skill sell-slice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sell-slice
Source: https://github.com/steve-piece/bytheslice/tree/main/skills/sell-slice
Command: npx skills add https://github.com/steve-piece/bytheslice --skill sell-slice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of bloated, unmanageable pull requests by enforcing a strict, high-touch delivery loop that ships software one slice at a time with rigorous verification.

Core Features & Use Cases

  • Interactive Delivery Spine: Orchestrates a complete workflow from reconnaissance and build-plan authorization to production and verification.
  • Automated Quality Gates: Integrates static analysis, unit testing, and behavioral UAT to ensure every slice is production-ready before commit.
  • Use Case: When building a complex feature, use this Skill to decompose the task into individual, verifiable slices, ensuring each piece of code is tested, reviewed, and documented before moving to the next.

Quick Start

Run the sell-slice skill to begin the delivery loop for the next item in your master checklist.

Frequently Asked Questions about sell-slice

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

FAQPage Schema
How do I automate git workflow delivery to ship small, verifiable slices instead of bloated pull requests?

To ship verifiable slices instead of bloated pull requests, this Skill orchestrates a high-touch delivery loop that decomposes complex features into individual pieces, applying automated quality gates and multi-stage verification before each commit.

What is a single-slice delivery loop for complex feature development?

A single-slice delivery loop is an orchestration process that manages subagent dispatch and build-plan authorization, ensuring complex feature development adheres to master checklists with isolated, verifiable commits using local git worktree management.

How do I set up automated quality gates for static analysis and unit testing before a git commit?

Automated quality gates for static analysis and unit testing are integrated directly into the delivery spine, ensuring every software slice passes behavioral UAT and is production-ready before moving to the next item in your master checklist.

Does this delivery orchestration workflow require local git worktree management?

Yes, local git worktree management is required to ensure isolated, verifiable commits during the delivery loop, integrating with Claude Code primitives to maintain strict adherence to your automated quality gates and master checklists.

When should I use a high-touch delivery orchestration workflow for software slices?

Use high-touch delivery orchestration when building complex features that require strict adherence to master checklists, decomposing tasks into individual slices to ensure each piece of code is tested, reviewed, and documented before moving to the next.

Can I integrate subagent dispatch and build-plan authorization into my existing automation workflow?

Yes, subagent dispatch and build-plan authorization are core components of the interactive delivery spine, integrating with Claude Code primitives to orchestrate the complete workflow from reconnaissance to production and verification.