
Create an ExecPlan from a locked refactor decision, PRD, RFC, or detailed problem statement, following the repo's PLANS.md. Use when the user asks for an exec plan, execution plan, or ExecPlan, or wants a decided refactor turned into a step-by-step plan.
Analyze Codex session logs for one repository, extract the repo-specific top-level conversations for a target day, summarize every user message in order, and surface the next best action. Use when the user asks what happened yesterday in a repo, which conversations touched a repo, what to work on next based on recent Codex work, or to reconstruct repo workstreams from session history.
Execute a pending execution plan from the .agent folder. Use when user asks to implement an execplan, execute the plan, run the pending plan, or mentions execplan-pending.md.
Analyze Codex rollout transcripts for one repository and time window, extract repo-scoped tool calls that failed, cluster repeated error patterns, and recommend the next agent/tooling improvements. Use when the user wants to inspect tool-call failures, operational friction, repeated command mistakes, patch failures, or prompt/tooling improvements based on recent Codex runs.
Update ARCHITECTURE.md after implementing an execution plan. Use when user asks to update architecture docs, sync architecture, refresh architecture after implementation, or mentions updating docs post-execplan.
Reads an existing ExecPlan, deeply analyzes every referenced file and code path in the codebase, then rewrites the plan with concrete, code-grounded improvements. Use when user asks to improve an execplan, review a plan, make a plan better, audit an execplan, refine a plan, strengthen a plan, or says "improve the plan."
Analyze a code repository (README.md, ARCHITECTURE.md, and lightweight codebase search) and create 3–5 new Beads issues via br (beads_rust). Use when the user asks to create/generate beads, seed a backlog, open tasks/issues, or wants 3–5 task ideas focused on reliability, new features, performance, security, refactors, docs, or marketing for a specific repo.