Use a workflow only when the work fans out
Choose a workflow for tasks such as reviewing every feature in a large pull request, triaging many issues, or auditing every route for one failure class. The work should split into independent investigations and finish as one clear report.
Ask in natural language for a workflow and state the population, independent checks, verification standard, and final ranking or synthesis. Grok plans and launches the orchestration in the background.
Use a workflow to review each feature in this pull request, have independent skeptics verify every finding, and return one ranked report.Monitor phases and preserve completed work
Open /workflows to watch phases, agents, and progress. The official announcement says progress is saved while the run proceeds, so pause and resume should not redo completed work.
Treat the live view as an operational console: stop a bad fan-out early, check whether verification is actually independent, and review the final evidence instead of accepting scale as quality.
- Watch scope and agent usage.
- Require each finding to carry evidence.
- Keep the final synthesis accountable to verified results.
/workflowsSave successful orchestration, not guesses
Grok authors and smoke-checks workflow scripts from the request. Keep team workflows under .grok/workflows and personal workflows under ~/.grok/workflows; do not invent or hand-document an unverified file schema.
A saved workflow becomes its own slash command that accepts arguments. Use the built-in /deep-research for parallel sourced research, and review generated workflow behavior before making it a team dependency.
.grok/workflows/
~/.grok/workflows/
/pr-review 5137
/deep-research