2.5 From Process Map to Department Structure
🎥 Video lesson — video not yet migrated (source Skool video id:
a8d316863e284c6ebe1b927bbcd5ecd0).
Learning Objective
Understand how your process map translates into a structured department hierarchy and see the folder structure pattern you will build in Part 3 (AUTOMATE).
Your Process Map Becomes Real Structure
Look at the process map you created in the last lesson. The departments you listed are about to become real folders with real structure. Each department gets its own context, its own agents, and its own skills. This is how everything stays organized as your system grows.
The Hierarchy: Department, Agent, Skill, Workflow
There are four levels to this structure, and each one has a clear purpose.
A Department is a functional area of your business - Marketing, Sales, Delivery, Operations. Each department has its own config file with context specific to that area. Think of it as a mini Business Brain just for that part of the business.
An Agent is a specialized worker within a department. Think of agents as roles: "Lead Researcher," "Email Writer," "Proposal Builder." Each agent has focused context about what it does and how it does it.
A Skill is a specific, repeatable task an agent can execute. One skill does one job well. Examples: "scrape leads from Google Maps," "write a cold email sequence," "generate a weekly report." Skills are the building blocks - small, testable, and reusable.
A Workflow is a multi-step pipeline that chains skills together. For example, a Lead Generation workflow might chain together: scrape leads, enrich data, score leads, draft outreach, send emails. Workflows connect skills in sequence to handle complex processes end-to-end.
The Folder Structure Pattern
Every department follows the same pattern:
department-name/
agents/
agent-name/
skills/
skill-name/
workflows/
workflow-name/
The config.md file is essentially the department's CLAUDE.md - it holds context specific to that area. This pattern repeats for every department in your business. Once you learn it for one, you know it for all of them.
Real Example: Agency Outreach Department
In Bohdan's agency, the outreach department follows this exact pattern. It has a config file with outreach-specific rules, agents for lead research and email writing, skills for scraping and enriching leads, and a workflow that chains the entire outreach pipeline together.
Every skill in that department maps directly back to a task from his process map. The workflow connects those skills so the entire outreach pipeline runs with one command. That is the power of this structure - it turns your process map into something that actually executes.
You Do Not Build This Yet
Right now you only need to understand the structure. Part 3 (AUTOMATE) is where you actually create departments, agents, and skills. Today is about seeing the blueprint so that building makes sense when you get there.
Why This Structure Matters
Each department has its own isolated context. Marketing context does not pollute Sales. When you work inside a department, Claude only loads what is relevant to that area. This keeps Claude focused and accurate instead of drowning in unrelated information.
As your system grows from 3 departments to 6, from 5 skills to 50, this clean separation is what keeps everything manageable. Without it, you end up with a tangled mess that confuses both you and Claude.
Action Items
- Look at your process map and confirm which department each task belongs to
- For each department, think about what agents (roles) you would need
- List 2-3 skills per department that match your highest-impact tasks
- Do NOT create any folders or files yet - that happens in Part 3 (AUTOMATE)
- Optional: sketch out your department structure on paper or in a notes app