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. Directly apply qualified maintenance actions instead of merely proposing them. The goal is to keep durable knowledge accurate and discoverable, 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 replace or remove it.
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.
Treat this skill's activation as authorization to perform safe local maintenance writes within the current task's established scope. Do not ask for separate confirmation merely because the destination is project docs, a permitted memory update, an existing skill, or a new skill. Higher-priority system, developer, and user instructions, filesystem permissions, sensitive-data rules, and external side-effect boundaries still apply. Do not infer permission to commit, push, publish, message other people, or modify production systems.