codex-task-backlog-hygiene

Audit Codex tasks and archive completed chats while preserving unowned outcomes in BACKLOG.md.

4.8k|376|Updated Mar 16, 2023
One-click install
npx skills add https://github.com/EpicenterHQ/epicenter --skill codex-task-backlog-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-task-backlog-hygiene
Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/codex-task-backlog-hygiene
Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill codex-task-backlog-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex desktop task lists accumulate completed, superseded, and abandoned conversations, making it hard to see what work is actually active. This Skill audits the task list, classifies each task by current ownership, and archives stale chats without losing any future intent that exists nowhere durable.

Core Features & Use Cases

  • Ownership Classification: Sorts each Codex task into active, backlog-then-archive, archive, or ask-the-user buckets based on concrete next actions and durable records.
  • Backlog Preservation: Extracts explicitly desired future outcomes into a compact repository-root BACKLOG.md before archiving, using a minimal structured format.
  • Uncertainty Handling: Presents genuinely ambiguous tasks to the user with evidence on both sides instead of guessing, and reports exactly what was archived, kept, or left untouched.
  • Use Case: After weeks of Codex sessions, your active task list mixes finished reviews, abandoned experiments, and one feature idea never written down. Run this Skill to archive the dead threads, record the feature idea in BACKLOG.md, and keep only tasks with real next actions.

Quick Start

Use the codex-task-backlog-hygiene skill to audit my Codex tasks, preserve any unowned desired outcomes in BACKLOG.md, and archive the completed conversations.

Frequently Asked Questions about codex-task-backlog-hygiene

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

FAQPage Schema
How do I clean up my Codex task list without losing ideas?

Audit each Codex task by ownership, then archive completed or superseded threads. Before archiving, check whether the task holds an explicitly desired outcome recorded nowhere durable, and if so add a compact entry to BACKLOG.md first.

What should go into a project BACKLOG.md file?

A backlog entry should capture one explicitly desired future outcome with no active owner, using a desired result sentence, grounding reference, and a revisit trigger. Omit transcripts, agent plans, and speculative possibilities to keep the file scannable.

Does archiving a Codex task delete it permanently?

No, archiving is not deletion. Archived Codex tasks remain searchable and recoverable, so closing a completed conversation does not destroy its reasoning or history.

When should a blocked Codex task stay active?

A blocked task stays active only when the user expects to resume it soon. Otherwise, preserve its desired outcome in the backlog and archive the task so the active list reflects real ownership.

Can a dirty git worktree keep a Codex task active?

No, a dirty worktree alone does not establish active ownership. Preserve valuable files or commits through the appropriate Git or worktree workflow, then archive the abandoned task.