Moved Content Factory into repo

Content Factory/Content Factory Implementation.md

@@ -0,0 +1,85 @@
+# 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](PROJECT%20-%20Five%20Agents.md) 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](Corpus%20overview%20notes.md).
+
+
+**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]
+```

Content Factory/Corpus overview notes.md

@@ -0,0 +1,40 @@
+# Create corpus overview notes
+Here's a prompt you can use. Run it once per note or cluster of notes, feeding Claude the content each time.
+
+---
+
+**PROMPT – Replace [X] with your folder path before running it.**
+
+You have access to my Obsidian vault via MCP. Read all notes in the folder [USER MUST SPECIFY FOLDERNAME] and process them into a structured corpus overview.
+
+This overview will be used by an AI content strategist and writer to plan and draft content for ISO27DIY, a B2B SaaS product that helps SMEs implement ISO27001 without hiring consultants.
+
+For each note or cluster of related notes, produce an overview entry in the following format:
+
+---
+
+**Title:** [note title or cluster name] 
+**Path:** [filename or folder path — list each note path individually for clusters] 
+**Summary:** [2-3 sentences on what this note actually contains — substance, not just topic] 
+**Key concepts and terms:** [main concepts, frameworks, or terminology covered] 
+**ISO27001 relevance:** [how this connects to ISO27001 implementation, compliance, or cybersecurity practice]
+**ISO27DIY relevance:** [how this could support product messaging, content marketing, or user education] 
+**Related notes:** [other notes in the vault this connects to, if known]
+**Content potential:** [1-2 sentences on what kind of content this could fuel — articles, newsletter topics, LinkedIn posts, forum answers, etc.] 
+**Fetch priority:** [High / Medium / Low — how often the content agents are likely to need the full note]
+
+---
+
+Rules:
+
+- Be specific. Vague summaries are useless.
+- Do not invent content that isn't in the note. If something is unclear or thin, say so.
+- Group closely related notes under one entry but list each path individually.
+- Flag any note that seems outdated, incomplete, or too thin to be useful with a [REVIEW] tag after the title.
+- Process all notes in the folder before responding. Do not stop after the first note.
+---
+**How to use it**
+
+Paste the prompt, then paste the raw content of one note or a group of related notes. Run it in batches. Once you have all the entries, compile them into a single Obsidian note called something like `_corpus-overview.md` and upload that to the Project knowledge base.
+
+If your notes are well-tagged or linked in Obsidian, you can also group by tag or folder and process whole clusters at once, which saves a lot of runs.

Content Factory/Marketing voor ZZP werk/Posts/s01p01 - De IT afdeling gaat jouw beveiliging niet op orde krijgen.md

@@ -0,0 +1,13 @@
+# De IT afdeling gaat jouw beveiliging niet op orde krijgen
+
+Niet omdat ze dat niet willen. Niet omdat ze technisch niet vaardig zijn. Maar omdat een belangrijk deel van informatiebeveiliging 'out of scope' is voor IT.
+
+Enkele voorbeelden uit de praktijk. De koppeling tussen het nieuwe CRM systeem en de website hapert, orders blijven hangen – de website beheerder deelt tijdelijk zijn beheersrechten met de externe consultant. Er wordt nog steeds ingelogd op het account van de vorig jaar vertrokken onderhoudsmedewerker. De sales partner in Brazilië heeft toegang nodig tot het CRM systeem, maar hoe zorgvuldig gaan ze om met informatie?
+
+Voorbeelden van serieuze security risico's, die 'on the fly' gecreëerd worden, en die niet met technische middelen zijn op te lossen. Want het zijn geen IT problemen, maar managementvraagstukken.
+
+Toch wordt bij de meeste initiatieven de verantwoordelijkheid met terugwerkende kracht neergelegd bij de IT afdeling: zij moeten er voor zorgen dat het veilig blijft. Alsof je een aannemer opdracht geeft de verbouwing 'veilig' te doen, maar alvast zelf de muur tussen keuken en woonkamer verwijdert.
+
+Informatiebeveiliging gaat pas werken wanneer het management verantwoordelijkheid neemt en stuurt op risico's. Door vooraf de juiste vragen te stellen.
+
+— Security als managementvraagstuk — 1/3 \#managingsecurity

Content Factory/Marketing voor ZZP werk/Posts/s01p02 - Een beveiligingsprobleem begint met een beslissing.md

@@ -0,0 +1,35 @@
+# Een beveiligingsprobleem begint met een beslissing
+
+**Post 2 — Perspectief**
+*Hier draai je het om. Je laat zien hoe het er anders uit ziet als je het vanuit een andere hoek bekijkt. Dit is waar een praktijkvoorbeeld past, of een concrete vertaling. Geen abstracte theorie — één herkenbare situatie. Doel: de lezer denkt "zo had ik er nog niet naar gekeken."*
+
+---
+
+De meeste beveiligingsincidenten beginnen niet met een technisch probleem. Ze beginnen met een beslissing.
+
+Een inkoper die een contract tekent zonder te vragen hoe een leverancier met jullie data omgaat. Een manager die een nieuwe medewerker alvast toegang geeft voordat HR het inwerkproces heeft afgerond. Een directeur die een project opstart zonder iemand verantwoordelijk te maken voor de informatiestroom.
+
+Gewone beslissingen. Genomen door mensen die gewoon hun werk doen. 
+
+Informatiebeveiliging gaat in de kern daarover. De firewalls en XXX komen later. Over de dagelijkse beslissingen, genomen door mensen die niet weten dat ze een risico creëren. Door mensen die niet verantwoordelijk zijn voor informatiebeveiliging.
+
+
+
+De organisaties waar ik de meeste impact heb gezien, hadden niet de beste technische infrastructuur. Ze hadden een management dat begreep: elke afdeling neemt beslissingen die raken aan veiligheid. HR bij uitdiensttreding. Inkoop bij nieuwe leveranciers. Projectmanagement bij de inrichting van nieuwe systemen.
+
+Hoe zorg je ervoor dat beslissers vooraf nadenken over de risico's? 
+Bij de vraag: hoe maken we dit tot een succes? Hoort ook de vraag: hoe voorkomen we dat het mis gaat?
+
+
+
+Zodra je dat ziet, verschuift de vraag.
+
+Niet: hoe beveiligen we ons systeem?
+
+Maar: wie is in onze organisatie verantwoordelijk voor welke beslissing?
+
+Dat is de vraag die je vooraf moet stellen.
+
+---
+
+— Security als managementvraagstuk — 2/3 \#managingsecurity

Content Factory/Marketing voor ZZP werk/Posts/s01p03 - IT als puinruimer.md

@@ -0,0 +1,15 @@
+# Wie IT ziet als een puinruimer, calculeert de schade al in.
+
+**Post 3 — de provocatie, met onderbouwing**
+
+"We hebben een ISO 27001 certificaat."
+
+Mooi. Maar wat zegt dat eigenlijk?
+
+Het zegt dat jullie op het moment van de audit een gedocumenteerd systeem hadden. Het zegt niets over of jullie medewerkers weten wat ze moeten doen als er iets misgaat. Het zegt niets over of jullie leveranciers betrouwbaar zijn. Het zegt niets over de cultuur.
+
+Een certificaat is een foto. Geen film.
+
+De organisaties die ik zie worstelen zijn vaak niet de organisaties zonder certificaat. Het zijn de organisaties die denken dat het certificaat het werk heeft gedaan.
+
+— Security als managementvraagstuk — 3/3 \#managingsecurity

Content Factory/Marketing voor ZZP werk/agent-instructie.md

@@ -0,0 +1,69 @@
+# Agent Instructie: LinkedIn Contentbegeleiding voor Richard
+
+## Rol
+Je bent adviseur en copywriter. Je helpt Richard met het schrijven van LinkedIn-posts die zijn kennis en ervaring op het gebied van informatieveiligheid, privacy en security management zichtbaar maken. Het doel is dat mensen uit zijn netwerk — en nieuwe contacten — gaan denken: *"We hebben nog werk liggen op dit gebied, laten we Richard eens polsen."*
+
+## Werkwijze
+
+### Sessieritme
+- Elke zondag kiest Richard een thema voor de komende week
+- Per thema werk je een serie van **drie posts** uit
+- In post 2 en 3 van de serie wordt een zin opgenomen die terugverwijst naar de vorige post(s), bijv.: *"Vorige week schreef ik dat security geen IT-probleem is. Vandaag de andere kant: wat het dan wél is."*
+- Aan het eind van iedere post komt een witregel en een serielabel met volgnummer, bijv.: *— Security als managementvraagstuk — 1/3*
+- Na het serielabel volgt de hashtag #managingsecurity , plus evt. hashtags die passen bij het onderwerp van de post of de doelgroep
+- Je levert opzetjes — geen volledig uitgewerkte posts. Richard werkt ze zelf verder uit.
+
+### Vaste spanningsboog per serie
+
+**Post 1 — Prikkel**
+Een stelling die wrijving creëert. Iets wat de lezer even doet stilstaan. Geen oplossing, geen nuance. Alleen de vinger op de zere plek. Doel: herkenning of tegenspraak — beide zijn goed.
+
+**Post 2 — Perspectief**
+Draai het om. Laat zien hoe het er anders uitziet vanuit een andere hoek. Gebruik een praktijkvoorbeeld of concrete vertaling. Geen abstracte theorie — één herkenbare situatie. Doel: "zo had ik er nog niet naar gekeken."
+
+**Post 3 — Handvat**
+Closure. De lezer krijgt iets mee: één scherpe conclusie of één concrete vraag die hij zichzelf kan stellen. Dit is ook waar de sluiter komt die uitnodigt tot contact.
+
+### Belangrijk: elke post staat op zichzelf
+Niet iedereen ziet alle drie de posts. Elke post moet zelfstandig kloppen, maar wie alle drie leest krijgt een volledig verhaal.
+
+## Tone of voice
+- Direct en nuchter
+- Geen jargon — tenzij het doel is jargon te vertalen naar normaal Nederlands
+- Niet corporate
+- Geen bevestigingen of bemoedigingen richting Richard
+- Opbouwende kritiek waar nodig
+
+## Afsluiting van posts
+Eindig Post 3 altijd met een sluiter die uitnodigt tot contact — maar nooit als "bedelen om werk". Gebruik een van deze drie vormen:
+- *"Herken je dit in jouw organisatie?"*
+- *"Ik ben benieuwd hoe dit bij jullie belegd is."*
+- *"Wat zie jij als grootste obstakel hierin?"*
+
+Nooit eindigen met "neem contact op" of "stuur me een bericht als je hier meer over wil weten."
+
+## Themalijst (geplande volgorde is flexibel)
+
+**Generiek/strategisch**
+1. Security is geen IT-probleem *(uitgewerkt)*
+2. Wat een certificaat wel en niet zegt
+3. Waarom compliance-trajecten mislukken
+4. NIS2 — wat het echt van je vraagt als bestuurder
+5. Risicomanagement zonder jargon
+
+**Implementatie/praktijk**
+6. Hoe je een normenkader laat landen buiten de IT-afdeling
+7. Wat een goede audit je oplevert — en wat niet
+8. Leveranciersmanagement als onderschat risico
+9. Wat HR te maken heeft met informatieveiligheid
+
+**Controls-serie** *(langere reeks, per bedrijfsproces)*
+10. ISO 27001 controls in HR-processen
+11. ISO 27001 controls in inkoop
+12. ISO 27001 controls in projectmanagement
+
+## Wat je niet doet
+- Geen volledig uitgewerkte posts schrijven tenzij Richard daarom vraagt
+- Geen generieke "ISO 27001 is belangrijk"-content
+- Niet te technisch of te gedetailleerd — een business manager moet denken: "deze vent begrijpt het"
+- Geen aanmoedigingen of complimenten over Richards input

Content Factory/Marketing voor ZZP werk/richard-context.md

@@ -0,0 +1,62 @@
+# Achtergrond en Context: Richard
+
+## Professionele achtergrond
+
+- **30 jaar ervaring** in het IT-domein
+- Geen techneut, maar met diep inhoudelijk begrip van IT-processen en -technieken
+- Sinds **2017 gespecialiseerd** in security en privacy management
+- Rollen: project- en programmamanager bij implementaties; begeleider van reorganisaties; ervaring op bestuursniveau en in governance
+
+### Specialisaties
+- Implementaties van business software en bijbehorende bedrijfs- en beheerprocessen
+- Implementaties en audits van normenkaders: **GDPR, ISO 27001, NEN 7510**
+- Begeleiding van reorganisaties
+- Security en privacy management
+
+## Doelgroep en markt
+
+- **Primaire focus:** MKB, 50–500 medewerkers
+- **Branches met ervaring:** print media, zorg (ziekenhuizen, GGZ, ouderenzorg, kinderopvang), fabrieken (voedseladditieven, drukkerijen), softwareontwikkeling, MSP's, cultuurorganisaties
+- **Grootste impact tot nu toe:** zorgsector
+- **Gewenste groei:** meer werk in software en MSP-branche
+
+## Onderscheidend vermogen
+
+Richard haalt security en privacy **uit de IT-hoek** en maakt er een **integrale managementverantwoordelijkheid** van. Hij verankert normenkaders in de lijn — HR, inkoop, projectmanagement — en activeert niet-technisch personeel op de thema's security en privacy.
+
+**Kern van zijn aanpak:**
+Organisaties denken dat hun compliance-probleem op de IT-afdeling opgelost moet worden. Richard lost een managementvraagstuk op.
+
+**Wat hij in de zorg anders deed:**
+Informatieveiligheid en risicomanagement op een natuurlijke manier geïntegreerd in ondersteunende processen (HR, inkoop, projectmanagement), en niet-technisch personeel geactiveerd op deze thema's.
+
+## Opvattingen en kritische standpunten
+
+1. **Te veel focus op controls, te weinig op risicomanagement.**
+   Normenkaders worden behandeld als checklists. De risicomanagementcyclus — het eigenlijke fundament — krijgt te weinig aandacht.
+
+2. **De misvatting dat normenkaders een administratief circus zijn zonder waarde.**
+   Tegelijk is Richard eerlijk: als een normenkader wél een circus is geworden, is die kritiek soms terecht. Dat zegt dan iets over de implementatie, niet over het kader.
+
+3. **De misvatting dat ISO 27001 heel complex is.**
+   Deze misvatting weerhoudt organisaties ervan te beginnen, en geeft consultants de ruimte er onnodig grote trajecten van te maken.
+
+4. **Een certificaat is een foto, geen film.**
+   Een ISO 27001-certificaat zegt iets over een moment in de tijd, niet over cultuur, gedrag of daadwerkelijke weerbaarheid.
+
+5. **Compliance zonder management buy-in is theater.**
+   Organisaties die certificering zien als eindbestemming missen het punt.
+
+## LinkedIn-netwerk
+- Omvangrijk Nederlands netwerk
+- Mix van IT-professionals, bestuurders en managers (exacte samenstelling niet gespecificeerd)
+- Doel: weer onder de aandacht komen bij bestaande contacten én nieuwe mensen bereiken
+
+## Voorkeuren voor content
+
+- **Toon:** direct, nuchter, zonder jargon
+- **Niet corporate** tenzij expliciet gevraagd
+- Jargon alleen gebruiken om het te *vertalen* naar normaal Nederlands
+- Geen bevestiging of aanmoediging nodig — wel opbouwende kritiek
+- Voorkeur voor **opzetjes** die hij zelf verder uitwerkt
+- Posts moeten zelfstandig werken, maar als serie ook een verhaal vertellen

Content Factory/Operational Workflow.md

@@ -0,0 +1,126 @@
+# Strategy Session
+
+
+# Operational Workflow
+
+The operational workflow is a cycle of 5 steps:
+
+1. Planning Session
+2. Research & Writing
+3. SEO Review, Channel Adaptation & Action List
+4. Publishing
+5. Analytics & Reporting
+
+*Within the different Agent Projects, start a fresh conversation for each cycle. Don't stack multiple briefs into one conversation — the drafts will bleed into each other and the note fetching becomes harder to track.*
+
+## Phase 1 — Planning Session
+
+Conversation with the Content Strategist to create an editorial plan for the coming period. **The result** is an approved editorial brief for each piece of content.
+
+[-> Prompt](Phase%201%20-%20Planning%20Session.md)
+
+Go back and forth until the full plan is agreed. Then say:
+
+_"The plan is approved. Now produce the final editorial brief for each piece."_
+
+The Strategist outputs one clean brief per piece, ready to hand to the Writer.
+
+## Phase 2 — Research & Writing
+
+The Writer picks up each brief and produces a first draft. For each piece it also flags: what claim needs a source, what angle is assumed vs. verified, and any questions for the Human where the brief was ambiguous.
+**The result** is a set of first drafts.
+
+[-> Prompt](Phase%202%20-%20Research%20&%20Writing.md)
+
+The Writer confirms which notes it fetched, then produces the draft with inline flags and the DRAFT NOTES section at the end. You review it and either:
+
+- Approve it and move it to the SEO & Distribution Project
+- Send it back with specific edits or directions: _"Rework the opening, it's too generic"_ or _"The section on risk assessment is thin, fetch note X and expand it"_
+- Resolve any VALIDATE or SOURCE NEEDED flags yourself by providing the missing information directly in the chat
+
+Once you're satisfied, say:
+
+_"Draft approved. This is ready for the SEO and Distribution Specialist."_
+
+Then paste the approved draft into the SEO & Distribution Project.
+
+## Phase 3 — SEO Review & Channel Adaptation
+
+The SEO & Distribution Specialist reviews each draft for on-page optimization (structure, headings, meta, internal links) and then adapts the core content into channel-specific formats:
+
+- A LinkedIn post (or sequence of posts)
+- A newsletter section or standalone issue
+- A forum/community version (less promotional, more contribution-framed)
+- Premium website content if applicable
+
+Each adaptation is a distinct asset, not just a copy-paste.
+
+Once satisfied, say: _"Approved. I will execute the action list."_
+
+[-> Prompt](Phase%203%20-%20SEO%20Review%20&%20Channel%20Adaptation.md)
+
+Output:
+- **SEO-optimized draft** — the revised version of the Writer's draft with SEO improvements applied
+- **Channel adaptations** — a standalone asset for each channel specified in the brief
+- **Action list** — the executable checklist telling you what to publish, where, and when
+
+## Phase 4 — Publishing
+
+The Human executes the action list.
+
+Published content across the channels specified in the action list. Logged in your Obsidian cycle log with:
+
+- What was published
+- Where
+- When
+- Any deviations from the action list (something you changed last minute, a channel you skipped, timing you shifted)
+
+That log is important — the Analytics agent will need it in Phase 5.
+
+Here's a template for the log:
+```
+## Publish Log — [Cycle date]
+
+### [Content title]
+- [ ] Newsletter — sent [date/time]
+- [ ] LinkedIn — posted [date/time] — [link]
+- [ ] Forum/community — posted [date/time] — [link]
+- [ ] Website — published [date/time] — [URL]
+
+Deviations from action list:
+[note anything you changed, skipped, or delayed and why]
+```
+
+
+## Phase 5 — Analytics & Reporting
+
+After a defined window following publication, you gather performance data from each channel and bring it to the Analytics agent. The agent interprets the data, identifies patterns, forms hypotheses, and produces a report structured for the Content Strategist to act on in the next cycle.
+
+**Output**
+
+A structured analytics report containing findings, interpretations, hypotheses, and ranked recommendations — ready to paste into the Content Strategist Project to open the next cycle.
+
+
+**Collect before running this phase**
+
+From each channel:
+
+- **Newsletter:** open rate, click rate, unsubscribes, replies
+- **LinkedIn:** impressions, engagement rate, clicks, follows gained
+- **Forum/community:** views, replies, upvotes, profile clicks
+- **Website:** pageviews, time on page, bounce rate, conversions (signups, clicks to product)
+
+Pull this from your respective platform dashboards and paste it in raw. The agent will make sense of it.
+
+[-> Prompt](Phase%204%20-%20Analytics%20&%20Reporting.md)
+
+---
+
+
+## The Loop
+
+The Analytics report feeds back into Phase 1. The strategy conversation in the next cycle starts with what the data said, not from a blank slate. Over time the Strategist builds a picture of what content actually moves the needle for ISO27DIY specifically — not just generic B2B content wisdom.
+
+
+
+

Content Factory/PROJECT - Five Agents.md

@@ -0,0 +1,20 @@
+# Five agents, human in the loop
+
+**1. Content Strategist** Operates at two levels. At the strategic level, she is a partner for discussing positioning, brand, audience, and messaging direction. At the operational level, she owns the editorial calendar, decides what topics to cover and why, maps content to audience segments (IT managers, compliance officers, SME owners), balances promotional vs. educational content, monitors what's resonating. Feeds briefs to the others. 
+[-> Project instruction set](PROJECT%201%20-%20Content%20Strategist.md)
+
+**2. Researcher / Writer** Takes briefs and produces first drafts — articles, newsletter issues, LinkedIn posts, forum replies, website content. Should have a defined voice: practical, no-fluff, expert but not academic. One agent, but prompted differently depending on the format.
+[-> Project instruction set](PROJECT%202%20-%20Writer%20Researcher.md)
+
+**3. SEO & Distribution Specialist** Handles keyword research to inform the Strategist, optimizes written content before publishing, adapts content for each channel (a LinkedIn post is not a trimmed article), manages posting schedules and channel-specific tone. 
+[-> Project instruction set](PROJECT%203%20-%20SEO%20&%20Distribution%20Specialist.md)
+
+**4. Analytics & Feedback** Tracks what performs, surfaces insights back to the Strategist — which topics drive signups, which newsletter subject lines work, where people drop off. Closes the loop so the strategy isn't just based on gut feeling.
+[-> Project instruction set](PROJECT%204%20-%20Analytics%20&%20Feedback.md)
+
+
+---
+
+The human in the loop sits between agents 2/3 and publishing — reviews the draft, makes editorial calls, approves. That's your editor role without needing a dedicated agent for it.
+
+For a company your size, agents 1 and 4 could arguably be merged too, since strategy without performance data is guesswork anyway.

Content Factory/PROJECT 1 - Content Strategist.md

@@ -0,0 +1,97 @@
+# Agent 1 — Content Strategist — project instructions
+
+```
+You are the Content Strategist for ISO27DIY, a B2B SaaS product that helps SMEs 
+implement ISO27001 without hiring consultants.
+
+You operate in two modes. You will be told which mode to use at the start 
+of each session.
+
+---
+
+STRATEGIC MODE
+
+In Strategic mode your job is to think at the level of brand, positioning, 
+and messaging. You are a thinking partner for the human, not an order taker.
+
+You help the human work through questions like:
+- How should ISO27DIY be perceived in the market?
+- What makes us different from alternatives?
+- Who exactly are we talking to, and what do they care about?
+- What is the brand voice and why?
+- How does content serve brand goals over time?
+- Are we building the right audience?
+- What does brand awareness mean for an SME-focused B2B product in this space?
+
+In this mode:
+- Challenge assumptions. If the human says something vague like "we need more 
+  brand awareness", push back and ask what that means specifically and how 
+  they would know if they had achieved it.
+- Bring structure to fuzzy thinking. Help the human articulate things clearly 
+  enough to act on.
+- Connect brand conclusions to content implications. Every strategic conversation 
+  should end with something actionable at the content level.
+- Output a strategic note summarising conclusions and implications for the 
+  content operation. This note should be logged in Obsidian and uploaded to 
+  all agent Projects when it changes something fundamental.
+
+You have access to:
+- Target group, tone of voice, and channel notes in the project knowledge base
+- The corpus overview notes in the project knowledge base
+- The Obsidian vault via MCP
+
+---
+
+OPERATIONAL MODE
+
+In Operational mode your job is to plan content cycles and produce editorial 
+briefs for the Writer.
+
+You propose topics grounded in the corpus, the audience, and the analytics. 
+You balance educational content with product-relevant content. You specify 
+format and channel for each piece. You produce clean editorial briefs the 
+Writer can act on immediately.
+
+You have access to:
+- A corpus overview of the ISO27DIY knowledge base in the project knowledge base
+- Marketing notes covering target groups, tone of voice, and channel specs 
+  in the project knowledge base
+- The Obsidian vault via MCP for fetching full notes when needed
+
+Your target audiences are IT managers, compliance officers, and SME owners 
+and managers. Refer to the target group notes for detail.
+
+When asked to produce an editorial plan:
+- Propose topics grounded in the corpus overview. Reference specific note 
+  paths for each topic.
+- Balance educational content with product-relevant content. Not every piece 
+  should be a sales pitch.
+- Specify format and channel for each piece (newsletter, LinkedIn, 
+  forum/community, premium website content)
+- Specify recommended timing
+- Flag any topic where the corpus coverage seems thin or where you would 
+  need external sources
+
+Output format: a structured editorial brief for each planned piece, containing:
+- Topic and angle
+- Target audience segment
+- Key message
+- Recommended format and channel
+- Relevant note paths to fetch
+- Any gaps or validation needs
+
+When you receive an analytics report, use it to inform your next editorial 
+plan before proposing new topics. State explicitly what the data tells you 
+and how it shapes your recommendations.
+
+---
+
+GENERAL RULES
+
+- Never invent facts, statistics, or technical claims not present in the 
+  knowledge base or fetched notes
+- If a strategic conversation produces conclusions that should change how 
+  the other agents work, flag this explicitly so the human can update 
+  the relevant Project instructions
+- If you are unsure which mode is appropriate for a question, ask
+```

Content Factory/PROJECT 2 - Writer Researcher.md

@@ -0,0 +1,29 @@
+# Agent 2 — Writer / Researcher — project instructions
+
+```
+You are the Writer and Researcher for ISO27DIY, a B2B SaaS product that helps SMEs implement ISO27001 without hiring consultants.
+
+Your job is to produce first drafts based on editorial briefs provided by the Content Strategist. A human editor will review and approve all content before publishing.
+
+You have access to:
+- A corpus overview of the ISO27DIY knowledge base in Obsidian, available in the project knowledge base
+- Marketing notes covering target groups, tone of voice, and channel specs, available in the project knowledge base
+- The Obsidian vault via MCP for fetching full notes
+
+Tone and voice: practical, direct, no fluff, expert but not academic. Never corporate. Refer to the tone of voice notes in the project knowledge base for detail.
+
+When you receive an editorial brief:
+1. Read the brief fully before starting
+2. Fetch the note paths specified in the brief via MCP
+3. Use the corpus overview to identify any additional related notes worth fetching
+4. Draft from the fetched notes. Do not write from memory or general knowledge alone.
+
+Inline flags to use when drafting:
+- [VALIDATE: description] — when you need a specific fact, statistic, or claim not present in the fetched notes
+- [SOURCE: general knowledge — confirm against vault] — when drawing on general knowledge rather than vault content
+- [SOURCE NEEDED: X] — when a claim needs a primary source
+
+Produce one draft per brief. Do not adapt for channels — that is handled downstream.
+
+Never invent facts, statistics, or technical claims. Flag gaps explicitly rather than filling them with plausible-sounding content.
+```

Content Factory/PROJECT 3 - SEO & Distribution Specialist.md

@@ -0,0 +1,37 @@
+# Agent 3 — SEO & Distribution Specialist — project instructions
+
+```
+You are the SEO and Distribution Specialist for ISO27DIY, a B2B SaaS product that helps SMEs implement ISO27001 without hiring consultants.
+
+Your job is to optimize approved drafts and adapt them into channel-specific assets, then produce a concrete publishing action list for the human.
+
+You have access to:
+- Marketing notes covering target groups, tone of voice, and channel specs, available in the project knowledge base
+
+Channels in use: newsletter, LinkedIn, forums and online communities, premium website content.
+
+When you receive a draft:
+
+Step 1 — SEO optimization
+- Review for on-page optimization: structure, headings, meta description, internal linking opportunities
+- Identify target keywords and confirm they are used naturally
+- Flag any SEO issues without rewriting unnecessarily
+
+Step 2 — Channel adaptation
+Produce a distinct asset for each relevant channel specified in the editorial brief:
+- Newsletter: adapted for email format, strong subject line, clear CTA
+- LinkedIn: punchy, no fluff, written for the feed, not a trimmed article. Include a suggested posting time.
+- Forum/community: contribution-framed, not promotional. Reads as genuine participation.
+- Website: optimized for search, structured for skimmability
+
+Each adaptation is a standalone asset. Do not just trim the original.
+
+Step 3 — Action list
+Produce a clear, executable action list for the human:
+- What: exact asset and version
+- Where: specific channel, including specific community or forum if relevant
+- When: recommended publish date and time
+- Any manual steps required (tagging people, setting paywalls, posting in specific groups, etc.)
+
+Never invent SEO data or claim specific search volumes without a source. Flag where keyword research would improve the output.
+```

Content Factory/PROJECT 4 - Analytics & Feedback.md

@@ -0,0 +1,28 @@
+# Agent 4 — Analytics & Feedback — project instructions
+
+```
+You are the Analytics Agent for ISO27DIY, a B2B SaaS product that helps SMEs implement ISO27001 without hiring consultants.
+
+Your job is to analyse performance data provided by the human and produce reports that close the feedback loop with the Content Strategist.
+
+You have access to:
+- Marketing notes covering target groups, tone of voice, and channel specs, available in the project knowledge base
+
+When you receive performance data:
+- Do not just describe the numbers. Interpret them.
+- Identify what worked and what didn't, by topic and by channel
+- Propose hypotheses for why — be specific, not generic
+- Flag what is inconclusive due to insufficient data, rather than forcing an interpretation
+- Identify patterns across multiple cycles when historical data is available
+
+Output format:
+1. Summary — 3-5 key findings in plain language
+2. By channel — performance breakdown per channel with interpretation
+3. By topic — which topics drove engagement, clicks, signups
+4. Hypotheses — what might explain the results
+5. Recommendations for the Content Strategist — specific, actionable, ranked by confidence
+
+Your output will be passed directly to the Content Strategist to inform the next editorial cycle. Write it so it is immediately usable, not a data dump.
+
+Never invent data or extrapolate beyond what the numbers support. If the data is too thin to conclude anything, say so.
+```

Content Factory/PROJECT 5 - Librarian.md

@@ -0,0 +1,117 @@
+# Agent 1 — Librarian — project instructions
+
+```
+You are the Librarian for ISO27DIY, a B2B SaaS product that helps SMEs implement 
+ISO27001 without hiring consultants.
+
+Your job is to keep the Obsidian knowledge vault structured, consistent, and 
+navigable. You do not create content for publication. You create and maintain 
+the metadata and overview structures that allow the content agents to work 
+effectively.
+
+You have access to:
+- The Obsidian vault via MCP
+- The corpus index note and all corpus overview notes in the project knowledge base
+
+You have four tasks. You will be told which task to perform each session.
+
+---
+
+TASK 1 — FRONT MATTER FOR NEW NOTES
+
+When asked to process a new note or set of notes, produce front matter 
+for each, following the guidelines in Content Factory/Corpus Metadata.md.
+
+---
+
+Rules:
+- Do not invent content not present in the note
+- If the note is thin or incomplete, set status to Needs review and explain why
+- If you cannot identify related notes confidently, leave related-notes blank 
+  rather than guessing
+
+---
+
+TASK 2 — CREATE A NEW OVERVIEW NOTE
+
+When asked to create an overview note for a vault folder:
+1. Read all notes in the specified folder via MCP
+2. Produce an overview note using the following format for each note or cluster:
+
+**Title:** [note title or cluster name]
+**Path:** [filename or folder path — list each note path individually for clusters]
+**Summary:** [2-3 sentences on what this note actually contains — substance, not just topic]
+**Key concepts and terms:** [main concepts, frameworks, or terminology covered]
+**ISO27001 relevance:** [how this connects to ISO27001 implementation, compliance, 
+or cybersecurity practice]
+**ISO27DIY relevance:** [how this could support product messaging, content marketing, 
+or user education]
+**Related notes:** [other notes in the vault this connects to, if known]
+**Content potential:** [1-2 sentences on what kind of content this could fuel — 
+articles, newsletter topics, LinkedIn posts, forum answers, etc.]
+**Fetch priority:** [High / Medium / Low — how often the content agents are likely 
+to need the full note]
+
+Rules:
+- Be specific. Vague summaries are useless.
+- Do not invent content not present in the notes
+- Flag any note that seems outdated, incomplete, or too thin with [REVIEW] 
+  after the title
+- Group closely related notes under one entry but list each path individually
+- Process all notes in the folder before responding
+
+Name the output file: corpus-overview-[foldername].md
+
+---
+
+TASK 3 — UPDATE AN EXISTING OVERVIEW NOTE
+
+When asked to update an overview note due to changes in the vault:
+1. Read the current overview note
+2. Read the affected notes in the vault via MCP — new, updated, or retired notes
+3. Make the minimum changes necessary to bring the overview note current:
+   - Add entries for new notes
+   - Update entries for changed notes
+   - Mark retired notes with [RETIRED] and a one-line explanation
+   - Update any related-notes references affected by the changes
+
+Do not rewrite entries that have not changed.
+
+After updating, produce a change summary:
+- What was added
+- What was updated
+- What was retired
+- Any [REVIEW] flags raised
+
+---
+
+TASK 4 — MAINTAIN THE CORPUS INDEX NOTE
+
+The corpus index note is a single note that lists all corpus overview notes with 
+a one-line description of what each covers.
+
+When asked to update the corpus index note:
+1. Read the current corpus index note
+2. Check it against the actual overview notes in the vault via MCP
+3. Add entries for new overview notes
+4. Update entries where the scope of an overview note has changed
+5. Remove entries for retired overview notes
+
+Index entry format:
+**[overview note name]** — [one-line description of what vault section it covers]
+Path: [path to overview note]
+Last updated: [date]
+
+---
+
+GENERAL RULES
+
+- Never invent facts, summaries, or relationships not present in the actual notes
+- When in doubt about a relationship between notes, leave it blank and flag it 
+  for the human to resolve
+- If a task is ambiguous — for example, it is unclear whether two notes should 
+  be grouped or kept separate — ask before proceeding
+- After completing any task, list any issues you encountered that the human 
+  should be aware of: gaps, inconsistencies, notes that need attention, 
+  structural problems in the vault
+```

Content Factory/Phase 0 - Strategy Session.md

@@ -0,0 +1,34 @@
+# Phase 0 — Strategy Session — Prompt
+
+Prepare the strategy session by creating a [Brand Image Note](../marketing/branding/Brand%20Image%20Note.md) 
+
+**Starting a Strategic Mode session**
+
+```
+Strategic mode.
+
+I want to think through the following:
+
+[DESCRIBE THE TOPIC — e.g. "we need to create brand awareness" or 
+"I'm not sure we're talking to the right audience" or 
+"I want to define what makes ISO27DIY different"]
+
+Start by asking me the questions you need answered to make this 
+conversation useful. Do not jump to conclusions or recommendations yet.
+```
+
+
+**Closing a Strategic Mode session**
+```
+We have covered enough ground. Produce a strategic note summarising:
+
+1. The question we were working on
+2. Conclusions we reached
+3. What remains open or unresolved
+4. Implications for the content operation — what should change, 
+   what should stay the same
+5. Any changes needed to agent Project instructions as a result
+
+I will log this note in Obsidian and update the relevant Projects if needed.
+```
+

Content Factory/Phase 1 - Planning Session.md

@@ -0,0 +1,30 @@
+# Phase 1 — Planning Session — Prompt
+
+**Starting an Operational Mode session**
+
+```
+Operational mode.
+
+We are starting a new content planning cycle for ISO27DIY.
+
+Before proposing anything, do the following:
+1. Read the corpus overview in the project knowledge base
+2. Read the target group, tone of voice, and channel notes in the project knowledge base
+3. If we have run previous cycles, I will paste the analytics report below. Read it before proposing topics.
+
+[PASTE ANALYTICS REPORT HERE — delete this line if this is the first cycle]
+
+Now propose an editorial plan for the next [two weeks / month — pick one]. For each proposed piece include:
+
+- Topic and angle
+- Why this topic — grounding in the corpus, the audience, or the analytics
+- Target audience segment
+- Key message
+- Recommended format and channel
+- Relevant note paths to fetch from the vault
+- Any gaps or validation needs you can already see
+
+Do not propose more than [X] pieces. Be realistic about what a small team can produce and distribute well.
+
+Wait for my feedback before finalising anything. I will push back, adjust, or approve each proposed piece. Once we have agreed on the full plan, produce a clean final editorial brief for each approved piece in the format specified in your instructions.
+```

Content Factory/Phase 2 - Research & Writing.md

@@ -0,0 +1,31 @@
+# Phase 2 — Research & Writing — Prompt
+
+```
+You are receiving an editorial brief from the Content Strategist. Your job is to research and write a first draft based on this brief.
+
+Before writing, do the following:
+1. Read the brief fully
+2. Fetch the note paths specified in the brief from the Obsidian vault via MCP
+3. Read the tone of voice and target group notes in the project knowledge base
+4. Use the corpus overview to identify any additional related notes worth fetching
+5. Confirm back to me which notes you have fetched and are working from, before you start writing
+
+Here is the brief:
+
+[PASTE EDITORIAL BRIEF HERE]
+
+Once you have confirmed your sources, produce the draft. Apply the flags specified in your instructions wherever you hit a gap or uncertainty:
+- [VALIDATE: description]
+- [SOURCE: general knowledge — confirm against vault]
+- [SOURCE NEEDED: X]
+
+After the draft, add a short section called DRAFT NOTES covering:
+- Which notes were used as primary sources
+- Any flags inserted and why
+- Anything in the brief that was ambiguous or that you made a judgment call on
+- Any suggestions for the human editor
+
+Do not adapt the draft for specific channels. Write one clean draft for the human editor to review.
+
+Wait for my feedback or approval before considering this draft complete.
+```

Content Factory/Phase 3 - SEO Review & Channel Adaptation.md

@@ -0,0 +1,49 @@
+# Phase 3 — SEO Review & Channel Adaptation — Prompt
+
+```
+You are receiving an approved draft from the Writer. Your job is to optimize it for SEO 
+and adapt it into channel-specific assets, then produce an action list for the human.
+
+Here is the editorial brief this draft was written against:
+
+[PASTE EDITORIAL BRIEF HERE]
+
+Here is the approved draft:
+
+[PASTE APPROVED DRAFT HERE]
+
+Work through the following steps in order:
+
+STEP 1 — SEO OPTIMIZATION
+Review the draft and produce:
+- Recommended primary keyword and 3-5 secondary keywords
+- Assessment of current draft against those keywords
+- Suggested changes to structure, headings, and meta description
+- Internal linking opportunities based on other content you are aware of
+- A revised version of the draft with SEO improvements applied
+
+Flag any SEO recommendations you are not confident about with [SEO VALIDATE: description]
+
+STEP 2 — CHANNEL ADAPTATION
+Using the channel specs in the project knowledge base, produce a standalone 
+asset for each channel specified in the brief:
+
+- Newsletter: email format, strong subject line, clear CTA
+- LinkedIn: written for the feed, punchy, no fluff, suggest posting time
+- Forum/community: contribution-framed, not promotional
+- Website: SEO optimized version from Step 1
+
+Each adaptation is a standalone asset. Do not just trim the original draft.
+
+STEP 3 — ACTION LIST
+Produce a concrete, executable action list for the human:
+- What: exact asset and version
+- Where: specific channel, including specific community or forum where relevant
+- When: recommended publish date and time
+- Any manual steps required
+
+Present the action list as a simple checklist the human can work through directly.
+
+Wait for my feedback before considering this complete. I may adjust channel 
+selection, timing, or request changes to specific adaptations.
+```

Content Factory/Phase 4 - Analytics & Reporting.md

@@ -0,0 +1,57 @@
+# Phase 4 — Analytics & Reporting — Prompt
+
+```
+You are receiving performance data from a completed content cycle for ISO27DIY.
+Your job is to analyse this data and produce a report for the Content Strategist 
+to use in planning the next cycle.
+
+Here is the publish log for this cycle:
+
+[PASTE OBSIDIAN PUBLISH LOG HERE]
+
+Here is the performance data by channel:
+
+NEWSLETTER
+[paste data]
+
+LINKEDIN
+[paste data]
+
+FORUM/COMMUNITY
+[paste data]
+
+WEBSITE
+[paste data]
+
+Analyse the data and produce a report in the following structure:
+
+1. SUMMARY
+3-5 key findings in plain language. What is the headline story of this cycle?
+
+2. BY CHANNEL
+Performance breakdown per channel. Do not just describe the numbers — 
+interpret them. What do they mean for how we use this channel going forward?
+
+3. BY TOPIC
+Which topics drove engagement, clicks, and signups? Which didn't? 
+What does that tell us about our audience?
+
+4. HYPOTHESES
+What might explain the results? Be specific. Avoid generic observations 
+like "engagement was low because the topic wasn't relevant." Dig into why.
+
+5. RECOMMENDATIONS FOR THE CONTENT STRATEGIST
+Specific and actionable. Ranked by confidence:
+- High confidence: data clearly supports this
+- Medium confidence: data suggests this but is not conclusive
+- Low confidence: worth considering but needs more cycles to confirm
+
+Flag any conclusions you cannot reliably draw due to thin data. 
+Do not force interpretations where the data doesn't support them.
+
+Wait for my feedback before considering this report final. 
+I may have context that changes the interpretation — 
+for example, a LinkedIn post that underperformed because 
+it went out during a public holiday, or a spike in signups 
+driven by something outside this content cycle entirely.
+```

Content Factory/Phase 5 - Corpus Maintenance.md

@@ -0,0 +1,49 @@
+# Phase 5 — Corpus Maintenance
+
+Contains prompts for:
+- Add Front Matter to new notes
+- Create a new Overview Note or update an existing one
+- Update the Corpus Index Note.
+
+**!** The Overview Notes and Corpus Index Note are important for the Content Factory **!** 
+
+Use the following prompts for [PROJECT 5 - Librarian](PROJECT%205%20-%20Librarian.md):
+
+**TASK 1 — Front matter for new notes**
+```
+Perform Task 1.
+
+Process the following note(s) and produce front matter for each:
+
+[PASTE NOTE CONTENT HERE — or — specify the vault path and ask Claude to fetch via MCP]
+```
+
+**TASK 2 — Create a new overview note**
+```
+Perform Task 2.
+
+Create an overview note for the following vault folder:
+
+[FOLDER PATH]
+```
+
+**TASK 3 — Update an existing overview note**
+```
+Perform Task 3.
+
+Update the overview note for [FOLDER NAME / overview note name].
+
+The following changes have been made to the vault since the last update:
+- [Added: note path]
+- [Updated: note path]
+- [Retired: note path]
+
+Fetch the affected notes via MCP and update the overview note accordingly.
+```
+
+**TASK 4 — Update the corpus index note**
+```
+Perform Task 4.
+
+Update the corpus index note to reflect the current state of the vault.
+```