grp06

Execute an approved .agent/goals plan through slop-janitor's goal runner, defaulting to .agent/goals/active when no explicit plan path is provided.

Turn a freeform idea, brief, or discussion into a durable sequential goal plan under .agent/goals/ for later execution by slop-janitor goals run.

Create a long-horizon meta-plan from a user brief, PRD, RFC, or dictated discussion. Use when the user wants to capture a multi-slice project in a durable parent artifact before creating child ExecPlans.

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.

Review the latest implemented work item or completed ExecPlan with fresh eyes, fix obvious issues immediately, rerun verification, and record the result. Prefer the new `.agent/work/` workflow, but preserve backward-compatible support for older `.agent/done/` ExecPlans.

Read an existing ExecPlan, deeply analyze every referenced file and code path, and rewrite the plan with concrete, code-grounded improvements. Prefer work-item plans under `.agent/work/`, while preserving backward-compatible support for older singleton plan files.

Improves an existing ExecPlan with a two-wave subagent workflow: first specialized reviewers audit factual accuracy, adjacent code, design quality, validation, and self-containment, then closure reviewers hunt residual gaps after a provisional rewrite before the parent produces the final plan. Use when the user asks to improve an execplan with subagents, audit a plan using parallel reviewers, strengthen an execplan via delegation, or says "execplan-improve-subagents".

Search a repo for the top 3-5 materially different refactor opportunities, record the evidence for each, and create a work item for later selection and planning. Use when the user wants the best refactor, highest-leverage cleanup, architectural simplification, boundary extraction, duplication removal, or a shortlist of strong refactor options before choosing one.

Compile a completed Grill Me session, transcript, or decision discussion into a durable work item under `.agent/work/`: write `decision.md`, initialize `meta.json`, create an ExecPlan, run configurable `execplan-improve` passes, and invoke Goalcraft to activate a Codex `/goal` that executes the ExecPlan lifecycle. Use after grilling, when the user says "GrillCraft", "turn this grill into a goal", "create the ExecPlan and goal", "run Goalcraft after this grill", or asks for N ExecPlan improvements.

Review the latest implemented work item or completed ExecPlan with fresh eyes, fix obvious issues immediately, rerun verification, and record the result. Prefer the new `.agent/work/` workflow, but preserve backward-compatible support for older `.agent/done/` ExecPlans.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on a design, pressure-test an architecture or implementation approach, or explicitly says "grill me".

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.

Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work. Use when the user asks to write, improve, format, sharpen, stress-test, or activate a Codex goal, thread goal, durable goal, or /goal prompt.

Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work. Use when the user asks to write, improve, format, sharpen, stress-test, or activate a Codex goal, thread goal, durable goal, or /goal prompt.

Investigates vague or specific leads, suspicions, public-records ideas, and partially drafted requests into high-impact FOIA request candidates, then drafts polished federal FOIA requests. Use when a user wants deep web research, existing-record discovery, prior FOIA search, agency routing, clarification questions, or final drafting for a FOIA, public records, government transparency, waste, fraud, oversight, or accountability request.

Use when the user wants Codex to use Grok in the in-app browser to find employees at a supplied list of companies who match a supplied role or role family, then export direct X/Twitter handles to a CSV. Trigger for prompts like "find developer relations people at these companies", "use Grok to find AI engineers at this company list", or "make a company,handle CSV from Grok results".

Sets up a local Linq SMS to Codex bridge end-to-end: normalizes the user's US phone number, discovers the Linq sandbox send-from number and API key in the Codex in-app Browser, scaffolds a Node webhook server, starts a public tunnel, creates the Linq webhook subscription, saves the signing secret, and validates Codex replies. Use when the user asks to connect Linq texts, SMS, iMessage, or a Linq number to local Codex/Codex App Server behavior.

Scaffold a minimal Next.js App Router app and configure it end to end with Nango Connect UI for a GitHub connection. Use when the user asks to create a working Nango, GitHub OAuth, connection-demo, or nango-demo app from scratch and wants Chrome used for Nango dashboard setup.

Scaffold a minimal Next.js React app and configure it end to end with the official Auth0 React SDK plus Auth0 dashboard callback, logout, and web-origin settings. Use when the user asks to create a working Auth0 React, Next.js, Universal Login, or auth0-demo app from scratch and wants Chrome used for Auth0 dashboard setup.