protoAgent

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.

/standup — an operational status report on everything this agent currently owns: tasks, goals, schedules, background work, and what needs the operator's call.

/writing-skills — the house discipline for authoring SKILL.md skills that behave predictably. Loads the rules; the skill_writer subagent applies them.

Use this whenever the user asks you to research a topic, find the current state of something, compare options, or gather background from the web — e.g. "what's the latest on X", "find the best approach to Y", "compare these three tools". Drives a scope → gather → gap-check → synthesize loop.

Use when the user just wants a friendly greeting or to test that the example plugin is wired up. Demonstrates a plugin bundling a skill alongside its tool.