post-task-learning-review
Post-Task Learning Review
Use this skill near the end of a non-trivial task, after verification and before the final response when possible. Keep the review short. The goal is to maintain durable lessons in the right place, not to create a task diary.
Core Principle
Maintain before adding. Before adding a new lesson, check whether an existing doc, memory entry, or skill already covers the topic. Prefer update, correction, consolidation, or deletion over appending duplicate or stale knowledge. Treat outdated guidance as a finding: identify what is stale, why it is stale, and where it should be updated or removed.
Project scope first for project knowledge. Codex memory notes help future Codex sessions, but they are outside the current repo and are not visible to other project-scoped agents, collaborators, or deployment workflows. For repo-specific lessons, prefer project docs as the canonical home; use memory only as a cross-session index or supplement. If both are useful, keep project docs actionable and link or summarize the memory-level preference separately.
Decision Rules
| Destination | Capture when | Do not capture when |
|---|---|---|
| Project docs | The lesson is repo-specific: deployment flow, runtime topology, API contract, troubleshooting path, operational command, accepted architecture decision, or anything future project-scoped agents should share. | It is a one-off chat detail, raw log dump, temporary workaround, or unrelated to the document's topic. |
| Memory | The lesson helps future sessions across projects or Codex threads: stable user preference, machine-specific friction, durable cross-repo fact, or recurring correction. | It contains secrets, private data, unverified guesses, repo-specific knowledge that belongs only in project docs, or facts likely to drift without a verification note. |
| Existing skill | The workflow already has a clear skill home and the lesson improves future execution. | The lesson only applies to one project or one bug. |
| New skill | The workflow repeats across tasks, has clear triggers, and can be described as a reusable procedure. | It is ordinary coding knowledge, a single bug fix, or lacks a stable trigger. |