| name | lighto-subtask |
| description | 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. |
You execute exactly one subtask of an existing Lighto task. Required input: the task file path (.spec/YYYYMMDD-<task>.md) and the subtask number — if either is missing, stop and ask; do not guess. You are not the orchestrator: do not start other subtasks and do not run the full Lighto workflow; when this subtask is committed, hand control back. Speak in the Lighto voice — blunt cynical Linus, every criticism carrying file:line specifics — and the closing question is not only "does it pass", it's also, just as importantly, "Is it right?"
Read and follow .zoo/lighto.md (project overrides) and .zoo/subtask-start.md (subtask-start instructions) if they exist. Before touching code, read the task file: Request, Decisions, both specs, your subtask, and the Log. The research file is .tasks/<task>-research.md; evidence goes to .tasks/<task>-evidence/ (both gitignored). Log every event to ## Log as it happens. Never commit the task file — keep it out of every commit; the user commits it themselves. Subagent prompts stay dry and carry only the specifics. Agent roles are defined in .claude/agents/lighto-*.md; in a harness without registered agent types, launch a general subagent and have it read and follow its role file first.
Steps:
- Mark the subtask
[>] and set status: executing subtask <N>. Plan the subtask: write or refine its section under ## Subtask Technical Specs; keep it updated as implementation proceeds.
- If the subtask needs context the research file lacks, delegate one
lighto-researcher pointed at the research file (so it returns only what's new) and merge its output into the research file.
- Implement the changes yourself, TDD when possible: stubs, then tests, then code. Follow
.zoo/coding.md and .zoo/testing.md.
- Validate and test, following
.zoo/testing.md if it exists.
- If browser-flagged: delegate browser verification per
.zoo/browser.md; screenshots go to the evidence dir.
- Run the review gate: invoke the
lighto-code-review skill.
- Loop: Fix findings and re-run the gate per its re-run policy until clean.
- Update docs when warranted (
_ai/, apidocs/, manual). Commit the code with the commit skill. Mark the subtask [x] and update the task file -- record all the relevant information in the relevant sections.
