deliver

Name: deliver
Availability: InStock
Author: edupazogle

Orchestrates sprint delivery from a Linear issue through planning, implementation, verification, and reporting.

Updated Aug 27, 2026

Search Tags:#implementation planning #architecture compliance #git branching #linear issues #sprint delivery #verification evidence #CI and acceptance criteria

Ready to run

npx skills add https://github.com/edupazogle/agentic_cockpit --skill deliver-edupazogle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deliver
Source: https://github.com/edupazogle/agentic_cockpit/tree/main/.agents/skills/deliver
Command: npx skills add https://github.com/edupazogle/agentic_cockpit --skill deliver-edupazogle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The deliver skill prevents “hacking” by turning a sprint delivery request into a fully planned, architecture-compliant workflow that is reviewed, implemented, verified, and ready for merge.

Core Features & Use Cases

End-to-end sprint delivery orchestration: Drives a sprint issue from review through implementation to review-ready completion.
Dependency and architecture guardrails: Enforces blocked-by gating and makes docs/architecture.md the single source of truth before any code changes.
Branching, planning, and evidence capture: Creates the correct delivery branch, produces an implementation plan, runs verification, and posts a completion report with test evidence.

Quick Start

Use deliver when you want to deliver a sprint issue by running /deliver AXA-N, where AXA-N is the Linear issue ID for the sprint work.

Frequently Asked Questions about deliver

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

FAQPage Schema

How do I orchestrate sprint delivery from a Linear issue to a review-ready state?▼

Sprint delivery from a Linear issue is orchestrated by enforcing dependency gates, creating an implementation plan, branching, and validating completion via acceptance criteria. This ensures work is fully planned, architecture-compliant, and ready for merge.

How does architecture compliance work during sprint implementation?▼

Architecture compliance is enforced by requiring docs/architecture.md as the single source of truth before any code changes occur. This prevents hacking by ensuring implementation plans align with the system's structural authority.

What's the best way to handle blocked dependencies and branching for Linear issues?▼

Handling blocked dependencies requires enforcing blocked-by gating before proceeding with sprint work. The workflow then creates the correct delivery branch and produces an implementation plan to ensure safe, tracked lifecycle management.

Do I need a sprint doc and Linear issue ID to automate implementation planning?▼

You need a Linear issue ID and a corresponding sprint doc to automate implementation planning. These inputs trigger the workflow, which uses the plan to run verification and capture test evidence for the completion report.

How is sprint completion validated against acceptance criteria?▼

Sprint completion is validated by running verification processes and checking results against the sprint demo and acceptance criteria. A completion report is then posted with the test evidence to prove the work is finished.