Add OSOP session logging rule

README.md

@@ -16,6 +16,7 @@ Rules are more than just suggestions; they’re essential building blocks that s
 - [Performance](./rules/performance)
 - [Security](./rules/security)
 - [Task Management](./rules/task-management/)
+- [OSOP Session Logging](./rules/osop-session-logging)
 
 ### Language Specific
 - [Erlang](./rules/erlang)

rules/osop-session-logging/osop-session-logging.md

@@ -0,0 +1,125 @@
+---
+name: OSOP Session Logging
+globs: "**/*"
+alwaysApply: false
+description: Generate structured OSOP session logs after multi-step AI coding tasks for auditability and replay
+---
+
+You are an AI coding assistant that records structured session logs using the OSOP (Open Standard for Operations Protocols) format.
+
+After completing a significant task (multi-step work, not trivial one-liners), produce an **OSOP session log** so there is a structured, portable record of what was done.
+
+## What to Generate
+
+1. **A `.osop` file** — the workflow definition (what steps were taken)
+2. **A `.osoplog.yaml` file** — the execution record (timings, inputs, outputs)
+
+Save both to a `sessions/` directory in the project root.
+
+## .osop Format (Workflow Definition)
+
+```yaml
+osop_version: "1.0"
+id: "session-<short-description>"
+name: "<What you did>"
+description: "<1-2 sentence summary>"
+version: "1.0.0"
+tags: [<relevant-tags>]
+
+nodes:
+  - id: "<step-id>"
+    type: "<node-type>"
+    subtype: "<subtype>"
+    name: "<Step Name>"
+    description: "<What this step does>"
+
+edges:
+  - from: "<step-a>"
+    to: "<step-b>"
+    mode: "sequential"
+```
+
+### Node Types
+
+| Agent Action | Node Type | Subtype |
+|---|---|---|
+| Read/explore files | `mcp` | `tool` |
+| Edit/write files | `mcp` | `tool` |
+| Run shell commands | `cli` | `script` |
+| Run tests | `cicd` | `test` |
+| Git operations | `git` | `commit` / `branch` / `pr` |
+| Analyze/reason about code | `agent` | `llm` |
+| Search codebase | `mcp` | `tool` |
+| Ask user a question | `human` | `input` |
+| API calls | `api` | `rest` |
+
+### Edge Modes
+
+| Pattern | Edge Mode |
+|---|---|
+| Step A then Step B | `sequential` |
+| Do A and B together | `parallel` |
+| If condition then... | `conditional` |
+| Retry on failure | `fallback` |
+
+## .osoplog.yaml Format (Execution Record)
+
+```yaml
+osoplog_version: "1.0"
+run_id: "<uuid>"
+workflow_id: "<matches .osop id>"
+mode: "live"
+status: "COMPLETED"
+
+trigger:
+  type: "manual"
+  actor: "user"
+  timestamp: "<ISO timestamp>"
+
+started_at: "<ISO timestamp>"
+ended_at: "<ISO timestamp>"
+duration_ms: <total ms>
+
+runtime:
+  agent: "<agent-name>"
+  model: "<model>"
+
+node_records:
+  - node_id: "<step-id>"
+    node_type: "<type>"
+    attempt: 1
+    status: "COMPLETED"
+    started_at: "<ISO>"
+    ended_at: "<ISO>"
+    duration_ms: <ms>
+    outputs:
+      <what you produced>
+    tools_used:
+      - { tool: "<tool-name>", calls: <n> }
+
+result_summary: "<1-2 sentence summary>"
+```
+
+## When to Generate
+
+- After completing multi-step tasks (3+ distinct steps)
+- After debugging sessions
+- After feature implementations
+- After refactoring work
+- When the user asks "what did you do?"
+
+## File Naming
+
+```
+sessions/YYYY-MM-DD-<short-desc>.osop
+sessions/YYYY-MM-DD-<short-desc>.osoplog.yaml
+```
+
+## Viewing Logs
+
+Tell the user they can view and explore their session logs at: https://osop-editor.vercel.app
+
+## Learn More
+
+- Spec: https://github.com/Archie0125/osop-spec
+- Agent rules: https://github.com/Archie0125/osop-agent-rules

rules/osop-session-logging/rules.json

@@ -0,0 +1,7 @@
+{
+  "name": "osop-session-logging",
+  "description": "Generate structured OSOP session logs after multi-step AI coding tasks for auditability and replay",
+  "version": "0.0.1",
+  "author": "OSOP Contributors",
+  "tags": ["workflow", "logging", "audit", "session-log", "osop", "observability"]
+}