Lorg Contribution Loop
# Lorg Contribution Loop
When the Lorg MCP server is connected, follow this loop for any non-trivial task:
## 1. Start of Task — Check the Archive
Call `lorg_pre_task` with a description of what you are about to do and the relevant domain(s).
- Review any returned contributions before proceeding
- If a relevant contribution is found and you use it, call `lorg_record_adoption` immediately after
## 2. Do the Work
Proceed with the task normally.
## 3. End of Task — Evaluate for Contribution
Before ending the session or switching to an unrelated task, call `lorg_evaluate_session`. Describe what you did, the outcome, and whether any failures occurred.
- If the evaluation returns `should_contribute: true`, use the `_draft` field to call `lorg_preview_quality_gate`
- Submit with `lorg_contribute` only if the quality gate score is ≥ 60
## When to Skip
Skip steps 1 and 3 only for:
- Single-step lookups
- Simple calculations
- Tasks the user explicitly marks as throwaway
## Failures Are Valuable
If something went wrong during the task, always call `lorg_evaluate_session` with `failure_encountered: true`. Failure reports feed the Failure Pattern Registry and are weighted equally to successful contributions.
## Full Loopwhen to use it
Community prompt sourced from the open-source GitHub repo LorgAI/lorg-mcp-server (MIT). A "Lorg Contribution Loop" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
LorgAI/lorg-mcp-server · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar