delivery-checklist

Provide a structured checklist and reusable prompts for software delivery verification.

2|1|Updated May 27, 2025
One-click install
npx skills add https://github.com/PAIPalooza/chicommerce --skill delivery-checklist-paipalooza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-checklist
Source: https://github.com/PAIPalooza/chicommerce/tree/main/.ainative/skills/delivery-checklist
Command: npx skills add https://github.com/PAIPalooza/chicommerce --skill delivery-checklist-paipalooza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured checklist and reusable prompts to ensure a smooth and complete delivery process for software development stories, reducing errors and improving review efficiency.

Core Features & Use Cases

  • Pre-delivery Verification: A comprehensive checklist to confirm all aspects of a story are complete before marking it as delivered.
  • Standardized Workflow: Enforces a consistent "Plan -> Implement -> Artifacts -> PR -> Verify -> Deliver" loop.
  • Reusable Prompts: Quick templates for common tasks like story classification, TDD initiation, refactoring, and PR description generation.
  • Use Case: Before merging a pull request, use the acceptance checklist to ensure all tests pass, documentation is updated, and the PR description is thorough.

Quick Start

Use the delivery-checklist skill to verify the completeness of a story before marking it as delivered.

Frequently Asked Questions about delivery-checklist

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

FAQPage Schema
How do I ensure a software development story is ready for delivery before marking it as delivered?

To ensure a development story is ready for delivery, use a pre-delivery acceptance checklist to verify all tests pass, documentation is updated, and the PR description is thorough. This enforces a consistent workflow loop from planning to final verification.

What is the best way to standardize a development workflow for pull requests and code review?

Standardizing a development workflow for pull requests involves enforcing a structured loop: Plan, Implement, Artifacts, PR, Verify, and Deliver. Reusable prompts for PR composition and code review checklists ensure consistent quality across the team.

Can I use reusable prompts for common developer tasks like TDD and refactoring?

Yes, you can use reusable mini-prompts to initiate test-driven development (TDD), guide refactoring efforts, and generate pull request descriptions. These templates integrate directly into the standard delivery loop to streamline common developer tasks.

Does a pre-delivery checklist help with final PR reviews?

A pre-delivery checklist significantly helps with final PR reviews by providing a structured verification step. It confirms that all acceptance criteria are met, artifacts are complete, and the pull request description accurately reflects the implemented changes.

When do I need to verify acceptance criteria during the software delivery process?

You need to verify acceptance criteria during the Verify stage of the software delivery process, just before marking a story as delivered. This ensures the implementation matches the planned artifacts and passes the pre-delivery checklist.