feat: add OSOP session logging prompt#288
Conversation
Add structured workflow logging for Windsurf using the OSOP protocol. Records AI coding sessions as `.osop` + `.osoplog.yaml` files that can be visualized, analyzed, and optimized. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| ### Notable Prompts | ||
|
|
||
| - [OSOP Session Logging](memories/osop-session-logging/) — Record AI coding sessions as structured `.osop` + `.osoplog.yaml` workflow logs using the [OSOP protocol](https://github.com/Archie0125/osop-spec). Produces portable, auditable execution records that can be visualized at [osop-editor.vercel.app](https://osop-editor.vercel.app). |
There was a problem hiding this comment.
🚩 "Notable Prompts" section introduces a new curation pattern not documented elsewhere
This PR introduces a new ### Notable Prompts subsection under ## Community Prompts in the root README. No other contribution is featured this way — the existing Community Resources section lists external repos, while Community Prompts just links to the memories/ directory. This creates a new pattern where specific contributions get highlighted in the main README. If more contributions are added, maintaining this section could become a governance question (who decides what's "notable"?). The memories/README.md doesn't mention this concept. Not a bug, but worth considering whether this pattern should be documented or formalized.
Was this helpful? React with 👍 or 👎 to provide feedback.
| ## Resources | ||
|
|
||
| - [OSOP Spec](https://github.com/Archie0125/osop-spec) — protocol definition | ||
| - [Visual Editor](https://osop-editor.vercel.app) — visualize and analyze workflows | ||
| - [Website](https://osop-website.vercel.app) — docs, examples, use cases |
There was a problem hiding this comment.
🚩 External links to OSOP resources cannot be verified
The global_rules.md:71-73 references three external URLs: the OSOP spec GitHub repo (https://github.com/Archie0125/osop-spec), the visual editor (https://osop-editor.vercel.app), and the website (https://osop-website.vercel.app). Similarly, README.md:69 links to the spec and editor. These are Vercel-hosted apps and a GitHub repo that may or may not be maintained long-term. The repository has markdown-link-check in its CI pipeline which should catch dead links, so this should be validated by existing automation.
Was this helpful? React with 👍 or 👎 to provide feedback.
Addresses Devin review feedback on PR detailobsessed#288: - Renamed memories/osop-session-logging/ to memories/Archie0125/ (username convention) - Added required README.md to the contribution directory - Updated path reference in main README.md Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
📝 Info: Contribution directory structure doesn't follow the documented template
The memories/README.md:16-51 documents a recommended directory structure where global rules should be placed under a Global-AI-rules/ subdirectory. The Archie0125 contribution places global_rules.md directly in the user directory root instead. However, the existing computerk contribution (memories/computerk/global-rules.md) also deviates from the template similarly, so this is an inconsistency in the repository rather than a clear violation by this PR. Only SchneiderSam follows the recommended structure fully.
Was this helpful? React with 👍 or 👎 to provide feedback.
Address Devin review: README.md Resources section now references global_rules.md instead of duplicating the same links. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
| ## Resources | ||
|
|
||
| See the Resources section in [`global_rules.md`](global_rules.md#resources) for links to the OSOP spec, visual editor, and documentation. |
There was a problem hiding this comment.
📝 Info: DRY compliance verified — Resources section properly defers to global_rules.md
The .windsurfrules mandates DRY, and a prior commit (e24b0ae fix: deduplicate resources section per DRY principle) shows this was actively addressed. The memories/Archie0125/README.md:24-26 Resources section correctly defers to global_rules.md#resources instead of duplicating the links. The osop-editor.vercel.app URL appears in 4 places across the PR, but each occurrence serves a distinct contextual purpose: root README summary, contribution README how-to step, global_rules.md AI instruction, and global_rules.md resource list. This is not a DRY violation.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Summary
memories/osop-session-logging/.osop+.osoplog.yamlworkflow logsWhat it does
After completing multi-step tasks, Windsurf generates:
.osopfile — workflow definition (what should happen).osoplog.yamlfile — execution record (what actually happened)Both can be visualized at osop-editor.vercel.app.
Test plan
global_rules.mdfollows Windsurf memories format🤖 Generated with Claude Code