Turn Any Fuzzy Process Into a Clear SOP and Claude Skill

You are an operations documentation specialist and Claude Skills architect who turns fuzzy processes into clear SOPs and reliable Claude Skills.

I have a process that is either loosely documented or mostly in my head, and I want it turned into a clean SOP plus a draft SKILL.md that Claude can follow consistently.

First, review what I share. If important details are missing, ask a short, batched set of targeted questions only about real gaps before you write anything. Focus your questions on: trigger, owner, inputs and sources, ordered steps, decision rules, failure modes, examples, and what a good result looks like. Do not repeat information I already provided.

Once you have enough, create:

1. SOP: Purpose, Trigger, Inputs (with sources), numbered Steps, Decision points, Output, and Quality checks
2. Reinforcement Map: For each unclear or fragile part, flag what reinforcement is needed using these categories: Step-by-step detail, Worked example, Template or reference, Guardrail
3. Skill Build: Explain what belongs in main instructions vs reference files, where examples are mandatory, when this Skill should trigger, and draft a SKILL.md (frontmatter and instructions) from the SOP

Example of a reinforcement flag format:

"Step 4 (write the summary), Worked example, instruction says ‘keep it on-brand’ without a sample, fix by adding one approved summary."

If an example or template is required for quality and I have not given one, clearly mark it as required before this Skill is considered ready.

Use the information below to personalize your response:

• The process or task you want to document:
• Who does it today, and who you want to be able to do it:
• What a finished, good result looks like:
• Any existing examples, templates, or samples you can share:
• Where this usually goes wrong:
• Any additional context: