Hey everyone, I’m building an ICM workspace for my recruitment work and I’ve been thinking about how to keep it structured without making it too rigid. I like the idea of numbered stages because they create a clear order and help Codex find the right instructions. But in practice, my work doesn’t always start at the beginning or follow the same path. For example, I might add a new company and vacancy, work through the vacancy preparation, and then assess a candidate’s CV. That feels like a nice, ordered process. But the next day I might get another CV for that same vacancy. Ideally, I’d want Codex to pick up the existing vacancy information and go straight to the new candidate’s assessment, without repeating all the earlier steps. Other times, I might get a CV before I have a vacancy, or I might just want to format a CV without going through the full recruitment process at all. I’d like the workspace to flag anything useful that’s missing, but also let me decide whether to do it or skip it and move on when it isn’t essential. I’m trying to understand how best to make those entry points and optional steps clear in the folder structure and instructions. Am I overthinking this? Has anyone else run into this when their work doesn’t always follow a clear, step-by-step process? How have you structured your ICM so it stays organised while still letting you jump in at different points and reuse work you’ve already done? Would love to hear how others have approached it!

Do folders need to be numbered sequentially, as the ICM states, or is it okay to have a mix of numbered and descriptive folder names? At the moment, the workflow stage folders are mostly numbered, but resourcing has a 01a stage and the final handoff stages jump from 04 to 06. Client, template and record folders use descriptive names without numbers. Is that setup wrong, or is it okay as it is?

I’m building an ICM recruitment system called ICM Recruitment, and I’d love some feedback from the Skool community. The system is organised around clear workflows, with guidance files explaining how to use each part. It covers client and vacancy intake, vacancy evaluation, candidate resourcing, and assessing candidates across a client’s portfolio of roles. The resourcing workflow runs from confirming a vacancy through recruitment preparation, sourcing, outreach, CV assessment and drafting, then screening and preparing documents. Each stage has its own instructions and outputs, so the work can be picked up consistently and handed on at the right point. I’m still refining the structure and have questions about how best to organise and number the folders. If you’re building an ICM system too, I’d be interested to hear how you’re approaching it and what you’d improve. ICM Recruitment / ├── AGENTS.md # Main instructions ├── CONTEXT.md # README / workflow map ├── _shared/ │ └── CONTEXT.md # Shared guidance ├── clients/ │ └── AGENTS.md # Client-folder guidance └── pipelines/ ├── client-and-vacancy-intake/ │ ├── AGENTS.md # Intake routing │ ├── CONTEXT.md # Intake workflow map │ └── stages/ │ ├── 01_confirm-client/ │ │ └── CONTEXT.md │ └── 02_lock-vacancy/ │ └── CONTEXT.md ├── vacancy-evaluation/ │ ├── AGENTS.md │ └── CONTEXT.md ├── resourcing/ │ ├── AGENTS.md # Resourcing routing │ ├── CONTEXT.md # Resourcing workflow map │ └── stages/ │ ├── 01_vacancy-lock/ │ │ └── CONTEXT.md │ ├── 01a_recruitment-preparation/ │ │ └── CONTEXT.md │ ├── 02_source/ │ │ └── CONTEXT.md │ ├── 03_outreach/ │ │ └── CONTEXT.md │ ├── 04_assess-and-draft/ │ │ └── CONTEXT.md

Hi all 👋 This is my first post and video. I have been a VIP member since March. I continue to learn and get value from all aspects of this community on a regular basis. I also joined the Lyceum recently to better understand how to translate everything that I have been learning and processing for the last ~6 months into a tangible skill, product, business and more. The progress that I have made so far has been well worth it. Given that its structured like a class, there are assignments, deadlines, group work, etc. That means more opportunity to procrastinate! In my most recent bender of procrastinating, I decided to be productive and try new things. I made a video in attempt to summarize many recent updates to how I work with Claude on a day to day basis. So here's my version... and it was supposed to be 30 seconds. It's version five and a bit over five minutes. I got way off track, lost the plot and burned way too many tokens - but I learned a lot and fun along the way! Hope there is something in there for at least 1 person 🙌 My Human Harness - First video I've ever made - Posting my imperfections

Welcome to Clief Notes. Here’s where to start. 👋 You don’t need to watch the entire classroom before trying something. Pick a starting point, make something small, and bring your questions back here. 🧭 Find your way around Navigating the Course shows you what’s here and how to get around. If you’re new to working with AI, start with The Foundation. We work through prompting, context, and organizing your files so you can give an AI a job you can actually check. You’ll find guidance for Claude Code and Codex, plus a regular chat route where you save the files yourself. 💬 Use the check-ins At the bottom of the lessons, you’ll find polls and discussion posts. Share what you tried, what worked, and what needed correcting. If something doesn’t make sense, post the lesson and timestamp. “I got stuck right here” is a perfectly useful question. 🏆 Put something into practice Visit the Competitions Mega Thread for the current challenges, rules, and prizes. It’s a good excuse to finish something and see how other people approached the same problem. 📦 Looking for more? Premium: Explore The Vault for practical packages, templates, meeting takeaways, and worked examples. VIP: Head into The Drawing Room for VIP sessions and resources. Post your work. Ask questions. Help someone else when you can. What are you here to build—or what’s one task you’d love to make easier? Tell us below.