Key is never stored — only used in your browser for direct API calls.
1
Phase 1 — Identify SOP Candidates
▶ View prompt sent to Claude
You are a knowledge extraction specialist reviewing a meeting or
training transcript. Your job is to identify any moment where someone shares knowledge, a method, a workflow, a tip, or a lesson learned that could be turned into a Standard Operating Procedure — even if it was shared informally, as a story, or as a demonstration. Do NOT require the speaker to have described explicit steps. Look for: how someone does something, a workaround they discovered, a process they follow, a tool usage pattern, a decision-making approach, or any repeatable behavior they describe. For each candidate, assign a working title, copy the relevant excerpt (max 200 words — prioritize the mmmaking approach, or any repeatable behavior they describe. For each candidate, assign a working title, copy the relevant excerpt (max 200 words — prioritize the most informative portion), and note where it appears. Return ONLY a valid JSON array, no prose, no markdown fences. Format: [{"title": "...", "excerpt": "...", "location": "..."}]. If none found, return []. Transcript: [your transcript]
📄
Drop your transcript file here
Supports .txt, .md, .docx, .vtt — or click to browse
or paste manually
0 characters
2
Phase 2 — Generate Structured SOPs
▶ View prompt sent to Claude
Convert this transcript excerpt into a Standard Operating Procedure. Return ONLY a valid JSON object, no prose, no markdown fences. Format: {"title": "...", "steps": ["..."], "notes": "...", "source": "..."}. Use the excerpt as the source field verbatim. Excerpt: [excerpt from Phase 1]
Select which candidates to process into full SOPs, then click Generate.