Convert an implementation, debugging, release, UI, backend, security, or research request into a concrete pass/fail acceptance checklist before code changes start. Use when Codex needs blocking success criteria, scope boundaries, verification targets, or a task note for Klimkit-managed work.
Diagnose bugs, failures, flaky behavior, broken tests, CI failures, or unexpected production signals with a reproduce-first workflow and Klimkit proof. Use when the user asks to debug, investigate, root-cause, fix a failure, or explain why behavior changed.
Interview the user relentlessly about a plan, design, architecture, product decision, workflow, or release choice until shared understanding is reached, using repo and web research to prioritize the most important unresolved questions while recording the considered question shortlist, each asked question, and each approved decision in a Klimkit task note. Use when the user asks to be grilled, stress-test a plan, resolve design branches, clarify tradeoffs, or turn vague intent into explicit decisions.
Run Klimkit's full implementation workflow for code, docs, release, configuration, UI, backend, security-sensitive, or proof-producing changes. Use when the user asks Codex to implement, fix, refactor, release, migrate, wire up, or complete non-trivial repository work with checklist, verification, reflection, and final review.
Write a concise cross-task reflection note after verification and before final review for non-trivial Klimkit work. Use when Codex should connect the current task to prior work history, patterns, risks, or future process improvements.
Check, explain, or set up Klimkit static proof-report serving for `docs/work` HTML reports and Tailscale URLs. Use as the fallback when native hosted publishing (Claude Code Artifacts, Codex Sites) is unavailable and a task needs report-server readiness, `/reports/` links, Tailscale Serve verification, or troubleshooting report visibility.
Set up Klimkit's docs-first repo context for agent work. Use when adding the `docs/work/` journal layout, repo skill pointers, config state, or onboarding instructions to a project that should use Klimkit workflows.
Implement behavior changes with narrow red-green-refactor loops and Klimkit proof. Use when adding features, fixing bugs with clear expected behavior, changing shared contracts, or when the user asks for TDD or test-first work.