Use to analyze an agent system's architecture or mechanisms from repository evidence, including follow-up questions and analysis documents. Exclude ordinary code review, implementation, fixes, and conceptual questions that need no repository evidence.
Run a Thread discussion with several members to compare perspectives, options or tradeoffs and produce shared notes. Applies to the host and invited contributors throughout that discussion; excludes solo work, unrelated messages and closed discussions.
Choose among Rovai messages, Tasks, Missions, history and Memory; coordinate parallel member requests, multi-step operations or recovery. For one known operation, use its command help directly.
Disciplined diagnosis for hard, intermittent, or performance bugs. Use when the user explicitly asks to diagnose, debug, find root cause, or investigate a regression, or when an earlier fix failed. Do not trigger for ordinary feature work or a simple compile error; a diagnosis-only request does not authorize…
Clarify a plan or design with one fixed Thread reviewer while maintaining confirmed domain language, current specifications and version decisions. Applies to the initiator and invited reviewer during that exchange; excludes solo questions, group debates and questioning without documentation work.
Clarify or stress-test a plan, requirement, design or decision through user questions and one fixed Thread partner's independent review. Applies to the initiator and invited reviewer during that exchange; use grill-duo-with-docs when confirmed project documentation must also be maintained.
Use to create a Rovai member or revise and confirm the unsaved identity card and avatar for that creation. Exclude profile questions, edits to existing members, and character or avatar designs without roster creation.
Maintain durable collaboration preferences, agreements and lessons when the user asks to remember, correct or stop using them, or current evidence warrants capture. Excludes temporary work, project facts, sensitive data and speculation.
Review a defined code change with two Thread members independently checking standards, quality and requirements. Applies to the initiator and invited reviewer through the final report; excludes solo review, undefined scope and implementation-only requests.
Test-driven implementation through red-green vertical slices at agreed public seams. Use when the user explicitly asks for TDD, test-first, red-green-refactor, or a feature or bug fix developed from a failing integration test. Do not trigger merely because tests will be added or updated after implementation.
Use when the user requests a Git worktree or a development task needs an isolated directory to create, find, reuse, hand off, or clean up. Exclude read-only work, non-Git repositories, and tasks that need no separate branch or directory.
Write and restructure documents consumed by coding agents, including Skills, AGENTS.md, CLAUDE.md, and documents reached through agent-facing pointers. Use for invocation wording, progressive disclosure, completion criteria, or pruning agent instructions; not for ordinary user documentation, product copy, or code…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: