andreyvit

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.

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.

Archive completed Zoo spec files and resolved proposal files. Use when Codex is asked to clean up finished `.spec` work, move completed specs into an `archived/` subfolder, or move fully implemented/rejected proposals into an archive, while honoring repo-local Zoo path overrides.

Rant, swear, and insult like Linus Torvalds on the LKML — brutally blunt technical criticism. Use when user asks for Linus review/voice or for swearing.

Terse writing/comm style. Use for agent messages, skills, instructions, memories, docs, comments, commit messages and similar.

Record user feedback for the active task without interrupting work. Use only when explicitly asked to add, remember, or handle later.

Verify browser-visible behavior and capture focused UI evidence. Use after implementation for browser-impact work or when explicitly requested.

Archive completed Zoo spec files and resolved proposal files. Use when cleaning finished `.spec` work, moving completed specs into `archived/`, or moving implemented/rejected proposals into archive while honoring repo-local Zoo path overrides.

Tiered code review gate: tests, scripted checks, narrow parallel checks, broad review. Invokable standalone on any diff or inside Zoo workflow.

Update durable documentation for completed Zoo work. Use when a Zoo docs writer or orchestrator should preserve practical learnings, behavior, or public documentation changes.

Manual deployment-safety validation for unpushed commits or user-specified changes. Use only when explicitly requested, especially in Codex /goal or Claude /loop, to hunt production rollout failures, legacy-data and migration hazards, mixed-version issues, and other real deployment risks before declaring safe or unsafe.

Track task steps and write reports to preserve context across agent sessions and avoid forgetting user intentions.

Do planreview step of the PLANNING phase of star-team workflow.

Do research step of the PREP phase of star-team workflow.

Run complex tasks successfully by utilitizing a development team with famour personalities. Use when

For research steps of the star-team workflow.

Do techspec step of the PLANNING phase of star-team workflow.