Always Ask... (A skills architect for YOU!)
I am including my /skill-architect here. Take it, customize it, go wild. (jump to the end if you don't want to know how I got here...) I've seen quite a bit of questions on here lately around skills, so I hope this helps. TL;DR - If you aren't asking Claude questions within chat AND planning with the chat feature via word vomit, yapping, brain dumps, and simply asking good questions... you should really start. (I plan to discuss my entire workflow for pretty much anything in another post) --- ## Context & Process I'm working on building an organizational structure for my personal brand. I am following the ICM framework, and heavily focusing on the 60% architecture before I even consider orchestration or AI integration. Today, I'm working through my content creation pipeline, where I'm focusing down on individual tasks that I want each 'employee' within my 'organization' to do. Enter skills. Now, I've worked for about 2 days on-and-off yapping on walks to develop a ROBUST product requirement description/document (PRD) and standard operating procedure document (SOP). After uploading this, I asked a simple question: If anything is unclear, if you couldn't exactly replicate this, [or] if I'm missing edge cases, I want you to ask me questions back and gather as much detail as possible. Interview me, one question at a time." This went on for about an hour or so before Claude decided that it had what it needed. It spit out a comprehensive document. I opened a new chat, uploaded the file, and gave it one simple prompt: [Can you break this down into a list of skills that would be relevant to have? For reference, I define a skill (or a skills file) as an individual, granular capability that an AI agent needs to execute its job. Rather than a general instruction, a skill is a comprehensive document that uniquely describes exactly how to perform a specific task.] What this did was take everything from that document and meticulously peeled out what the jobs-to-be-done are to achieve the overarching objective. I ended up with 51 skills and one-line descriptions of what each skill did. I saved this as a markdown.