ComputerConnection/store-sop

Store SOP Generator: $ARGUMENTS

Document this Computer Connection process for AI consumption.

---

Why This Matters

Your 6-month goal: AI server that serves store SOPs. The AI can only serve what's documented. Every SOP captured = more value from the AI.

---

Step 1: Interview Mode

I'll ask questions to extract the process. Answer quickly - don't overthink.

Basic Info

1. Process name: [what do you call this?]
2. When does this happen?: [trigger/situation]
3. Who usually does it?: [role/person]
4. How often?: [frequency]
5. How long does it take?: [typical duration]

The Steps

Walk me through it like I'm a new employee:

1. First, you...
2. Then...
3. Then...
4. Finally...

Decision Points

Where do you have to make a judgment call?

• If [condition], then [action A]
• If [other condition], then [action B]

Common Mistakes

What do new people get wrong?

• [mistake 1]
• [mistake 2]

Tools/Systems Used

What do you need access to?

• [ ] POS system
• [ ] Inventory system
• [ ] Email
• [ ] Phone
• [ ] Physical tools
• [ ] Other: [specify]

---

Step 2: Structure the SOP

sop:
  id: SOP-[category]-[number]
  name: [Process Name]
  version: 1.0
  last_updated: [date]
  owner: [who maintains this]

  metadata:
    category: [sales | repair | inventory | customer-service | admin | other]
    frequency: [daily | weekly | as-needed | rare]
    duration: [typical time]
    difficulty: [easy | medium | complex]

  trigger: |
    When to use this process:
    [condition or situation]

  prerequisites:
    - [what must be true before starting]
    - [access/permissions needed]

  steps:
    - step: 1
      action: |
        [What to do]
      details: |
        [How to do it - specific clicks, words, etc.]
      tips:
        - [helpful hint]
      warnings:
        - [thing to avoid]

    - step: 2
      action: |
        [Next action]
      decision_point:
        condition: [if X]
        if_true: [do Y]
        if_false: [do Z]

  edge_cases:
    - scenario: [unusual situation]
      handling: [what to do]

  common_mistakes:
    - mistake: [what people do wrong]
      prevention: [how to avoid]
      recovery: [how to fix if it happens]

  tools_required:
    - name: [tool/system]
      purpose: [why needed]
      access: [how to get access]

  related_sops:
    - [SOP-XXX-NNN]

  ai_queryable:
    keywords: [search terms customers or staff might use]
    questions_this_answers:
      - "How do I...?"
      - "What's the process for...?"
      - "When should I...?"

---

Step 3: AI Optimization

Make it queryable by adding:

Natural Language Triggers

ai_triggers:
  - "customer wants to return"
  - "how do I process a return"
  - "return policy"
  - "refund"

FAQ Pairs

faq:
  - q: "Can I return this?"
    a: "See return eligibility in step 2"
  - q: "How long do returns take?"
    a: "Typically [X] minutes"

Escalation Paths

escalation:
  - condition: "Customer is angry"
    action: "Get Zach or manager"
  - condition: "System won't process"
    action: "Manual override - see SOP-ADMIN-005"

---

Step 4: Save Location

Store SOPs in:

~/store-ai-poc/sops/
├── sales/
│   ├── SOP-SALES-001-new-customer.yaml
│   └── SOP-SALES-002-quote-build.yaml
├── repair/
│   ├── SOP-REPAIR-001-intake.yaml
│   └── SOP-REPAIR-002-diagnosis.yaml
├── inventory/
├── customer-service/
└── admin/

Also maintain an index:

~/store-ai-poc/sops/INDEX.md

---

Step 5: Validation

Before finalizing:

• [ ] Could a new employee follow this?
• [ ] Are decision points clear?
• [ ] Are edge cases covered?
• [ ] Is it AI-queryable (good keywords)?
• [ ] Does it link to related SOPs?

---

Quick Capture Mode

For fast documentation:

# SOP: [Name]

**When**: [trigger]
**Time**: [duration]

## Steps
1. [action]
2. [action]
3. [action]

## If Problems
- [issue] → [solution]

## Don't Forget
- [common mistake to avoid]

Expand to full format later.

---

SOP Categories for Computer Connection

Track progress:

Sales

• [ ] New customer intake
• [ ] Quote/build consultation
• [ ] Checkout process
• [ ] Financing options
• [ ] Business accounts

Repair

• [ ] Repair intake
• [ ] Diagnosis workflow
• [ ] Customer communication
• [ ] Parts ordering
• [ ] Repair completion/pickup

Inventory

• [ ] Receiving shipments
• [ ] Stock checks
• [ ] Reordering
• [ ] Returns to vendor

Customer Service

• [ ] Phone handling
• [ ] Warranty claims
• [ ] Complaints/escalations
• [ ] Follow-ups

Admin

• [ ] Opening procedures
• [ ] Closing procedures
• [ ] Cash handling
• [ ] Scheduling

---

Output

1. Show the structured SOP
2. Save to appropriate location
3. Update INDEX.md
4. Suggest related SOPs to document next