bens_indispensable_skills

Extract decisions, action items, new context, and insights from the current session into LEARNINGS.md and auto-memory. Run before ending any substantive conversation.

Capture a lightweight work item into BUGS.md, NEXT_STEPS.md, DEFERRED.md, or recommend the feature workflow. Use when a bug, fix, small follow-up, next step, deferred idea, or possible feature comes up during development.

Use when seeking a second opinion from OpenAI Codex on documents, specs, plans, or other non-code-diff content.

Use when delegating code implementation to Codex CLI with Claude-managed decomposition, context scoping, and verification.

Use when requesting an OpenAI Codex review of the current branch with documentation research and cross-AI verification.

Detect split data source anti-patterns and scattered business rule duplication where the same logic is reimplemented across multiple files and languages. Catches semantic duplication that syntactic tools like jscpd miss. Use at phase checkpoints or when investigating data consistency issues.

Use when determining how an AI coding agent can autonomously run and verify a specific user flow end to end before implementation.

Identify high-impact innovative additions to the current app or plan. Use when planning next features, during strategic reviews, or when the user asks for creative ideas.

Search past conversations with Claude Code and Codex CLI. Finds matching excerpts across all sessions with metadata (date, project, agent). Use when looking for a past discussion, decision, or piece of context from any previous session.

Review BUGS.md and NEXT_STEPS.md together, rank what to work on next, and update lightweight work tracking files when useful. Use when deciding between bugs, fixes, and small next-step work.

Use when analyzing product UI/UX through code review, product context, pattern research, prioritized recommendations, or design system setup.

Update documentation after commits. Syncs README, AGENTS.md, CHANGELOG, and docs/ with code changes. Use after commits or to analyze working tree changes.

Summarize all possible work across features, bugs, next steps, deferred items, and archived/completed work. Use when the user asks what can be worked on next or asks for status across work tracking files.