zoo-docs

Update Zoo durable docs after workflow completion to reflect code and tests.

5|1|Updated Aug 22, 2025

Search Tags:#documentation #governance #knowledge #process #learnings #retention #zoo

Ready to run

npx skills add https://github.com/andreyvit/zoo --skill zoo-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: zoo-docs
Source: https://github.com/andreyvit/zoo/tree/main/.codex/skills/zoo-docs
Command: npx skills add https://github.com/andreyvit/zoo --skill zoo-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps durable Zoo workflow learnings and public/internal docs synchronized with implemented code, preventing knowledge loss and drift over time.

Core Features & Use Cases

Update actual durable docs after Zoo task completion to reflect outcomes and decisions.
Capture and organize lessons, pitfalls, and best practices for future agents and maintainers.
Ensure consistency between docs, code, and tests across Zoo projects and teams.

Quick Start

Run Zoo Docs after finishing a Zoo workflow to update the durable documentation with the latest learnings and changes.

Frequently Asked Questions about zoo-docs

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

FAQPage Schema

How do I preserve workflow learnings and prevent documentation drift after project implementation?▼

To preserve workflow learnings and prevent documentation drift, run a post-implementation review to synchronize durable docs with outcomes, code, and tests. This ensures updates align with implemented changes and captures pitfalls for future agents.

What is the best way to capture cross-project knowledge and governance for Zoo docs?▼

The best way to capture cross-project knowledge and govern Zoo docs is to apply a structured post-implementation review process. This organizes lessons and best practices while ensuring documentation consistency across teams and projects.

How do I update durable documentation to reflect outcomes and decisions after a task completion?▼

Update durable documentation after task completion by applying a review process that reflects outcomes and decisions. This guarantees the public and internal docs are synchronized with the implemented code and tests.

Can I use a post-implementation review to ensure consistency between docs, code, and tests across teams?▼

Yes, you can use a post-implementation review to ensure consistency between docs, code, and tests across teams. It applies governance to Zoo docs and captures organized lessons for future maintainers.

Why does documentation knowledge loss occur and how do I synchronize it with implemented code?▼

Documentation knowledge loss occurs when durable docs drift from implemented code over time. Synchronize them by running a post-implementation review that aligns documentation updates with the latest code, tests, and decisions.

When do I need to run a Zoo docs update in my workflow?▼

You need to run a Zoo docs update after finishing a Zoo workflow. It updates the durable documentation with the latest learnings and changes, preventing knowledge loss and drift over time.