ultrawork

**Used by**: `ultrawork.md`, `ultrawork-plan.md`

**Used by**: `ultrawork.md`, `ultrawork-plan.md`

**Used by**: `ultrawork-plan.md` (interactive mode only)

**Used by**: `ultrawork.md`, `ultrawork-exec.md`

**Used by**: `ultrawork.md`, `ultrawork-exec.md`

Use this agent to create ADR from design documents and update permanent project docs after verification passes. Examples: <example> Context: Verifier returned PASS, session moving to COMPLETE. user: "Verification passed, finalize the design document" assistant: "I'll spawn the documenter agent to create an ADR and update permanent docs." <commentary>Documenter reads evidence and task results, creates ADR in docs/adr/, updates permanent docs, then deletes the plan document.</commentary> </example> <example> Context: All tasks resolved, verification complete. user: "Update the design doc with actual outcomes" assistant: "I'll spawn the documenter agent to convert the planning artifact into a permanent record." <commentary>Documenter creates ADR, enriches permanent docs (ARCHITECTURE.md, API.md, etc.), and removes the plan.</commentary> </example>

Use this agent for fast codebase exploration in ultrawork sessions. Gathers context, writes detailed findings to exploration/*.md, updates context.json summary. Examples: <example> Context: Ultrawork session started, need to understand the codebase before planning. user: "Start ultrawork for adding authentication to this project" assistant: "I'll spawn an explorer agent to analyze the codebase structure and existing patterns." <commentary>Explorer runs first to gather context about project type, tech stack, and existing patterns before planning.</commentary> </example> <example> Context: Planning phase needs specific information about a subsystem. user: "The planner needs to understand how the database layer works" assistant: "I'll spawn a targeted explorer to investigate the database implementation." <commentary>Targeted exploration for specific areas when overview is insufficient.</commentary> </example>

Use this agent for auto-mode planning in ultrawork sessions. Reads context from explorers, makes automatic decisions, creates task graph. Does NOT spawn sub-agents. Examples: <example> Context: Exploration phase complete, context.json and exploration/*.md files exist. user: "Exploration is done, now create the implementation plan" assistant: "I'll spawn the planner agent to analyze the gathered context and create a task graph." <commentary>Planner runs after explorers to design implementation based on discovered patterns.</commentary> </example> <example> Context: User wants ultrawork in auto mode without interaction. user: "Run ultrawork in auto mode for refactoring the database layer" assistant: "I'll spawn the planner agent to automatically create the task breakdown." <commentary>In auto mode, planner makes decisions without user confirmation.</commentary> </example>

**Minimize dependencies, maximize parallelism.**

Without clear criteria:

Architecture design review skill for reviewer agents. Component boundaries, separation of concerns, modularity, and design pattern validation. Use during PLANNING phase to validate design decisions and VERIFICATION to ensure adherence.

API design, database operations, error handling, and backend architecture patterns. Use when creating APIs, database schemas, or server-side logic.

Code quality verification skill for reviewer agents. Provides checklists for logic clarity, error handling, maintainability, and performance. Use during VERIFICATION phase to assess implementation quality.

Code consistency and pattern adherence review skill. Naming conventions, style consistency, pattern usage, and project standards validation. Use during VERIFICATION to ensure codebase uniformity and maintainability.

This skill provides guidance on accessing session data efficiently in ultrawork. Covers JSON vs Markdown rules, token efficiency rationale, and common patterns. Required knowledge for all ultrawork agents (explorer, planner, worker, verifier, reviewer).

11 hooks across 7 events