messy files to sop training system

The problem

Process documentation is often scattered across messy transcripts, screenshots, and old PDFs, leading to "knowledge rot" where instructions are invented or assumed. Developers and ops teams struggle to maintain a single source of truth that is 100% verifiable against raw evidence.

What it does

• Extracts atomic evidence from messy notes, meeting transcripts, tool screenshots, and legacy PDFs.
• Generates a synchronized SOP Core where every step, decision, and quality check includes a direct source trace ID.
• Produces a complete training pack including a one-page reference, onboarding lesson, and evidence-backed quiz.
• Logs procedural gaps and conflicting instructions explicitly instead of making assumptions or "hallucinating" fixes.
• Audits existing documentation to identify orphan instructions that lack source evidence.

Why this beats prompting it yourself

Generic prompts often smooth over contradictions or fill in missing steps with common sense, creating dangerous inaccuracies. This skill enforces a strict non-invention contract, ensuring that every piece of output is anchored to a specific source ID and registry entry.

Use cases

• Converting a recorded handoff call into a formal SOP and trainee quiz.
• Consolidating scattered Slack screenshots and markdown notes into a synchronized training system.
• Auditing legacy documentation to find steps that no longer align with current tool screenshots.
• Updating a production process by merging new evidence into an existing documentation set with a full change log.

Known limitations

Cannot resolve procedural conflicts automatically, these are flagged for user decision. Requires manual confirmation for blurry screenshots or unreadable OCR text.