Introduction

In DSH (DeepSeek Harness) plugin development, the accuracy of deliverables directly affects credibility. Many errors stem from over-relying on build scripts instead of opening the files directly to verify them. The delivery-checklist plugin solves this problem by inspecting the actual files rather than depending on scripts.

Plugin Overview

This is a workflow plugin maintained by ChenneyZhuang for verifying files before delivery. It does not rely on script output; instead, it opens the actual files for direct inspection. Its core value is using a few minutes of verification to avoid error fixes that could take days or longer.

Core Features

  1. Open real files for verification: check the file’s line count and the count after de-duplication.
  2. Placeholder scanning: scan for residual content such as TODO, XXX, [X], test, and N/A.
  3. Incremental Diff comparison: compare incremental files with declared baseline files to verify claims such as “all new”.
  4. Ledger tracking: record batches in the ledger and distinguish candidate counts from shippable counts.

Installation and Enabling

Use the officially provided command to clone the repository into Claude’s skills directory:

git clone https://github.com/ChenneyZhuang/delivery-checklist ~/.claude/skills/delivery-checklist

Typical Usage

Scenario: an incremental worksheet claims to be “all new”.

  1. Open both worksheets, showing 240 lines and 5100 lines.
  2. Deduplicate on the name+location key, yielding 239 lines and 5046 lines, and reveal 54 duplicate lines within the same worksheet.
  3. Diff against the declared baseline file; the overlap is 0, verifying the “all new” claim.
  4. Scan for placeholders; the result is clean.

Key Distinction

Distinguish between duplicate rows within a single file and duplicates across batches:
* Duplicate rows within the same file are a defect and must be fixed before shipment.
* The same entity appearing in two batches is normal funnel behavior and should be recorded in the ledger.

Confusing the two can lead to either shipping a defect or deleting normal historical data.

Limitations

  • De-duplication keys are heuristic: the de-duplication key uses name+location, so different entities with the same name and location may be merged. It is recommended to spot-check merged items before shipping.
  • Dependency on ledger maintenance: ledger reconciliation assumes that a ledger exists and is maintained. If the ledger is corrupted, it must be rebuilt first.

Conclusion

By physically opening files and enforcing a strict reconciliation process, this plugin helps DSH developers ensure the quality of their deliverables. It works with all tabular files that an agent can open (xlsx / csv). After installation, it should be used together with ledger maintenance.

  • Plugin directory: https://www.skillhub.cn/plugins/ChenneyZhuang/delivery-checklist
  • GitHub repository: https://github.com/ChenneyZhuang/delivery-checklist