zoo-lite

Coordinate Zoo 2.1 workflows with delegated research, review, and browser-verification subagents.

5|1|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/andreyvit/zoo --skill zoo-lite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoo-lite
Source: https://github.com/andreyvit/zoo/tree/main/.codex/skills/zoo-lite
Command: npx skills add https://github.com/andreyvit/zoo --skill zoo-lite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zoo Lite provides a structured, plan-driven framework to execute complex tasks by coordinating a top-level orchestrator with research, browser verification, and review subagents, ensuring reproducible plans and traceable results.

Core Features & Use Cases

  • Spec-based orchestration of Zoo 2.1 workflows with delegated subagents for research, review, and browsing
  • Built-in planning loop: zoo-plan, plan_reviewer, plan uberreview, and evidence-driven execution
  • Browser-impact aware with dedicated browser_verifier reporting and evidence
  • Bureau MCP-driven task lifecycle with clear reports and durable docs

Quick Start

Start a Zoo Lite session and run zoo-plan to define the first (next) subtask

Frequently Asked Questions about zoo-lite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate complex planning workflows with research and browser verification agents?

Spec-driven workflow orchestration coordinates a top-level planner with delegated research, review, and browser-verification subagents. It executes formal planning cycles and uses evidence-backed validation to ensure reproducible plans and traceable results across implementation and reviews.

What is a spec-based task lifecycle and how does it manage subtasks?

A spec-based task lifecycle uses a Bureau MCP-driven process to maintain a single active next subtask at any time. It enforces a cadence of plan, review, and uberreview phases, ensuring complex tasks progress sequentially with structured evidence management and durable documentation.

How do I start a spec-driven workflow session for complex task planning?

Start a workflow session by initiating the orchestrator and running the planning command to define the first next subtask. This generates the initial formal plan, establishing the structured execution loop for subsequent research, implementation, and browser-verification phases.

Does this workflow orchestration framework support browser-impact verification?

Browser-impact verification is supported through dedicated browser_verifier subagents. These agents execute checks during the workflow lifecycle and generate mandatory evidence reports, ensuring that implementation changes are validated against actual browser behavior.

When should I use a spec-driven workflow orchestrator instead of a standard agent?

Use a spec-driven orchestrator for complex tasks requiring formal planning cycles, bounded research questions, and multi-phase validation. Standard agents lack the structured plan, review, and uberreview cadences needed for reproducible plans and evidence-backed execution across multiple subagents.

What are the limitations of using a plan-driven workflow with delegated subagents?

Plan-driven workflows with delegated subagents require mandatory frontmatter in SKILL.md and impose strict plan/review cadences. This overhead makes them less suitable for simple, single-step tasks where lightweight execution is preferred over formal planning cycles and evidence management.