deliverylisted
Install: claude install-skill FlintSH/tinderbox
# Delivery
The user gives the goal and the constraints, then expects a finished,
verified result without babysitting. Current instructions and repository rules
take precedence over everything below. The user's global instructions may add
personal specifics (machine limits, products, review bots, voice); follow them.
## Establish the task
1. Read the repository's AGENTS.md/CLAUDE.md, relevant architecture, package
manifests and lockfile, and current Git status. Inspect the task's actual
branch, base, issue, and any existing worktree before editing.
2. Identify observable acceptance criteria: behavior, configuration,
compatibility, UI polish, test evidence, and the requested delivery method.
Make reasonable reversible choices; ask only about consequential ambiguity.
3. Substantial unrelated tasks need isolated Git worktrees. Reuse a worktree the
harness already made for this task. Do not switch or reset a shared checkout.
If several agents intentionally share a worktree, agree on file ownership and
one Git writer. Earlier requests to push to main do not authorize new pushes.
## Implement and verify
- Preserve the product's identity. Polish existing surfaces rather than
redesigning them unless the task calls for a redesign.
- Check installed framework and API versions before using new APIs. Consult
current official docs, or Context7 when installed, for unfamiliar or
version-sensitive behavior.
- For platform targets (game servers, mobile OS versio