← Back to Skills Marketplace
urbantech

Delivery Checklist

by Toby Morning · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
140
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install delivery-checklist
Description
Pre-delivery acceptance checklist and reusable mini-prompts for common tasks. Use when (1) Preparing to mark story as Delivered, (2) Final PR review before m...
README (SKILL.md)

Delivery Checklist & Mini-Prompts

Default Loop

Plan → Implement (Red→Green→Refactor) → Produce Artifacts → PR → Verify CI → Deliver

Always respond in this order:

  1. Plan (checklist)
  2. Actions & Artifacts (logs, screenshots, test output)
  3. Findings
  4. Code Diffs (unified ---/+++ patches)
  5. Tests Added/Updated
  6. PR Description (summary, risks, rollout)
  7. Next Steps

Acceptance Checklist (before marking Delivered)

  • Story type + estimate stated; branch follows convention
  • Red→Green→Refactor commits present (incl. WIP + EOD)
  • Tests added/updated and passing locally & in CI
  • Security/a11y/responsive considerations addressed (if UI)
  • PR description complete with evidence and rollback plan
  • Staging deploy verified or verification plan included

Reusable Mini-Prompts

  • Classify story: "Classify as feature/bug/chore and justify. Provide estimate (0/1/2/3/5/8) with rationale."
  • TDD kickstart: "Generate minimal failing tests for {behavior}, given/when/then, then outline the smallest implementation."
  • Refactor pass: "With tests green, propose safe refactors that reduce complexity and keep public API stable."
  • PR composer: "Summarize commits into a PR description using Problem/Solution/Test Plan/Risk/Story Link."

Reference Files

See references/acceptance-criteria.md for expanded checklist with examples and verification steps.

See references/mini-prompts.md for detailed mini-prompt templates with usage examples.

Usage Guidance
This skill is a reusable checklist and set of prompt templates and appears coherent. Before installing or using it, note that: (1) the SKILL.md references example files that are not included — you will need to supply repository context, logs, diffs, or screenshots when asking the skill to produce evidence; (2) when using the skill to generate code diffs or PR descriptions, avoid pasting sensitive data (secrets, credentials) into prompts; (3) if you allow an agent running these prompts to access your repository or CI, ensure the agent's permissions are scoped appropriately. If you want the referenced examples included, ask the publisher for the missing references/ files or provide your own.
Capability Assessment
Purpose & Capability
Name/description (delivery checklist, PR composer, mini-prompts) match the SKILL.md content. No unexpected binaries, env vars, or credentials are requested and the prompts are appropriate for the stated purpose.
Instruction Scope
The SKILL.md asks the agent to produce artifacts (logs, screenshots, test output, unified diffs) and references files under references/*. Those files are not present in the package, so the agent will need user-provided context or repo access to fulfill those parts. The instructions do not themselves instruct the agent to read arbitrary system files or environment variables.
Install Mechanism
No install spec and no code files — instruction-only skill with no on-disk installation or third-party downloads.
Credentials
No environment variables, credentials, or config paths are requested. Nothing disproportionate is asked for relative to the skill's stated function.
Persistence & Privilege
always is false and the skill does not request persistent or elevated privileges. It is user-invocable and can be invoked autonomously per platform defaults, which is expected for a prompt/template skill.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install delivery-checklist
  3. After installation, invoke the skill by name or use /delivery-checklist
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of delivery-checklist skill. - Provides a structured pre-delivery acceptance checklist for software stories and PRs. - Includes a default process loop (Plan → Implement → Artifacts → PR → Verify → Deliver) with step-by-step outputs. - Offers reusable mini-prompts for classification, TDD, refactoring, and PR composition. - Supplies an acceptance criteria checklist covering tests, commits, security/UI concerns, PR format, and verification. - References detailed checklists and prompt templates in supplementary files.
Metadata
Slug delivery-checklist
Version 1.0.0
License MIT-0
All-time Installs 2
Active Installs 2
Total Versions 1
Frequently Asked Questions

What is Delivery Checklist?

Pre-delivery acceptance checklist and reusable mini-prompts for common tasks. Use when (1) Preparing to mark story as Delivered, (2) Final PR review before m... It is an AI Agent Skill for Claude Code / OpenClaw, with 140 downloads so far.

How do I install Delivery Checklist?

Run "/install delivery-checklist" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Delivery Checklist free?

Yes, Delivery Checklist is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Delivery Checklist support?

Delivery Checklist is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Delivery Checklist?

It is built and maintained by Toby Morning (@urbantech); the current version is v1.0.0.

💬 Comments