From mentilead-growth-os
Capture experiment observations — agent decisions, failures, escalations, contradictions between enterprise advice and personal practice, autonomy milestones. Quick capture (under 60 seconds) with automatic type-specific reflection prompts, standalone reflection mode for older observations, and monthly review with autonomy score. Use when the user wants to log something that happened.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mentilead-growth-os:observation-loggerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before starting any mode, determine the current state and recommend the next logical step.
Before starting any mode, determine the current state and recommend the next logical step.
marketing/MEMORY.md and marketing/STATUS.mdmarketing/ does NOT exist: tell the user to run the init skill first and stopreferences/experiment-thesis.md — required by the Experiment Layer rules in CLAUDE.mdmarketing/experiment/observations.md exists. If not, offer to create it from templates/observations.mdmarketing/experiment/autonomy-log.md exists. If not, create it from templates/autonomy-log.mdexperiment_chapter from STATUS.md frontmatter (default: "Chapter 1: Foundation")If invoked via slash command, skip the options menu and go directly to Step 1 (Quick Capture).
If the user's intent is not clear from their message, present these options:
Observation Logger:
Current chapter: {experiment_chapter}
Observations logged: {count from observations.md}
Observations with reflections: {reflected_count}/{total_count}
Current month autonomy score: {score}%
What would you like to do?
1. Quick Capture — log what just happened (under 60 seconds)
2. Reflection — add depth to a recent observation
3. Review — monthly summary with autonomy score
Route to the appropriate step based on the user's choice or detected intent.
Designed for speed — the user should be able to log an observation in under 60 seconds.
Ask only what's needed:
From the user's answer, classify:
type: one of autonomous-action, human-escalation, agent-failure, contradiction, milestoneseverity: if failure → low / medium / high (based on impact described)system: which agent or system was involved (extract from user's words)Count existing ### OBS- entries in marketing/experiment/observations.md and increment by 1. Format as OBS-{NNN} with zero-padded three digits (e.g., OBS-001, OBS-012).
Append to marketing/experiment/observations.md:
### OBS-{NNN} — {YYYY-MM-DD}
- **Type:** {type}
- **System:** {system}
- **Chapter:** {experiment_chapter from STATUS.md}
- **Severity:** {severity, if applicable — omit line if not a failure}
- **What happened:** {user's words}
- **Significance:** {user's note, or "—"}
- **Has reflection:** false
If type is autonomous-action, human-escalation, or agent-failure, update marketing/experiment/autonomy-log.md:
The Monthly Summary table has 7 columns: Month | Autonomous | Human Escalations | Agent Failures | Total | Score | Notes
YYYY-MM)| {YYYY-MM} | 0 | 0 | 0 | 0 | 0% | — |autonomous-action → increment Autonomoushuman-escalation → increment Human Escalationsagent-failure → increment Agent Failuresautonomous + human_escalations (agent failures are NOT part of the total)autonomous / total * 100 (rounded to nearest integer, format as {score}%)After updating the summary row, update the System Breakdown section for the current month:
### {YYYY-MM} section under ## System Breakdown### {YYYY-MM}
| System | Autonomous | Escalated | Failures |
|--------|-----------|-----------|----------|
| {system} | {n} | {n} | {n} |
{system} from this observationShow the logged entry back to the user:
Logged OBS-{NNN}:
- Type: {type}
- System: {system}
- What happened: {summary}
{if autonomy-relevant: "Autonomy score updated: {score}% ({autonomous}/{total} decisions this month)"}
Immediately after confirming the logged entry, offer type-specific reflection questions while the moment is fresh. This is optional — the user can skip instantly to preserve the under-60-second quick capture path.
| Type | Question 1 | Question 2 |
|---|---|---|
autonomous-action | "What would have gone wrong without the agent?" | "What did it miss?" |
human-escalation | "Could you have given the agent enough context to handle this?" | "Why or why not?" |
contradiction | "Which side of the contradiction do you trust more right now?" | "Why?" |
milestone | "What's the next milestone this makes possible?" | "What could block it?" |
agent-failure | "What should the agent have done instead?" | "Is this a training gap or a fundamental limitation?" |
#### Reflection block to the observation entry:
#### Reflection
- **Q:** {question 1}
- **A:** {user's answer}
- **Q:** {question 2}
- **A:** {user's answer}
And update - **Has reflection:** false → - **Has reflection:** true
Has reflection: false and proceed to Session Log & State Update (current behavior preserved)marketing/logs/{YYYY-MM-DD}.md:
- **Observation Logger** — Logged OBS-{NNN} ({type}): {one-line summary}
marketing/STATUS.md: set last_updated to today's date, preserve experiment_chapterFor adding depth to existing observations. Observations with reflections are the highest-value content sources for future publishable material.
marketing/experiment/observations.md#### Reflection block (already reflected via Step 1)Recent observations:
1. OBS-{NNN} ({date}) [{type}] — {what happened, truncated to one line}
2. OBS-{NNN} ({date}) [{type}] — {what happened, truncated to one line}
...
Ask the user three questions (can be answered together or one at a time):
Add the reflection to the selected observation entry in marketing/experiment/observations.md. Find the entry by its ### OBS-{NNN} heading and append after the existing fields:
- **Enterprise advice:** {what they'd tell a client}
- **What I actually did:** {what they did}
- **Why the difference:** {reasoning}
- **Has reflection:** true
Update the Has reflection line from false to true.
Reflection added to OBS-{NNN}.
This observation is now flagged as a content candidate for future publishing.
Observations with reflections: {reflected_count}/{total_count}
marketing/logs/{YYYY-MM-DD}.md:
- **Observation Logger** — Added reflection to OBS-{NNN}
marketing/STATUS.md: set last_updated to today's dateMonthly summary of observations and autonomy progress. This is read-only — no files are written except the session log.
marketing/experiment/observations.mdmarketing/experiment/autonomy-log.md### OBS-{NNN} — {YYYY-MM-DD} headings)Monthly Observation Summary — {YYYY-MM}:
| Type | Count |
|----------------------|-------|
| Autonomous Actions | {n} |
| Human Escalations | {n} |
| Agent Failures | {n} |
| Contradictions | {n} |
| Milestones | {n} |
| TOTAL | {n} |
Autonomy Score: {score}% ({autonomous} autonomous / {total} total decisions)
Observations with reflections: {reflected_count}/{total_count} ({percent}%)
Group observations for the current month by type and list each:
Autonomous Actions:
- OBS-{NNN} ({date}): {one-line summary} {if has_reflection: "[has reflection]"}
Human Escalations:
- OBS-{NNN} ({date}): {one-line summary} {if has_reflection: "[has reflection]"}
...
If any observations have reflections, highlight them:
Content Candidates (observations with reflections):
- OBS-{NNN}: {what happened} → {enterprise advice vs. actual decision, one line}
These are the highest-value entries for future narrative content about the experiment.
Append to marketing/logs/{YYYY-MM-DD}.md:
- **Observation Logger** — Monthly review for {YYYY-MM}: {total_count} observations, {score}% autonomy score
| Mode | References Read | User Files Read | User Files Written |
|---|---|---|---|
| Step 0 | references/experiment-thesis.md | MEMORY.md, STATUS.md, experiment/observations.md | — |
| Step 1 | — | STATUS.md | experiment/observations.md, experiment/autonomy-log.md, STATUS.md, logs/{today}.md |
| Step 2 | — | experiment/observations.md | experiment/observations.md, logs/{today}.md, STATUS.md |
| Step 3 | — | experiment/observations.md, experiment/autonomy-log.md | logs/{today}.md |
npx claudepluginhub mentilead/growthos --plugin mentilead-growth-osCaptures structured lessons learned entries for organizational memory after incidents, completed projects, or significant learnings to preserve knowledge for future teams.
Generates weekly and monthly insight reports from journal entries, including pattern recognition, floor trends, life coach feedback, therapist observations, and advisory panel thoughts.
Runs context-aware retrospectives auto-gathering git metrics, learnings, away-logs, and handoffs into pre-populated tables for interactive or agent-summary review.