delivery-loop

Coordinate a four-step plan, review, QA, and ship execution loop.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jukqaz/stack-pilot --skill delivery-loop-jukqaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delivery-loop
Source: https://github.com/jukqaz/stack-pilot/tree/main/addons/stackpilot-dev-kit/codex/skills/delivery-loop
Command: npx skills add https://github.com/jukqaz/stack-pilot --skill delivery-loop-jukqaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams manage large tasks by enforcing a structured execution loop that plans, reviews, QA, and ships with clear handoffs.

Core Features & Use Cases

  • Structured Plan/Bounded Slice: plan the smallest deliverable and bound scope.
  • Explicit Reviews & Risk Checks: review changes before or immediately after implementation and document risks.
  • Narrow QA & Verification: run targeted quality checks before shipping.
  • Handoff Trail: produce a concise final report capturing decisions and status.
  • Use Case: when a task is large but not a giant harness, use this skill to maintain focus and traceability.

Quick Start

Plan the smallest deliverable, then proceed through review, QA, and ship steps.

Frequently Asked Questions about delivery-loop

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

FAQPage Schema
How do I manage large project tasks with a structured plan-review-QA-ship workflow?▼

This workflow coordinates large project tasks by enforcing a four-step execution loop: plan a bounded deliverable, review changes with risk checks, run narrow QA, and ship with a documented handoff trail.

What is the best way to enforce scope boundaries and explicit signoffs during project execution?▼

To enforce scope boundaries, plan the smallest deliverable first, then require explicit signoffs across the review, QA, and shipping phases to maintain strict focus and traceability.

Can I use this plan-review-QA-ship loop for solo work, or does it require a full team?▼

Yes, you can use this plan-review-QA-ship loop for both solo work and cross-team projects. It applies to any large task requiring disciplined planning, explicit reviews, and a compact handoff trail.

How does the handoff process work after completing the QA and execution steps?▼

After completing the QA and ship steps, the handoff process outputs a compact final report capturing decisions, status, and the handoff trail to ensure clear traceability across teams.

When should I use a bounded execution loop instead of a giant test harness for project management?▼

Use a bounded execution loop when a task is large but does not require a giant harness. It maintains focus by bounding deliverable scope and enforcing structured review and QA steps.