delivery-checklist

Automate pre-delivery planning with a structured delivery loop for stories, PRs, and release tasks.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AINative-Studio/telemetry-agent --skill delivery-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-checklist
Source: https://github.com/AINative-Studio/telemetry-agent/tree/main/.ainative/skills/delivery-checklist
Command: npx skills add https://github.com/AINative-Studio/telemetry-agent --skill delivery-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This checklist and mini-prompts provide a structured, repeatable pre-delivery workflow to ensure quality and readiness before merging or releasing work.

Core Features & Use Cases

  • Standardized delivery loop (Plan → Implement → Artifacts → PR → Verify CI → Deliver) to coordinate steps across teams.
  • Reusable mini-prompts for tasks like classifying stories, kicking off TDD, safe refactors, and PR composition.
  • Acceptance criteria templates and reference materials to guide reviewers and maintain quality.

Quick Start

Run the delivery-checklist workflow to guide your pre-delivery preparation and PR process using the included prompts and references.

Frequently Asked Questions about delivery-checklist

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

FAQPage Schema
How do I create a pre-delivery checklist for pull requests?

A pre-delivery checklist standardizes the PR process using a structured loop: Plan, Implement, Artifacts, PR, Verify CI, and Deliver. It coordinates tasks across teams with reusable mini-prompts and explicit acceptance criteria to guide reviewers.

What is a standardized delivery loop for software release tasks?

A standardized delivery loop coordinates release readiness through sequential steps: Plan, Implement, Artifacts, PR, Verify CI, and Deliver. It applies to stories and PRs, using prompts and references as sources of truth to maintain quality.

How do I write acceptance criteria for PR review?

Write acceptance criteria for PR review using provided templates and reference guidance. These criteria act as sources of truth to guide reviewers, verify implementation steps, and ensure quality before merging or releasing work.

Can I use mini-prompts for TDD and safe refactoring?

Yes, reusable mini-prompts support kicking off TDD and executing safe refactors. They also include prompts for classifying stories and PR composition, integrating directly into the pre-delivery workflow.

Does the delivery workflow support story classification?

Yes, the delivery workflow supports story classification through reusable mini-prompts. It applies structured steps to stories, PRs, and release tasks, ensuring tasks are properly categorized before implementation and verification.

When do I need a structured pre-delivery workflow?

You need a structured pre-delivery workflow when coordinating stories, PRs, and release tasks that require explicit acceptance criteria. It ensures quality and readiness before merging by applying a repeatable sequence from planning to final delivery.