iso27diy-corp/Content Factory/Content Factory Implementation.md

2.7 KiB

Content Factory Implementation

1. A Claude Project is created for each of 5 Agents

  • content strategist
  • writer / researcher
  • SEO & distribution specialist
  • Analytics & Feedback
  • Librarian

See PROJECT - Five Agents for role descriptions and instructions.

2. Create Vault Overview Notes

  • One Overview Note per vault section, not one large note.
  • Name them consistently to mirror your vault's folder structure.
  • Create a single short Corpus Index Note with a list of all overview notes, with a one-line description of what they cover.
  • Upload the Corpus Index Note and all Overview Notes to each agent Project. Claude will read the ones it needs and ignore the rest.

See Corpus overview notes.

3. Prepare and maintain a log

The log is your paper trail for the entire cycle. It lives in Obsidian and has two purposes: giving the Analytics agent what it needs in Phase 5, and building a historical record across cycles.

How to use it

  • Fill it in progressively as you move through the phases — don't try to reconstruct it at the end
  • The Editorial Plan and Drafts sections feed Phase 2 and 3
  • The Published Assets section is what you paste into the Analytics prompt in Phase 5
  • The Analytics Report section closes the cycle and is what you paste into the Strategist to open the next one
  • The Carry-Forward Notes section is for you — things that shouldn't get lost between cycles but don't belong in the analytics report

One log note per cycle. After a few cycles you'll have a useful history of what you tried, what worked, and how your thinking evolved.

CYCLE LOG TEMPLATE

## Cycle Log — [Start date] to [End date]

---

### EDITORIAL PLAN
[Paste the approved editorial briefs from Phase 1]

---

### DRAFTS
For each piece:

**[Content title]**
- Brief: [link to or paste of approved brief]
- Draft approved: [date]
- Flags resolved: [list any VALIDATE or SOURCE NEEDED flags and how you resolved them]
- Editor notes: [anything you changed and why]

---

### PUBLISHED ASSETS
For each piece:

**[Content title]**
- Newsletter — [sent / skipped] — [date/time]
- LinkedIn — [posted / skipped] — [date/time] — [link]
- Forum/community — [posted / skipped] — [date/time] — [link]
- Website — [published / skipped] — [date/time] — [URL]
- Deviations from action list: [note anything you changed, skipped, or delayed and why]

---

### PERFORMANCE DATA
[Paste raw data per channel after the measurement window closes]

---

### ANALYTICS REPORT
[Paste the final approved report from the Analytics agent]

---

### CARRY-FORWARD NOTES
[Anything the next cycle should pick up — unresolved flags, 
topics that were dropped, ideas that came up during the cycle]