AgentCompany

Pick the right worker class for each Issue. Use every time you assign an Issue; wrong routing wastes tokens and creates rework.

Break a Company Goal into 3-10 atomic Issues. Use when a Goal arrives with no pre-existing plan and you need to produce a shippable work list.

Ship the smallest change that solves the Issue. Use on every implementation task; scope creep is the default failure mode of executors.

Run build/test/lint and read the actual output before claiming done. Use on every implementation task, at the end.

Start implementation with a red test. Use on any bugfix or new behavior — not on refactors or style changes.

Report research results in a form other agents can act on. Use at the end of every Explorer session.

Find files and code patterns fast. Use for every codebase question that starts with "where is X" or "how is Y used".

Pick the 3-5 files that an Executor must open first. Use as the last step of writing any implementation plan.

Produce a plan an Executor who has no shared context can follow. Use at the end of every Planner session.

Combine behavioral signals with output classification before intervening. Use every time the Psychologist considers dispatching an intervention.

Craft interventions that name the failure mode and offer the opposite move. Use when composing instructions-inject or board-comment content.

Walk every review through the same checks in the same order. Use on every Reviewer task; skipping steps is the

Catch yourself when you're about to approve without verifying. Use during every Reviewer session; it's a self-check, not a one-off step.

Create new agents in PetAgent with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.

Interact with the PetAgent control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any PetAgent API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for PetAgent coordination.

PetAgent UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design tokens, typography, status/priority systems, composition patterns, and the /design-guide showcase page. Always use this skill alongside the frontend-design skill (for visual quality) and the web-design-guidelines skill (for web best practices).

Create new PetAgent plugins with the current alpha SDK/runtime. Use when scaffolding a plugin package, adding a new example plugin, or updating plugin authoring docs. Covers the supported worker/UI surface, route conventions, scaffold flow, and verification steps.