Your core context — automatically injected into every skill execution.
Ten questions. Five minutes. Builds the intelligence layer that every skill reads before producing output.
Generates brand-aligned copy in any format. Produces two complete versions so you can choose the best angle.
Writes high-converting short-form video scripts with production notes. Three complete scripts per run.
One source piece becomes many channel-ready formats. Paste any long-form content and select your outputs.
Identifies what is gaining traction in your niche. The brief feeds directly into your next copy or content run.
No outputs yet.
Execute a skill to generate your first project file.
Per-skill feedback accumulated across sessions. Each skill reads its own section here before executing.
Session history. Short-term logs each session; long-term accumulates strategic knowledge.
Rate outputs, log feedback, and close the session. The system updates skill learnings and saves memory automatically.
Register a custom skill. The heartbeat validates dependencies and adds it to the registry on next run.
The Agentic OS System Blueprint
A complete reference for understanding, deploying, and scaling your AI-powered business operating system — from first principles to advanced workflows.
The Agentic OS is not a collection of AI prompts. It is an operating system — a structured, self-improving intelligence layer that sits between you and AI, making every output brand-specific, contextually aware, and progressively sharper over time.
Most people use AI by typing a request and getting generic output. The Agentic OS inverts this. You build your intelligence once — brand voice, ideal customer, positioning — and every skill reads that foundation automatically before producing anything.
Layer 1 — Brand Context
Built once during setup. Contains voice profile, ideal customer, positioning, products, assets, and writing samples. Every skill reads from here before producing output.
Layer 2 — Skills
Modular, category-organised, plug-and-play capabilities. Each is a SKILL.md with step-by-step instructions, reference files, and declared dependencies.
Layer 3 — Learning System
SOUL.md defines agent identity. USER.md tracks preferences. learnings.md accumulates per-skill feedback. Memory stores session history. Everything compounds.
The Heartbeat
thestoryofeveryheartbeat runs on every session start — scans skills, validates dependencies, syncs the registry, loads memory, and reports system status automatically.
Run the Heartbeat
Opens every session. Scans skills, validates registry, loads context and learnings into working memory, reports status. Keeps everything in sync automatically.
Execute Skills
Choose a skill and run it. The executor automatically injects brand context, ICP, positioning, and the skill's own learnings before sending to AI. The output is already yours.
Save to Projects
Every execution saves to your projects library with timestamp, skill name, and full content. Review, copy, or open any output — nothing disappears between sessions.
Wrap Up
Ends every session. Rate outputs, log what worked and what to improve. The system writes those notes into each skill's learnings section. The next run reads them. This is the loop that compounds.
🚀 SaaS & Tech
- Product launch copy
- Feature announcements
- Cold outreach sequences
- Case study repurposing
- Onboarding email flows
🎯 Coaching & Consulting
- Discovery call scripts
- Programme sales pages
- Newsletter content
- Podcast repurposing
- LinkedIn content system
🛍 E-Commerce & DTC
- Product descriptions
- UGC scripts for creators
- Email abandonment flows
- Ad copy variants
- Influencer briefs
🏢 Agencies
- Client proposal copy
- Case study writing
- Outreach email variants
- Trend research reports
- Social proof content
🏥 Healthcare & Education
- Patient communications
- Educational content
- Referral letter templates
- Course promo copy
- Social media content
🎬 Media & Creators
- Video script writing
- Multi-platform repurposing
- Sponsorship pitches
- Trend-surfing content
- Community newsletter
After Copywriting — A/B test across channels
Run Version A in one campaign, Version B in another. Feed results back via Wrap Up so the system learns which angles work for your audience. Over 4–6 sessions, the skill converges on your highest-performing style.
After UGC Scripts — send to creators or film yourself
Forward scripts directly to UGC creators with production notes already included. Or use as teleprompter-ready scripts. The HOOK sections work as standalone ad hooks.
After Repurpose — build a full content calendar in minutes
One run gives you: newsletter, LinkedIn post, Twitter thread, 5 hooks, 5 email subjects, and 3 quote cards. That is a full week of multi-channel content from a single source piece.
After Trend Research — chain to execution skills
Run Trend Research then immediately run Copywriting or Repurpose — the system context now includes the trend data. Your next copy run incorporates trending angles automatically.
After multiple Wrap Ups — export Learnings as a strategy document
After 20+ sessions, your learnings.md is a living document of what works for your specific business. Use it as a brief for a copywriter, onboarding doc for a new team member, or quarterly strategy review.
| Workflow | Chain | Outcome |
|---|---|---|
| Weekly content engine | Trend Research → Repurpose → Copywriting | Full week of multi-channel content in one session with current angles. |
| Launch sequence | Copywriting (awareness) → Copywriting (conversion) → UGC Scripts | Three-phase launch content — awareness, conversion, creator assets — all in brand voice. |
| Podcast monetisation | Repurpose (transcript) → UGC Scripts | One episode becomes a newsletter, LinkedIn post, Twitter thread, and three UGC scripts. |
| Competitor response | Trend Research → Copywriting (myth-bust) | Research competitor narratives then write counter-positioning copy that addresses the same pain from your angle. |
Frequently Asked Questions
Everything you need to know about the Agentic OS — from getting started to advanced usage, troubleshooting, and scaling across multiple businesses.
- Persistent brand context — your voice, ICP, and positioning are injected automatically into every run. You never re-explain who you are.
- Learning loop — the system logs feedback after every session and reads it before the next run. It gets smarter over time.
- Skill registry — each task is a structured process (a SKILL.md file), not a freeform prompt. This means reproducible, consistently on-brand outputs.
- Scans the skill registry and detects new or removed skills
- Validates dependencies for all active skills
- Loads your brand context into working memory
- Loads the learnings from previous sessions
- Reports system status
- Gives you real A/B testing material — deploy both and measure which resonates
- Prevents you from anchoring on a single approach
- Surfaces angles you might not have considered
HTML mode generates a complete, formatted HTML document you can download and use as a template or embed directly in a CMS.
Live Preview mode renders the HTML output in a browser frame inside the app — so you can see exactly what the page looks like before you use it. Best for landing pages, newsletter templates, and any content where visual presentation matters.
- Run
Trend Research→ immediately runCopywriting— the trending angles are now in context - Run
Repurposeon a transcript → runUGC Scripts— the source content informs the scripts - Run
Copywriting (awareness)→Copywriting (conversion)→UGC Scriptsfor a complete launch sequence
- Run — skill executes with full brand context injected
- Review — you rate the output and leave notes in Wrap Up
- Log — notes are written to that skill's section in learnings.md
- Apply — next time the skill runs, it reads its own learnings before executing
- The feedback being logged to learnings.md
- The skill improvement that would have happened
- The short-term memory entry for that session
- Run the Setup Wizard again (it overwrites brand context only)
- Or keep separate browser profiles / localStorage instances for each client
- Skills persist and are shared — new business just gets different brand context injected
- Does it sound like you, not like generic AI?
- Does it speak to your actual customer, not a hypothetical one?
- Would you edit out more than 20% of it?
Learnings — per-skill feedback logs. What worked, what to improve, your ratings from each session. This is what makes skills smarter over time.
Memory — session-level records. What you worked on, decisions made, next priorities. Short-term tracks recent sessions; long-term accumulates strategic knowledge that doesn't expire. Think of Projects as your content archive, Learnings as your training data, and Memory as your notes between sessions.
Use HTML when: you need a formatted document to embed in a CMS, send as a branded email, or use as a template for a developer.
Use Live Preview when: you want to see exactly how the content looks rendered before using it — ideal for landing page copy, newsletter templates, and any content where visual hierarchy matters. You can copy the HTML from the code view and paste it directly into any HTML-capable platform.