Menu
/standup — an operational status report on everything this agent currently owns: tasks, goals, schedules, background work, and what needs the operator's call.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use this when asked to build, create, write, scaffold, or publish a protoAgent plugin — e.g. "make a plugin that …", "add a plugin for X", "package this as a plugin", "write a plugin that adds a tool/dashboard/workflow", "publish a plugin so others can install it". Covers the plugin contract (manifest + register()), the full contribution surface (tools, subagents, SKILL.md skills, workflows, console views, routes, MCP servers, config/secrets/settings), the conventional repo layout, testing, and distribution by git URL — with the safety model. Not for: using an already-installed plugin, or extending via a one-off SKILL.md skill or MCP server (smaller asks — see the Skills / MCP guides).
/due-diligence — validate a technology or architecture choice with the due-diligence workflow: codebase map + external research in parallel, antagonist + claim verification, and a cited adopt/build/defer verdict.
Use this when writing, drafting, or updating an Architecture Decision Record (ADR) or a plan document for this repo — e.g. "write an ADR for X", "record this decision", "author the ADR for this design", "draft the plan doc". Covers the house MADR shape, numbering, the index row, the docs-nav regeneration step, and the VitePress traps that fail the docs build.
/code-review — adversarial PR review via the code-review workflow: four parallel finder angles, dedup, an evidence-checking verify pass, and a findings report. Falls back to a two-axis inline review when the workflow isn't available.
When the user wants to SEE, render, visualize, preview, or "show me" a chart, diagram, mock-up, table, or interactive widget — render it with the show_artifact tool instead of writing files to disk.
/grill — a relentless interview that sharpens a plan or design before any of it is built.
| name | standup |
| description | /standup — an operational status report on everything this agent currently owns: tasks, goals, schedules, background work, and what needs the operator's call. |
| user_only | true |
| slash | standup |
Produce a status report on the work this agent owns — formatted for a fast scan, honest about gaps, ending in decisions rather than chatter.
Collect from every surface this instance actually has, in parallel where the
reads are independent (task_batch for anything that needs digging). Skip a
surface silently only if its tools aren't installed; if a read fails, say so
in the report rather than omitting it:
## Owned now
- 🟡 <in-flight item> (state — what it's waiting on)
- ⬜ <queued item>
## Done since last standup
- ✅ <item> (evidence: link/id)
## Gated / blocked
- 🚨 <item> — <what unblocks it, and whose move it is>
## Schedule
- <job> — next fire <when> (or "no scheduled jobs")
## Needs your call
- <decision> — <your recommendation>
Conventions: ✅ done · 🟡 in flight · ⬜ queued · ⬛ deferred (reason inline) · 🚨 blocked/escalation (sparingly). Don't oversell — half-done is more honest than an inflated status. Name blockers by id, not vibes.
The report is ephemeral: deliver it in chat, don't persist it anywhere.