菜单
Record user feedback for the active Zoo spec without interrupting current work. Use only when explicitly requested, especially when the user gives feedback to address later during Zoo Heavy, Zoo Lite, Zoo Zero, or another running Zoo workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Close out a completed Lighto task: full validation, final report, rebase. Requires the task file path as input.
Tiered Lighto code review gate: scripted checks, parallel narrow checks, broad review. Invokable standalone on any diff, or as part of the Lighto workflow.
Lightweight spec-driven workflow: collaborative spec, top-level TDD implementation, tiered parallel review gate, one commit per subtask. Use only when explicitly requested.
Review a Lighto task file spec from all angles: flag omissions, fix uncontroversial problems, punt real decisions to the user. Requires the task file path as input.
Execute one Lighto subtask: plan, TDD, validate, browser-verify, review gate, commit. Requires the task file path and subtask number as input; use only on an existing Lighto task file.
Verify browser-visible Zoo behavior and capture focused UI evidence. Use only when explicitly requested.
| name | zoo-add |
| description | Record user feedback for the active Zoo spec without interrupting current work. Use only when explicitly requested, especially when the user gives feedback to address later during Zoo Heavy, Zoo Lite, Zoo Zero, or another running Zoo workflow. |
Read and follow .zoo/zoo.md if it exists.
Use this when the user explicitly asks to add feedback for later while a Zoo workflow continues.
Goal: preserve the feedback in the active workflow state without switching away from the current subtask.
User Input as a later user clarification.(future) subtask that addresses the feedback after the active (next) subtask.(next) subtask and current plan untouched unless the feedback explicitly invalidates them.