← All playbooks · Raw API
task-case-study-from-package
# Capability: Case study from a package
## Intent phrases
- build case study from Drive
- multi-ART port
- lab case study from Figma
- case study from package
- port case study assets
- multi-block case study from brief
- process case study assets
## Requires capabilities
`articles`
## Prerequisites
- Read `cms-edit://customer/case-study-from-package` (full playbook + SE media-pipeline ops table)
- Read `cms-edit://customer/articles` (SEO, lab, composition)
- Read `cms-edit://customer/task-media-pipeline-prepare` when the package has a Drive media folder
- `cms_edit ["index", "sync"]` when assets will be reused by filename
## Steps
1. Run **`task-source-readiness-review`** — inventory, beat sheet, GO / GO-WITH-GAPS / NO-GO
2. Post soft-proof (numbered content order + gaps)
3. Light human **yes** before create
4. **Media pack:** if Drive/binary masters exist, run **`task-media-pipeline-prepare`**
- Base: `https://se-media-pipeline.vercel.app`
- Tenant: `se`
- Folder shared with `media-pipeline-reader@se-media-pipeline.iam.gserviceaccount.com`
- Import ready URLs with reuse-first + `asset upload --url`
5. Lab defaults for experiments: `lab/…` slug, `hidden`, unindexed, `LAB |` labels
6. Build multi-block **Case study rich text** in **source order** — Separated only for true pairs; merge continuous prose; link visuals from the pack map
7. **Do not rewrite copy**
8. `diff` → `save` → **`task-preview-verify`** multi-block checklist
## Out of scope
- Publish lab articles
- Rewriting source copy
- Inventing pair layouts or section titles
- Mid-chat ffmpeg / oversized staged uploads
## Related resources
- `cms-edit://customer/case-study-from-package`
- `cms-edit://customer/articles`
- `cms-edit://customer/task-source-readiness-review`
- `cms-edit://customer/task-media-pipeline-prepare`
- `cms-edit://customer/task-media-reuse-and-upload`
- `cms-edit://customer/task-create-article`
- `cms-edit://customer/task-preview-verify`