## TL;DR

Ship every content piece as a pack: the final text, two title variants, a one-line excerpt, a featured image with alt text, tags, the canonical URL, and the adapted per-platform versions. A checklist makes packs complete by default; incomplete packs are why publishing stalls on missing images at the last minute.

```text
building a content pack: assets per piece checklist
```

## Use this when

- Standardizing a content pipeline
- Handing production to someone else or to automation
- Publishing stalls on missing assets

## Not for this skill when

- You publish rarely and informally (overhead)
- The checklist would never be read (fix adoption first)
- One platform is the whole strategy (simplify instead)

## Steps

1. Define the pack contents once. Text, titles, excerpt, image plus alt text, tags, canonical URL, platform adaptations, scheduled dates. Expected: a fixed checklist, not a per-piece invention.

2. Produce assets in dependency order. Text first, then titles and excerpt from the text, then image, then adaptations. Expected: no asset waits on another out of order.

```
pack checklist:
  [ ] final text
  [ ] title A / title B
  [ ] one-line excerpt
  [ ] featured image + alt text
  [ ] tags
  [ ] canonical URL
  [ ] platform adaptations
  [ ] scheduled dates
```

3. Name files consistently. Date plus slug plus asset type, so packs are findable months later. Expected: a naming convention in the checklist.

4. Review the pack as a unit. One pass over everything before anything publishes; missing alt text and broken links get caught here. Expected: no publish blocked on a missing asset.

5. Archive packs after publishing. Keep them with their performance notes; the next similar piece starts from a proven pack. Expected: a growing library, not a pile.

## Variant phrasings

### content production asset checklist

Text, titles, excerpt, image and alt, tags, canonical, adaptations, dates.

### what goes in a content pack

Everything publishing needs, assembled before anything ships.

### standardizing content assets

Fixed checklist, dependency-ordered production, unit review, archived packs.

## Why it happens

Publishing stalls on the last missing asset: the image nobody made, the excerpt nobody wrote, the alt text skipped. A pack checklist moves those from "remembered at midnight" to "produced in order", which is the difference between a pipeline and a scramble.

## Edge cases / pitfalls

- Do not gold-plate; the checklist should fit the actual distribution, not an ideal one.
- Alt text is not optional; write it when the image is made, not later.
- Keep image sources; you will need to resize for the next platform.
- Review the checklist itself quarterly; packs accrete cruft.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LexSGtlBUTxyuRhermtikw