Results for “sub-agents”

Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.

Builds reliable browser automation skills by iteratively running a browsing task, reading the trace, and improving the navigation strategy until it passes consistently.

Use acpx as a headless ACP CLI for agent-to-agent communication, always inside an isolated SubAgent. Use when running coding agents through acpx, managing persistent ACP sessions, queueing prompts, consuming structured agent output from scripts, comparing the same prompt across multiple agents, or composing multi-agent workflows with defineFlow/decision/decisionEdge. Never invoke the claude adapter (nested-instance blacklist).

Investigates bugs, regressions, and crashes by dispatching four parallel read-only sub-agents, then ranks hypotheses and recommends the fastest proof or fix path.

Orchestrates group discussions between installed BMAD agents, enabling natural multi-agent conversations where each agent is a real subagent with independent thinking. Use when user requests party mode, wants multiple agent perspectives, group discussion, roundtable, or multi-agent conversation about their project.

Analyze codebase structure, generate domain-specific sub-skills (UI, Backend, Database, etc.), and create agent-guidance files to help AI agents navigate and develop consistently within a project. Use when onboarding to a new codebase, creating project documentation, or setting up agent guidance systems.

Agent skill for agent - invoke with $agent-agent

Design and author reusable subagents for specialized AI tasks. Use when the task needs an isolated agent persona, scoped system prompt, or reusable domain-specific assistant rather than a general skill.

This skill should be used when the user asks to "/do-agent", asks for "Execute complex tasks using multi-agent architecture with context protection", or needs the workflow previously provided by the /do-agent slash command.

Launches four parallel read-only sub-agents to review a git diff or file scope for regressions, security risks, performance issues, and contract gaps, then aggregates findings into a prioritized fix path.

Browse available agent personas and compose ad-hoc teams of up to 5 agents to work in parallel on a task, then synthesize their results.

Composes ad-hoc teams of AI agents from local markdown personas and dispatches them in parallel on a task, then synthesizes their outputs.

Decision-theoretic framework for agents embedded within the environments they model and act upon

Interactive agent picker for composing and dispatching parallel teams

Interactive agent picker for composing and dispatching parallel teams

Interactive agent picker for composing and dispatching parallel teams

Orchestrate multi-agent workflows with task decomposition, role assignment, handoff protocols, and per-session context budgeting.

Simulator.Company digital-twin & actor-agent specialist — talk to an agent AS an agent and delegate work to it. An agent is ANY actor whose `description` holds an "# Agent" competency profile (what it does, what it knows, whether it fits a task). The common case is a person: every workspace user has a 1:1 twin actor (`systemObjType="user"`) carrying that profile. But any actor can be an agent — a service/bot twin, a team or department, an organization, a process. This skill discovers the agent (`findAgent`), loads its profile (`getAgent`), adopts it as the persona, then either does the task, finds a better-suited agent, or hands the decision to the user (for a person: a task or a p2p message; for a non-person: propose another executor or run/trigger it as an actor). It is the actor-analog of `simulator-skills` (the `Skills`-form registry), but the registry is the workspace's agent actors. Use when the user wants to "delegate", "assign this to <someone/something>", "can <X> do this", "who/what should do this",

Design multi-agent systems with context isolation, supervisor or swarm coordination, explicit handoffs, parallel execution, and decision frameworks for when multiple agents are justified.

Interactive agent picker for composing and dispatching parallel teams

Decompose a task into parallel workstreams, assign agent ownership, run integration at dependency boundaries, and synthesize results.

Central status dashboard for the PA agent. Use when: owner asks 'what's the status', 'what are you working on', 'what's happening', or any status/overview question. Aggregates active tasks, open issues, monitored groups, pending follow-ups, and system health into one structured report.

Merges agent or review outputs into one deduplicated, evidence-linked, severity-ranked actionable report.

Creates and maintains minimal, high-signal AGENTS.md files for AI coding agents, enforcing research-backed best practices for concise agent documentation.

Coordinate multiple subagents/worktrees for parallel workstreams. Decomposes larger tasks into independent sub-tasks, dispatches each to a dedicated agent.

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

Agent skill for pseudocode - invoke with $agent-pseudocode

Agent skill for architecture - invoke with $agent-architecture

Progressively refines context retrieval in multi-agent workflows to solve the subagent context problem.

Orchestrating specialist AI agent teams as a meta-coordinator: decomposes requests into minimum viable chains, spawns each as an independent session, drives to final output. For multi-domain tasks.