App / Tool Workflow Template

Template for any external-app or tool-workflow doc. Use when an app/tool has its own non-trivial workflow that should be documented separately from a robot-specific SOP.

---
title: <Tool / App Name>
status: stub
applies_to:
  - universal
audience:
  - operator
visibility: internal_general
approval_status: draft
owner: TBD
last_source_check: TBD
related_apps: []
related_sops: []
related_dashboards: []
related_issue_forms: []
known_gaps: []
---

Required body sections (13 fields per user prompt)

1. Tool / app name

Canonical product name.

2. Current status

Active / experimental / deprecated / unknown.

3. Audience

Which roles use this tool.

4. Workflow owner

Skild handle responsible for the doc’s correctness.

5. When to use it

Trigger conditions — what situation calls for this tool.

6. Step-by-step workflow

Numbered procedure.

7. Screenshots

Links to library/public/screenshots/ (when added). Per BACKLOG B-A9 / B-D7.

Link to library SOPs that use this tool.

Link to dashboards that consume data from this tool.

Link to incident forms / issue-reporting flows.

11. Known stale areas

Sections of this workflow that may be out of date.

12. Current procedure gaps

Steps not yet documented; operator workarounds known but not normalized.

13. Open questions

TBD items.