Skip to content
Back/Writing

AI-Assisted Creative Production

View in Graph
Updated 2026-10-30
7 min read
1,726 words

AI-Assisted Creative Production

What it is

AI-assisted creative production is a workflow in which AI helps process material, test structures, make visual or textual artifacts, and handle repeatable production steps while the creator retains the question, selection, interpretation, voice, and final judgment. The work is divided by responsibility rather than by a single rule that either the human or the model must do everything.

The available cases describe two different forms of this division. The 诗梳风 team decomposed long-form nonfiction production into material collection, functional classification, card drafting, sequencing, scale decisions, source retrieval, and style migration. Ben Tossell used daily agent sessions as possible story material, then chose to keep idea selection and creative interpretation human-led while automating parts of video and page production. Both are practitioner accounts. They show workable patterns, not controlled proof that one workflow fits every creator.

Why it matters

Prompt-and-polish can produce fluent but generic work. Full delegation can remove the creator's taste, lived experience, and responsibility for what the artifact says. Process-level assistance offers another option: use models where they expand, sort, render, or repeat work, and keep the decisions that give the work its meaning visible to the creator.

This distinction also helps avoid a common design error. A repeatable production system does not need to automate the choice of what is worth making. An agent may find candidate moments in conversations or organize evidence, while the creator decides whether a moment is a story and what the audience should learn from it.

Working boundary: author decisions and agent work

Decisions the creator retains

  • The question or experience the piece is about.
  • Which candidate facts, scenes, conflicts, and interpretations belong in the work.
  • The claim the piece makes and the explanation for its structure.
  • Whether a detail is accurate, fair to the people involved, and sufficiently sourced.
  • The voice, emotional emphasis, exclusions, and final edit.
  • Whether the work should be published at all.

These decisions are not all impossible to assist. An agent can offer alternatives, identify gaps, or ask questions. The evidence from Ben's process is narrower: he tried an automated system that would inspect logs and conversations and suggest two stories each day, then decided he did not want it to make the creative selection for him.

Work agents can support

  • Cleaning transcripts and normalizing source material.
  • Expanding search terms and finding candidate references.
  • Classifying material by function, such as fact, story, or emotional resonance.
  • Generating outline options, cards, drafts, diagrams, and layout variants.
  • Retrieving source passages after notes have been condensed.
  • Rendering a selected visual language across a page or video.
  • Repeating production steps such as sizing, export, light editing, upload preparation, and adding a finished video to a page.

The boundary is chosen per project. It is not a general prohibition on idea discovery or a requirement that every production task be automated.

A workflow that keeps the source inspectable

1. Start from a human question or sample

Record what the creator wants to understand, show, or explain before asking a model to generate a polished piece. For style-sensitive work, keep a human-written sample as a quality anchor. This makes it easier to see whether AI assistance is clarifying the idea or merely making more material.

2. Collect broadly, then select deliberately

The 诗梳风 case treats material collection as part of the creative work. It uses broad research before selection and separates gathering from rejection. Ben's case adds another possible source: sessions with coding and personal agents. An agent can help locate candidate moments, but the creator can retain the decision about which experience deserves a story.

When private conversations are used as source material, define what can be searched, what may be quoted, and what must remain private before automating collection. Keep the original source path so every extracted claim or scene can be checked.

3. Label by narrative function

The 诗梳风 workflow groups material as:

Function Use
Fact Dates, structure, cost, and other verifiable context
Story A sequence with people, actions, and tension
Resonance Material that creates emotional force at an opening, turn, or ending

Labels describe what a passage can do in a piece, not just its topic. They make it easier to notice when a draft has facts but no human-scale scene, or several stories but no evidence for its main claim.

4. Try structures that match the material

A three-act sequence of setup, conflict, and resolution can work for a build story told in the order it happened. Card-based drafting can work for long nonfiction with many sources: split material into inspectable units, remove duplicates, group dependencies, then decide which units need expansion or compression. These are options from the two cases, not a universal template. The creator should choose a form that helps the audience follow the actual reasoning.

5. Create small, reviewable artifacts

Generate outline variants, cards, diagrams, or one page at a time. Keep evidence linked to the source. If a model summarizes material during sorting, retrieve the original passage before final writing. Review the weakest claims and the sections where the creator's judgment is doing the most work.

6. Reuse visual primitives without fixing every story

Ben's visual kit keeps a few objects consistent, including boxes, arrows, prompts, agents, web pages, people, and cameras. Other drawings can be created for the specific story. A repeated new object can become a reusable component after it proves useful more than once.

His iteration also shows why using a tool is different from using its visual language. The first version used a tldraw canvas. The next used a normal HTML page because the desired output was a readable page with diagrams, not an embedded canvas product. The HTML version initially lost arrows and annotations, so he asked the agent to restore them. Review the relationships a diagram must communicate, not just its styling.

7. Automate production after the creative decisions are clear

Repeatable tasks can be encoded as a kit or checklist: choose an output size, prepare tools, export, perform light edits, upload, and update the destination page. Keep a person responsible for final meaning, source accuracy, and audience fit. This division can make production more consistent without turning every story into the same format.

8. Review the artifact and the process

Ask whether the reader can follow the causal sequence, whether diagrams clarify rather than decorate, whether the chosen stories are well-supported, and whether the creator can explain the decisions. For repeated work, also ask whether the format is enjoyable enough to sustain. Ben explicitly treats the creator's enjoyment as one condition for making the series repeatable.

Evidence across sources

Source Practice described What it supports
诗梳风 EP21: AI-assisted content production A team decomposed nonfiction production into research, fact/story/resonance classification, cards, sequencing, scale decisions, source retrieval, style migration, and human review. AI can support a multi-stage creative process while preserving inspectable choices and a final human review.
Ben's Bites: Is Anthropic the best business in the world? Ben explored selecting video stories from agent sessions, rejected daily automated idea selection, and used agents for diagrams, a reusable visual kit, and production steps. A creator may automate making while keeping story selection and interpretation human-led; a small set of repeated visual primitives can coexist with story-specific freedom.

Risks and limits

  • AI can make an unsupported detail sound finished. Keep factual claims linked to source passages and verify them before publication.
  • A fixed workflow can flatten pace and voice. State where a creator may override a rule and preserve examples of useful exceptions.
  • Automated discovery can expose private conversations or select material the creator would not choose to publish. Treat source access and publication approval as separate decisions.
  • The two cases are self-reported and use different types of output. They do not establish a productivity gain, a universal division of labor, or a best tool stack.
  • An enjoyable process may help a creator continue, but enjoyment alone does not establish accuracy or audience value.

Open questions

  • Which creative decisions does Jean want to keep personally owned in different output types?
  • Would a reusable visual kit make a real newsletter, video, or article easier to finish without making it feel templated?
  • What source and privacy boundaries should apply if agent sessions are considered as material for a public story?
  • Do the card-based and session-based approaches work together, or are they useful for different kinds of pieces?
  • How should the creator measure quality beyond output speed, such as source accuracy, clarity, reader response, and willingness to repeat the process?

2026-10-30:上坡下坡框架——技术应该带你下坡,而不是推你上坡

来源:writerbuilder — What Not to Automate(Hilary Gridley)

Hilary Gridley 提出"技术应该带你下坡,而不是推你上坡"的框架。下坡 = 只是想从 A 到 B 的任务(将其自动化到最低限度);上坡 = 让你在某件事上变得更强的挣扎(必须亲自攀登)。技术的承诺不是更少的挣扎,而是更好的挣扎——它移除无意义的摩擦,把精力留给能力建设。AI 是路线图而不是缆车:冷启动的灵感和从想法到执行的过渡是 AI 的合理位置;攀登本身必须是人的。

另一个要点:"不要在观点尚不清晰时让 AI 给出骨架"——当你自己的视角尚未形成,AI 建议的大纲必然会扭曲作品;通过 AI 躲避挣扎会让你原地打转,落在平庸里;挣扎是走出森林的路。配套引用 Ira Glass 的品味/技能差距:技能永远追不上品味;如果所有精力都花在"做"上而 none 花在"看"上,你会撞上天花板(品味训练是上坡,不能外包)。

Counterpoints & Gaps

  • 这是作者的个人写作经验,不是对照实验。
  • "上坡下坡"的边界因人因项目而异,框架提供的是判断提问而非硬规则。

Pending Jean review

2026-10-30: Brief-first workflow for code-assisted video

来源:AI Briefing 2026-10-30 morning;Eian Lu 的六步视频工作流文章,由 @EianLu 分享。

Eian Lu 的流程依次明确 brief、收集参考影片、制作分镜、按音乐安排节奏、用代码渲染画面、检查缩略图后迭代。作者认为代码更适合图形与文字驱动镜头,写实人物运动仍有局限。该案例与本页已有的创作者流程相互补充:先做创意和事实判断,再把可重复的渲染与检查步骤交给工具。

播放量等结果是作者自述,未独立核实;流程也没有给出统一的质量或成本对照。

Sources (2026-10-30 addendum)

Pending Jean review

2026-10-30 Evening: 像素特效用多版本视觉迭代

来源:AI Briefing 2026-10-30 evening

Hugo Duprez 描述了代码生成像素特效的迭代方法:让 Agent 先生成 5–10 个草稿,渲染为短视频供人检查,再选择一个方向逐步调整细节、节奏和平衡。创作者负责质量判断,并通过设计、电影、摄影和游戏参考积累视觉判断力。

这个案例补充了本页的“小型、可审查产物”原则:生成多个视觉方案可以扩大探索范围,但筛选、审美标准和最终批准仍由创作者负责。它是个人实践描述,没有对比不同工具的质量或时间收益。

Counterpoints & Gaps

  • 单一创作者的经验,不能证明 5–10 个草稿适用于所有项目。
  • 来源没有量化迭代成本或成品质量。

Pending Jean review

Sources (2026-10-30 evening addendum)

Sources

Synthesized from 7 sources

Evolution

1 event
  1. absorbed

    Derived from source material

    This page is currently synthesized from 7 sources.

    From 诗梳风 EP21 — 用 AI 生产内容的复盘之二:到底怎么把好内容翻译给 AI, Ben’s Bites — Is Anthropic the best business in the world?, writerbuilder — What Not to Automate(Hilary Gridley), 2026-10-27 What Not to Automate, 诗梳风-EP21-AI写作复盘To AI-Assisted Creative Production
    Sources: raw/podcasts/诗梳风-EP21-AI写作复盘.md · raw/newsletters/Ben's Bites/2026-10-27 Is Anthropic the best business in the world.md · raw/newsletters/writerbuilder/2026-10-27 What Not to Automate.md · /Users/jean/Documents/Obsidian Vault/raw/newsletters/writerbuilder/2026-10-27 What Not to Automate.md · /Users/jean/Documents/Obsidian Vault/raw/podcasts/诗梳风-EP21-AI写作复盘.md · raw/briefing/AI Briefing/2026-10-30-08-18.md · raw/briefing/AI Briefing/2026-10-30-22-56.md

Linked from