SOP and process documentation generation

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

1. process_capture_source

   REQUIREDREADhuman

   How the process gets observed. Screen recording, narrated walkthrough, or interview transcript.

   DATA SHAPE

   Recording (screen + audio) or transcribed walkthrough with the operator describing what they're doing and why.
   COMMONLY FILLED BY

   • screen recording tool with annotation
   • structured interview with the operator
   • narrated walkthrough captured during normal work
2. existing_sop_corpus

   RECOMMENDEDREADcorpus

   Existing SOPs the pattern reads to learn the firm's documentation conventions (style, structure, level of detail).

   DATA SHAPE

   Existing approved SOPs in their native format.
   IF MISSING

   Drafts follow generic SOP conventions rather than the firm's. Reviewer has to adjust style on every document. Recommend at least 3-5 example SOPs even if they're rough.
   COMMONLY FILLED BY

   • existing wiki SOPs folder
   • structured SOP library in a docs tool
   • shared drive with previously written procedures
3. draft_review_destination

   REQUIREDWRITErequest

   Where the drafted SOP goes for human approval. Operator and a designated reviewer both need to validate before publishing.

   DATA SHAPE

   Draft SOP with annotations: confident vs. uncertain steps, places where the operator's narration was unclear, edit interface.
   COMMONLY FILLED BY

   • draft folder in the wiki with review-comment functionality
   • shared doc with the operator and reviewer
   • draft section in the SOP management tool
4. approved_sop_destination

   REQUIREDWRITEevent

   Where approved SOPs land once reviewed and signed off. Becomes the new official version.

   DATA SHAPE

   Versioned approved SOP with structured metadata (process owner, last reviewed, related SOPs).
   COMMONLY FILLED BY

   • published wiki pages with version history
   • SOP management tool with formal approval workflow
   • structured library accessible to relevant teams
5. screen_context_resolver

   RECOMMENDEDREADrequest

   When the recording shows screens of internal tools, identify which tools and screens to make instructions specific. Significantly improves SOP usability.

   DATA SHAPE

   Mapping from visual screen recognition to tool/screen identifiers, with associated context.
   IF MISSING

   SOPs describe what the operator clicked in generic terms ('the blue button at the top'). Recommend especially for tool-heavy processes.
   COMMONLY FILLED BY

   • tool-aware screen recognition with custom training
   • operator manually labels screens during capture
   • structured tool inventory the pattern matches against