zoo-plan

Plan Zoo Workflow subtasks by researching code and maintaining the spec contract.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This planning skill helps teams coordinate Zoo Workflow subtasks by ensuring deep codebase research, strict spec maintenance, and actionable, tactical plans for the active subtask.

Core Features & Use Cases

  • Research-driven planning: consumes code, tests, docs, and production signals to produce a concrete plan anchored in reality.
  • Spec-as-contract: updates and preserves the whole-task contract (user input, spec, decisions, open questions, memory) and surfaces a real (next) subtask.
  • Subtask decomposition: splits work into independently testable subtasks with clear acceptance criteria, browser impact, and evidence plans.
  • Execution memory: preserves learnings from completed subtasks to replan future steps and avoid repeating mistakes.
  • Traceable decisions: records decision log and rationale to enable audits and rollback if needed.
  • Produces explicit HOW: focuses on concrete, shipable steps for the active subtask.

Quick Start

Follow the current (next) subtask's required actionable steps to implement the plan.

Frequently Asked Questions about zoo-plan

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

FAQPage Schema
How do I plan complex workflow subtasks with detailed tactical steps?

Research-driven workflow planning decomposes complex tasks into independently testable subtasks with clear acceptance criteria, browser impact notes, and concrete shippable steps by anchoring plans in codebase reality.

What is execution memory in software task planning?

Execution memory in task planning preserves learnings from completed subtasks to replan future steps and avoid repeating mistakes, maintaining a continuous record of decisions, rationale, and open questions throughout the project lifecycle.

How do I maintain a spec contract when updating project subtasks?

Spec-as-contract planning updates and preserves the whole-task contract—including user input, decisions, and open questions—while surfacing the next actionable subtask to ensure strict spec maintenance across complex projects.

Can I trace decisions and rationale for complex workflow subtasks?

Traceable decision planning records a decision log and rationale during subtask execution to enable audits and rollback if needed, capturing the reasoning behind spec updates and tactical steps.

Does research-backed planning work for projects requiring code and production signal analysis?

Research-backed planning consumes code, tests, docs, and production signals to produce concrete subtask plans anchored in reality, making it suitable for complex projects requiring deep codebase research before execution.

What's the best way to decompose work into independently testable subtasks?

Subtask decomposition splits work into independently testable units with clear acceptance criteria, explicit browser impact assessments, and evidence plans, producing tactical HOW-to steps for the active subtask rather than vague high-level goals.