orchestrator-core

Use this agent to run lint, typecheck, and build checks after code has been written. Returns a structured pass/fail report. Never invoke before writer has produced changes. <example> Context: Orchestrator needs to verify code written by the writer passes all checks. user: [orchestrator passes task description and list of modified files] assistant: [checker runs checks and returns structured pass/fail with error details] </example>

Use this agent to update docs or inline comments after a feature has been implemented, tested, and approved. Only invoke when the task changes a public API, module behavior, environment variable, or core architecture. Never touches source logic. <example> Context: A new feature was added. Orchestrator needs docs updated. user: [orchestrator passes diff and description of what changed] assistant: [documenter updates relevant doc files only] </example>

Use this agent to map relevant code paths and produce a structured context snapshot before writing or reviewing code. Invoke when you need to understand which files are involved in a task, what interfaces exist, and what conventions are in use — without making any changes. <example> Context: Orchestrator needs to understand which files to touch before implementing a new feature. user: [orchestrator passes task description] assistant: [reader returns structured snapshot of relevant files, interfaces, and conventions] </example>

Use this agent to find external patterns, library APIs, and internal prior decisions relevant to a task. Invoke when the task requires knowledge of external library APIs or when the task may have prior art in the project docs. <example> Context: Orchestrator needs to know how a library handles a specific pattern before writing code. user: [orchestrator passes task + research question] assistant: [researcher returns concise findings from web and docs] </example>

Use this agent to review code changes against project conventions after checker has passed. Returns APPROVED or a specific issue list with file paths and line references. Never auto-fixes — reports only. <example> Context: Checker passed, orchestrator needs a convention and quality review of the diff. user: [orchestrator passes diff and task context] assistant: [reviewer returns APPROVED or issue list] </example>

Execute an orchestrator-native plan from .claude/plans/, dispatching agents per the plan's agent map and enforcing the 5 invariants throughout.

Write an orchestrator-native implementation plan for a multi-step task, mapping each step to specific agents and respecting the 5 invariants. Saves to .claude/plans/.

Agent dispatch guide for this codebase. Defines the agent catalog, core invariants, and flexible working loop for any development task.

1 hook across 1 event