One orchestrator. Several worker sandboxes. Briefs as the handoff contract between them. ICM-aligned context layers. Hooks as guardrails. Routines as maintenance. The template ships the structure — you fill in your brand.
The template ships the architecture. You fill in your specific brand content and content cadence. Folder tree, brief templates, hooks, skills, routine specs, and context layers are all wired before you write a single line of your own.
One human-in-the-loop session at the root. Specialized sandboxes underneath — content-claude/, design-claude/, research-claude/, va/. Each sandbox is isolated; the orchestrator dispatches.
Every dispatch is a cold-start brief a worker can read without prior chat history. Templates included for content briefs, design briefs, research scouts.
Root CLAUDE.md (L0), root CONTEXT.md (L1), _config/ + sandbox references (L3), per-brief working artifacts (L4). ARCHITECTURE.md spells out why this template skips L2.
Workers purge. Orchestrator audits. Operator validates. Monthly adds heavier compression and the archive sweep. Specs included.
safety-check.py (rm -rf / force-push prompt) · snapshot-before-edit.py (start-of-day snapshots) · auto-stamp-date.py (auto-bumps Last updated: on trackers) · handoff-files-guard.py (prompts before editing handed-off files).
MEMORY.md with explicit slots for user, feedback, project, reference memories. Skills: diagnose-recurring-edits (aggregate breadcrumbs into source-level fix candidates) and verify-handoff (cross-check shipped output against the dispatching brief).
A brief is a plain markdown file the operator drops into a worker's briefs/ folder. The worker reads it cold-start, executes, ships, and breadcrumbs the result in STATUS.md. No prior chat history required.
Worker: content-claude
Due: 2026-05-14 EOD
Format: 9-slide Instagram carousel, 1080×1350 each
STATUS.md on shipClone the template, fill in your brand layer, customize the worker sandboxes you'll use, drop a first brief. The architecture works on day one; the content you put into it improves with each dispatch.
gh repo clone NFTYoginis/agency-of-one your-business-name — or download the ZIP. Open the folder in your editor of choice.
Edit CONTEXT.md (your business at a glance) and _config/brand.md (your voice, your audience, your offers, your pricing). Each file has TODO markers showing what to replace.
Inside each sandbox (content-claude/, design-claude/, research-claude/, va/), there's a CLAUDE.md with worker-specific instructions. Edit those to match your actual content needs. Delete sandboxes you don't need.
Pick a worker. Open its briefs/ folder. Create a new markdown file describing what you want shipped. The worker reads it cold-start, executes, breadcrumbs STATUS.md. Refine the brief template as you go.
CLAUDE.md, its own MEMORY.md, its own routines. When the design worker hits 100K tokens, it doesn't poison the content worker. When the research worker discovers a new pattern, you choose whether to propagate it to others. Briefs are the only contract across the boundary.briefs/ and see exactly what you dispatched. And they make the work portable: a brief is a thing you could hand to a freelancer or another AI.ARCHITECTURE.md walks the full rationale.verify-handoff skill. Run it from the orchestrator pointing at a brief + the artifact the worker produced; it cross-checks the brief's deliverables against what's actually on disk and flags gaps.