codex-max

MANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.

Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Legacy compatibility alias for task-router-lite. Keeps older codex-max references working while using a thin Phase PLAN routing model.

Thin Phase PLAN router for codex-max. Select at most one primary execution skill and one optional secondary skill from the installed local skill surface.

Use when a significant technical decision should be recorded with context, alternatives, and consequences so the reasoning survives beyond the current session.

Use before creative or constructive work when requirements or solution shape are still unclear. Turns vague ideas into confirmed designs before implementation begins.

Optional browser automation workflow for interactive browser tasks, Playwright-style automation, and stable scraping/testing patterns.

Use when entering an unfamiliar repository or when the user asks to understand a codebase. Produces a structured onboarding view: stack, entry points, directory roles, request flow, and conventions.

Optional alternative docs-current layer that uses Context7-style documentation retrieval automatically for library/framework questions.

Use current library and framework documentation through Context7 when available, instead of relying on stale assumptions or training data.

Use for end-to-end testing of critical user journeys, especially browser-driven flows. Focus on stable, maintainable Playwright-style testing patterns and evidence collection.

Fact-forcing pre-action gate for codex-max. On this runtime, Bash can be gated by hooks while Edit/Write discipline is enforced through AGENTS.md and routing instructions.

Use for branching, commit, PR, merge, rebase, and release discipline. Adapts Git workflow guidance to codex-max multi-repo boundaries.

Maintainer-only curation workflow for codex-max. Build an evidence-backed plan to sort skills, hooks, docs, and related surfaces into runtime core, optional library, maintainer-only, or archive buckets.

Maintainer-only workflow for managing the codex-max curated skill library. Covers import, rewrite, promote, demote, optionalize, archive, and documentation synchronization.

Maintainer-only context compaction guidance for long curation or migration sessions. Suggests manual compaction at logical boundaries instead of arbitrary compaction points.

Research-before-coding workflow for codex-max. Check the repo, installed skills, libraries, and existing patterns before building custom code or adding dependencies.

Optional deep security audit workflow for broader DevSecOps, architecture, compliance, and residual-risk reviews beyond the normal security-review path.

Use when working with authentication, authorization, secrets, sensitive input, file uploads, new endpoints, or any feature with meaningful security risk.

Use when implementing a feature, bugfix, refactor, or behavior change where a failing test can be written before production code.