task-observer

Mines a finished project version's session history for skill improvement patterns.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/CMiller838/meal-planner --skill task-observer-cmiller838
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-observer
Source: https://github.com/CMiller838/meal-planner/tree/main/.claude/skills/task-observer
Command: npx skills add https://github.com/CMiller838/meal-planner --skill task-observer-cmiller838

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Insights about how AI skills could be improved surface during real work but get lost between sessions. This Skill runs a retrospective pass over one finished project version, mining the whole version's session history for repeated corrections, workflow patterns, and methodology gaps worth turning into new skills or fixes to existing ones. ## Core Features & Use Cases - Version-level retrospective: Run once per project version, right after project-retro, to review everything that happened rather than monitoring per-session. - Structured observation log: Captures findings as numbered observations with Status, Issue, Improvement, and Principle fields in a persistent workspace log, with concurrency-safe numbering and archival rules. - Weekly review workflow: A scheduled or 7-day fallback review cross-checks OPEN observations against all skills, applies non-escalated improvements, and stages updated skills for user approval. - Use Case: After finishing v1 of a project, invoke it explicitly to surface that users repeatedly corrected the same report-formatting rule, then turn that pattern into a staged update to the reporting skill before starting v2. ## Quick Start Run task-observer to review this finished project version and tell me what skill improvements came out of it.

Frequently Asked Questions about task-observer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a skill improvement retrospective after a project version?

Invoke task-observer explicitly by name once per version, right after project-retro. It mines the whole version's session history for patterns and repeated corrections, then logs observations for review before you start the next version.

How do I capture AI skill improvement ideas during work sessions?

Observations are appended silently to a persistent log at skill-observations/log.md with a mandatory Status field, numbered using a check-then-act-then-verify discipline. Hard checkpoints after every third completed todo and at deliverable events force the writes.

Does task-observer trigger automatically during a session?

No, it is invoked explicitly by name and deliberately does not auto-trigger mid-session, since that proved noisy relative to its value. A scheduled or 7-day fallback review can run the weekly review procedure when the backlog is stale.

Can the observation log work without persistent filesystem access?

Yes, handoff-doc mode collects observations in-session and delivers them as a structured handoff document the user stores and pastes into the next session. The methodology is environment-independent; only persistence varies.

Why did entries disappear from a shared observation log?

Concurrent sessions can overwrite each other during full-file rewrites like archival. The skill mandates backups, re-reading the live log before write-back, bounded per-entry mutations, and post-write survival checks to prevent silent loss.