TL;DR /brofessor is ICM-based skill that helps clean up AI-agent workspaces. It's also a small persona factory: the audit engine stays the same, but you can switch and create personas, and even tune them with a CONFIG.md It checks whether your docs, routing, stages, review gates, and context-loading patterns make sense. It finds bloat, confusion, contradiction, and overbuilt process junk. Then it proposes the smallest safe fix, waits for approval, executes only what you approve, and wraps up with a clear synthesis. It is half workspace auditor, half context janitor, half theatrical menace. Yes, that is three halves. The math is fine. Keep moving. Grab it, run it on a messy workspace, and let it bully your docs into behaving. - Brofessor iight now that that's out of the way, I'm going to explain why this shit actually bangs - actually fuck it imma let him explain this too. ps - this skill was made in 3 prompts, I can show you how I did it if anyone's curious... - yuckyyy Yep — replace the longer **“How It Works”** section with this: ```md ## How It Works Brofessor works because the prompt is built like a layered workspace auditor, not a generic “clean up my docs” request. ### 1. Core Directive: Treat the Workspace Like a Factory The prompt frames the repo as a multi-stage context system: - each stage has inputs - each stage produces outputs - each stage loads only what it needs - stable rules live outside active work - review gates control movement between stages So Brofessor is not asking, “Are these files tidy?” It is asking, “Can agents move through this workspace predictably?” ### 2. Layer Model: Give Every File a Job Brofessor audits through five layers: - **Layer 0:** workspace identity - **Layer 1:** map/orientation - **Layer 2:** routing/context loading - **Layer 3:** stable rules, contracts, criteria - **Layer 4:** active products and outputs This prevents the classic markdown soup problem where `CLAUDE.md`, `CONTEXT.md`, plans, rules, drafts, and review notes all start pretending to be the boss.

🔥 16 saves. 1 day. 3 AI voices cooking together. I'm a retired NYPD detective. Zero coding background. Yesterday I caught something nasty in my empire: one of my businesses had been silently bleeding revenue for 11 days. Pipeline running, files getting written, but the daily summary email to my partner — gone. Dark. Eleven days. I didn't catch it. My Council did. What's the Council? Three AI voices I run in parallel using Jake's file method: ⚔️ Odin — the architect. Strategy, debate, big decisions. 🗡️ Tyr — the surgeon. Line-by-line, finds bugs others miss. 🛡️ Heimdall — the watchman. Cross-tree audits, sees what's drifting. They don't agree. That's the whole point. Yesterday Heimdall flagged something off in a system I thought was healthy. Tyr cut it down to the exact file. Odin built the recovery plan. I executed in shell. Total time from "wait, what's wrong" to "fixed and verified": 4 hours. Without them? I'd have found out when my partner asked "where's my email" and I'd have spent a week figuring out why. The wild part — none of this is some custom agentic framework. No fancy orchestration layer. It's just folders and SKILL.md files. Jake's method. A folder. A markdown file telling each voice what to do. They read the same file. They argue. They ship. By the end of the session: 16 distinct catches the Council made that I would've missed alone. One catch alone saved me from losing thousands of dollars of leads and a partner relationship. Right now as I type this, the same 3 voices are autonomously building a new state scraper for me — folder method, SKILL.md driving, Codex cooking overnight. I'm going to wake up to a finished Phase 1 report. I built none of this with code I wrote. I orchestrated it with files. If a cop with no tech background can run 3 AI models like a symphony using nothing but folders and markdown — what's your excuse? Jake's method works. Receipts above. 🥷 七転び八起き