Claude Code plugin (with an opencode port): describe a change and it researches, builds in slices on the cheapest model that fits, checks with tests and an independent review, and keeps going while you are away.
Skill Claude CodeCodex
Run an approved ac plan to completion, wave by wave, with cost-tiered workers, per-wave verification and a final review. Loaded by /ac/execute; the request carries a plan slug or path plus flags.
Skill Claude CodeCodex
Plan a change: research in parallel, ask only the decisions the user must make, write a tiered plan. Writes no code. Use only when the user asks for a written plan, runs /ac/plan, or passes a .ac/tasks/.yaml file. Request text: [--auto] [--lane] [--slug ] [--revise] .
Skill Claude CodeCodex
Away mode: carry the run in progress, or a new request, to completion unattended, ending at one verification gate. Use when the user runs /ac/auto or says in any language they are leaving and the work should go on until done, even while another flow is active; not for open-ended audits. Request text: [request, and any…
Skill Claude CodeCodex
Test recent work the way a QA engineer would: derive cases from the requirement and the diff, run them against the live app, fix critical and high findings, retest once. Use when the user asks for QA, a test pass or a browser walk-through, or the execute skill reaches Phase 3e; never start it unasked.
Skill Claude CodeCodex
Turn a large request into a reviewed roadmap of bundles and drive them through parallel ac/lane worktrees. Use when a request is too large for one plan and splits into bundles that can run in parallel worktrees; ends in one approved push. Request text: [--lanes N] [--max-workers N].
Skill Claude CodeCodex
Split the working-tree changes into atomic commits, preflight and push them; also rebase, squash and trace history. Add --no-push to the request when the user only asked to commit. Use when committing, rebasing, squashing, cherry-picking or tracing history; GitHub issues and PRs are ac/github-cli.
Skill Claude CodeCodex
Write or audit a visual-identity DESIGN.md: design tokens plus rationale in the Google Labs format, for UI agents. Use when a UI needs a brand or style spec or a token file for the frontend-design skill; the architecture doc is the architecture-md-writer skill.
Skill Claude CodeCodex
Run a medium or large request on the main thread: parallel research, interview, build in slices, oracle review. Use before building anything that touches several files, an unfamiliar area or an open behaviour choice; not for a one-file change or an explicit /ac/plan.
Skill Claude CodeCodex
Build distinctive, accessible web and mobile UI from a committed design direction and token plan. Use when building or restyling pages, screens, components or Flutter widgets, or from a DESIGN.md or Stitch design; not for backend work.
Skill Claude CodeCodex
Work with GitHub repositories, issues, PRs, releases and Actions runs through the gh CLI instead of web fetches. Use when researching a GitHub repository or reading and changing its issues, PRs, releases and Actions runs; local commits and history are ac/commit.
Skill Claude CodeCodex
Turn an idea into a feasibility-checked PRD and a parallel-ready roadmap through research and an interview. Runs when the user types /ac/product with an idea to specify before any planning; not for a change that is already specified.
Skill Claude CodeCodex
Write or audit a PROJECT.md (what, scope, constraints, decisions) for agents; commands and conventions go in AGENTS.md. Use when creating or updating a project overview doc, or when agents keep re-proposing ruled-out work.
Skill Claude CodeCodex
Write or audit an ARCHITECTURE.md for agents: boundaries, invariants with verify commands, flows and a change guide. Use when creating or updating the architecture doc, or when agent changes keep landing in the wrong place; a UI style spec is the design-md-writer skill.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: