When should you use it?
- You write many articles a month and lose time to research and admin
- Your past articles and trackers already live in folders
- You want help with drafts but publish in your own voice
Not for: Client work whose contract forbids AI or restricts sharing materials; People who only use chat assistants occasionally
What do you need, and what do you get?
You need
- Your back catalog of finished pieces
- Your writing style rules
- A publishing tracker spreadsheet
- A keyword research tool connection
You get
- Keyword shortlists with search data
- A topic table showing overlap with past work and how to differentiate
- Drafts in your style
- An updated publishing schedule
- Template image drafts
How does it work, step by step?
- Scope the folderGive the agent only the working folder, never folders with personal data or unrelated client files.
- Plan from your archiveHave it read every past article and tabulate new topic ideas, overlap and angle, then set a roadmap.
- Teach your styleGive explicit rules such as tone, sentence length and limits on bold text, and feed back your corrections.
- Hand off the trackerTell it to mark pieces published and report what is next instead of updating the sheet yourself.
- Keep the last passRewrite the experience sections in your own words and verify every number and name before submitting.
The prompt
Our own prompt, inspired by 片倉慧@webライター and written to work in Claude Cowork. Values in lime are placeholders.
You are my writing desk assistant. Work only in [folder]. 1) Go through everything in /published, then propose [n] fresh topics as rows: topic | most similar earlier piece | overlap (high/medium/low) | angle that sets it apart. 2) For the topic I pick, draft an outline and first draft following /rules/style.md, leaving clearly marked gaps where my personal experience goes. 3) Update tracker.xlsx: mark [title] as published and tell me what is scheduled next. Do not invent facts or quotes.
Inspired by 片倉慧@webライター: How My Web Writing Workflow Changed After Using Claude Cowork. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The writer finds other tools better for polished images; the agent is used for layout drafts only.
- Check each client's terms before letting the agent read their materials.
Our take
片倉慧, a Japanese freelance web writer on note.com, describes five jobs handed to Claude Cowork: keyword shortlists through a keyword tool, a table checking new topics against past articles, drafts trained on style rules, updates to a publishing spreadsheet and template image drafts, with monthly output reported between forty and fifty articles. The useful insight is the shift named in the piece: from asking a chatbot questions to delegating a task and verifying the result. The archive overlap table is the standout idea for anyone with a back catalog, because it prevents near-duplicate articles before they are written. Limit folder access, respect client terms, and treat the agent as taking over tasks, not responsibility. Output volume is the writer's own report and will depend on niche and editing standards. Keep client-confidential briefs out of shared folders. Review every draft before delivery. Version the style rules file so tone does not drift unnoticed.
Where the time goes back: Copy-pasting between chat and files and maintaining trackers ate the writer's time; the agent reads and saves files directly, so the writer reviews instead.
FAQ
What plan does the writer use?
Where should a beginner start?
Source and credit
Inspired by 片倉慧@webライター. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How My Web Writing Workflow Changed After Using Claude Cowork
- Creator
- 片倉慧@webライター
- Published on
- note.com
- Original date
- Sep 27, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Cowork
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; nothing was sent, filed, purchased or published.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.