Write, refactor, debug, and review application code with validated boundaries, canonical domain types, explicit dependency lifetimes, pseudocode-like orchestration, local code over gratuitous helpers, deliberate effects and observability, and minimal critical-path tests. Use for substantive business logic, data modeling, state and error flows, API/CLI/env/queue/persistence/file/third-party boundaries, and design-focused code review.
Write, refactor, debug, and review application code with validated boundaries, canonical domain types, explicit dependency lifetimes, pseudocode-like orchestration, local code over gratuitous helpers, deliberate effects and observability, and minimal critical-path tests. Use for substantive business logic, data modeling, state and error flows, API/CLI/env/queue/persistence/file/third-party boundaries, and design-focused code review.
Use when reading, summarizing, analyzing, comparing, or extracting from Notion pages, databases, URLs, or docs in read-only tasks; prefer materializing the full target into a local temp Markdown, JSON, HTML, or text file before analysis instead of repeatedly reading MCP chunks; do not use for Notion create, update, or write operations.
Use when reading, summarizing, analyzing, comparing, or extracting from Notion pages, databases, URLs, or docs in read-only tasks; prefer materializing the full target into a local temp Markdown, JSON, HTML, or text file before analysis instead of repeatedly reading MCP chunks; do not use for Notion create, update, or write operations.
Use only when explicitly invoked for an expensive multi-agent code review and iterative fix loop. Reviews the current branch, PR, commit range, file list, or requested target for consistency problems, race conditions, missing static type safety, and inconsistent style or naming, then fixes verified issues one at a time with tests, commits, and push.
Use only when explicitly invoked for an expensive multi-agent code review and iterative fix loop. Reviews the current branch, PR, commit range, file list, or requested target for consistency problems, race conditions, missing static type safety, and inconsistent style or naming, then fixes verified issues one at a time with tests, commits, and push.
Design, critique, set, create, activate, or run durable Codex goals for persistent or long-running objectives. Use when the user says "set a goal", "start a goal", "activate goal mode", "persistent goal", "long-running objective", "goal tree", or asks for a goal with verifiers, durable state, approval gates, completion proof, bounded delegation, or parent/child subagent goals.
Query and manage Observe using the Observe CLI. Use when the user wants to access metrics, logs, traces, or other telemetry data about Laurel infrastructure.