stepandel

Render pages with headless Chromium: screenshot, mobile/responsive layout review, viewport sweep, post-JS DOM, eval JS. Use for any visual/design/frontend QA task — see how a page actually looks rather than read its source. Triggers on: screenshot, render, mobile layout, responsive, viewport, breakpoint, design review, visual review, frontend QA, what does X look like, see the page, hydrated DOM, SPA, headless browser.

Orchestrate an epic — assess readiness, sequence sub-issues, implement all on a single branch, open one PR, and deliver a completion summary. Handles fresh epics, partially-completed epics, and crash recovery.

Linear project management integration. Provides tools for managing issues, comments, teams, projects, and issue relations via the Linear GraphQL API.

Investigate a bug or issue reported in a Linear ticket. Identify root cause, assess impact, implement the fix, and open a pull request.

Implement the solution for a Linear ticket and open a pull request. Full coding workflow — plan, implement, test, PR.

Prepare Linear tickets for the coding agent. Validates sizing (splits oversized tickets into sub-issues), researches tools/APIs involved, enriches context by scanning the codebase, and generates a focused implementation prompt.

Route a Linear ticket to the correct skill based on its action label (epic, research, prep, bug, execute, review — with or without

Create and edit pi cron jobs in .vera/crons/. Use when the user wants to schedule tasks, create cron jobs, edit cron schedules, or automate recurring workflows and prompts.

Test and validate PRs against ticket requirements. Use when a PR is ready for review — check out the branch, verify the build, run tests, and confirm all ticket acceptance criteria are met.

Handle a ticket from the Linear queue as the Engineering agent. Delegates implementation to coding agent, monitors progress, and manages the ticket lifecycle. Triggered by the openclaw-linear plugin when a ticket enters Titus's queue.

Handle tickets from project management tools and delegate coding tasks to Claude Code. Use when processing tickets, planning implementation, submitting PRs, or coordinating coding work.

Address review comments on a GitHub PR. Triages each comment as resolve-as-suggested, resolve-differently, or ignore, using project context from Linear tickets. Use when asked to go over PR review comments, address feedback, or resolve PR discussions.

Prep Linear tickets for a coding agent. Validates sizing (splits oversized tickets into sub-issues), researches tools/APIs involved, enriches context by scanning the codebase, and generates a focused Claude Code prompt. Use when starting work on a Linear ticket or when asked to prep/triage tickets.

Route Linear tickets based on labels. Use when processing unprepped tickets during heartbeat to determine the correct workflow and assignee. Handles Research Needed, Bug, Plan, and Slow modifier labels.

Handle a ticket from the Linear queue as the PM agent. Routes the ticket by labels, preps it with research/context/sizing, and assigns it to the right agent. Triggered by the openclaw-linear plugin when a ticket enters Juno's queue.

Handle a ticket from the Linear queue as the QA agent. Reviews the PR against acceptance criteria, runs build/test checks, and reports results. Triggered by the openclaw-linear plugin when a ticket enters Scout's queue.

Create and edit cron job definitions in .agent/crons/. Use when the user wants to schedule recurring workflow or prompt runs, adjust cron schedules, or validate cron YAML.

Picking the right built-in channel for outbound communication (SMS, voice, chat, email).

Surface typed UI cards in the console chat via the propose_card tool. Use when the user needs to take a configuration action (set up a channel, configure a webhook, install a skill) or when you want to post a standout notice. Covers when to use a card vs. prose, which kind to pick, and how the tool blocks until the user decides.

Edit the runtime setup via get_setup and patch_setup. Use when the user asks to change the agent model, edge model profiles, agent definitions, or channel display metadata. Covers what is editable, what is operator-only, and the JSON-Pointer patch format.

Create executable agent workflows in .agent/workflows/. Use when the user wants to define, scaffold, validate, or edit a multi-step workflow pipeline that uses tools, delegate steps, approval gates, or parallel branches.

Create and edit cron job definitions in .agent/crons/. Use when the user wants to schedule recurring workflow or prompt runs, adjust cron schedules, or validate cron YAML.

Picking the right channel for outbound communication (SMS, voice, chat, email). Prefer built-in channels over Composio third-party providers like Twilio.

Edit the runtime setup via get_setup and patch_setup. Use when the user asks to change the agent model, routing profiles, Composio trigger prompts, or channel display metadata. Covers what is editable, what is operator-only, and the JSON-Pointer patch format.

Create executable Assemblio workflows in .agent/workflows/. Use when the user wants to define, scaffold, validate, or edit a multi-step workflow pipeline that uses tools, delegate steps, approval gates, or parallel branches.

Surface typed UI cards in the console chat via the propose_card tool. Use when the user needs to take a configuration action (set up a channel, connect an integration, enable a trigger, configure a webhook, install a skill) or when you want to post a standout notice. Covers when to use a card vs. prose, which kind to pick, and how the tool blocks until the user decides.

Prepare GitHub issues for implementation. Validate sizing, break oversized work into smaller issues when needed, research external dependencies, enrich the issue body with concrete codebase context, and add a focused implementation prompt.

Review a GitHub pull request for correctness, consistency, edge cases, and test coverage. Post findings on the PR or linked issue. No code changes.

Linear project management integration. Provides tools for processing a notification queue, managing issues, comments, teams, projects, and issue relations via the Linear GraphQL API.

Add agentic shopping (AI-agent checkout) to an existing store or website. Wires up MPP (Machine Payments Protocol) checkout over Stripe Shared Payment Tokens plus the agent discovery layer (llms.txt, agent-storefront manifest, OpenAPI). Use when the user wants agents/LLMs to be able to discover, price, pay for, and buy from their store. Verifies Stripe prerequisites, installs code, and confirms the 402 payment flow works. Scope: stores where an agent can pay and be fulfilled immediately with NO user authentication or human-in-the-loop — not login-gated or manually-fulfilled checkouts.

Linear project management integration. Provides tools for processing a notification queue, managing issues, comments, teams, projects, and issue relations via the Linear GraphQL API.