Use before implementing any change that adds, removes, or modifies package behavior, public API, types, or contracts. Ensures the governing spec is updated before code is written and a verification test plan exists.

Mandatory verification loop after any SPEC.md or contract document change. Compares spec against implementation code, fixes code to match spec, repeats until zero discrepancies, then runs regression tests. Spec is always the source of truth — never modify the spec within this workflow.

Manages semantic versioning and public API surfaces for multi-package monorepos. Use when adding, changing, or removing exported interfaces, types, or functions to determine version impact and maintain compatibility.

Applies the Robota scenario verification loop by checking scope, preserving canonical ownership, re-recording only when necessary, and stopping on strict-policy failures. Use when scenario files, example flows, or execution-path behavior changes.

Guide Robota SDK usage patterns, constructor configuration, and migration from deprecated packages. Use when working on Robota setup, constructor options, or SDK migration.

Applies Robota's repository writing rules for `.design/`, general documentation, and conventional commit messages. Use when editing docs, ADRs, design notes, or preparing commit text.

Runs the standard Robota change loop by identifying impact, building affected scope, running targeted verification, and summarizing residual risk. Use when making or reviewing repository changes that should end in an explicit verification result.

Before modularizing or refactoring a package, analyze the code for extraction points, write characterization tests for current behavior, then modularize under test protection. Use when a package has monolithic files that need to be broken into testable modules.

Mandatory checklist after completing implementation work — SPEC verification, README update, npm publish, content/ docs update, docs site deploy

Provide pnpm monorepo build commands and workflow guidance. Use when running package builds, filtered builds, or discussing build order.

Guide plugin development workflows with validation, disable strategies, and error handling. Use when working on plugin development, plugin system changes, or plugin options validation.

Systematic per-package code review using six specialist perspectives (Correctness, Architecture, Type Safety, Security, Performance, Maintainability) with severity labels. Use when reviewing an entire package or a set of changed files for quality, compliance, and improvement opportunities.

Defines when to use each log level (error, warn, info, debug) and common logging anti-patterns. Use when adding or reviewing log statements in production code.

Governs the Robota harness by checking rule-skill-owner consistency, finding undefined terminology, spotting examples that violate rules, and preferring mechanical checks over duplicated prose. Use when editing AGENTS, skills, or repository guidance.

Provide execution caching workflows to reduce repeated runs and costs. Use when discussing cached execution, cache invalidation, or cache system operations.

Models success and failure explicitly in TypeScript using Result or Either-like flows instead of uncontrolled exceptions. Use when implementing predictable error propagation across async workflows.

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Applies Domain-Driven Design tactical patterns (Aggregate, Bounded Context, Value Object, Domain Event) to structure domain models with clear transactional boundaries. Use when designing domain objects, deciding ownership, or separating contexts.

Applies practical CQRS and event projection fundamentals in TypeScript systems by separating write and read concerns with deterministic projections. Use when read models diverge from write workflows or event-driven views are needed.

Applies consumer-driven contract testing to verify API compatibility between packages or services without full E2E tests. Use when designing or evolving API boundaries between loosely coupled modules.

Use when reviewing a package's class contract relationships (interface implementations, inheritance chains, cross-package port consumers) and updating its SPEC.md Class Contract Registry.

Guard against committing directly to protected branches (main, master, develop). Use before every git commit to ensure work happens on a feature branch.

Guides authoring of a new spec document. Ensures every required section is present and meets minimum quality before the item enters the gate pipeline. Does not validate gates or make approval decisions.

Orchestrator for the spec document gate pipeline. Reads current status from frontmatter, determines the next gate, invokes backlog-writer or backlog-gate-guard, and updates frontmatter status on PASS. Does nothing else.