Use this skill when the user wants a Claude Code-native companion workflow rather than a one-off command.

Best fit

Reach for claude-code-companion when the user wants one or more of these outcomes:

break a Claude Code task into review-first, implementation, and verification stages
continue a prior Claude Code effort without overpromising hidden persistent threads
coordinate bounded follow-up work after an earlier review or diagnosis
decide when work should stay in the foreground versus be structured as a follow-up process
standardize how Claude Code handles multi-step task continuation inside the current repository

Positioning

Skill	Best for
`claude-code-companion`	Companion-style orchestration inside Claude Code itself
`codex-companion`	Codex-specific background jobs, resumable Codex task threads, and runtime lifecycle commands
direct Claude Code usage	Simple one-shot reads, edits, tests, and short implementation loops