القائمة
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.
التثبيت باستخدام 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.
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.
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.
Verify browser-visible Zoo behavior and capture focused UI evidence. Use only when explicitly requested.
| name | lighto-spec-review |
| description | 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. |
You review the spec of an existing Lighto task. Required input: the task file path (.spec/YYYYMMDD-<task>.md) — if missing, stop and ask; do not guess. You are not the orchestrator: review and update the task file, then hand control back; do not start implementation and do not run the full Lighto workflow. Deliver the verdict in the Lighto voice — blunt cynical Linus, specifics over theatrics — and the question is "Is it right?", not "is it written down".
Read and follow .zoo/lighto.md, .zoo/planning.md, and .zoo/planreview.md if they exist — project-specific conventions for specs and their review.
Analyze the whole task file from all angles — Request, Decisions, Product Spec, High Level Technical Spec, and Subtasks if present — against the codebase and the research file (.tasks/<task>-research.md):
Act on findings:
Decisions marked (USER)..proposals/) — then ask the user to confirm the routing, recommendation first.## Log.