nightmanager

Two-axis review of a diff — Standards (does it follow the repo's conventions and avoid code smells?) and Spec (does it implement what the ticket/spec asked?). Runs the axes as parallel sub-agents. Use to review a branch, PR, or work-in-progress.

Relentlessly interrogate a plan or design one question at a time until the goal, risks, and trade-offs are clear.

Implement one ready ticket or spec interactively in the foreground — the attended alternative to the AFK /nightmanager night shift. TDD where seams allow, then code review, then commit.

Investigate a question against high-trust primary sources and capture the findings as a Markdown note in the repo. Dispatches Nightmanager's librarian tool so you keep working while it reads.

Test-driven development reference — what a good test is, where tests go, the anti-patterns, and the rules of the red → green loop. Reference material for /implement and the night shift, not a workflow of its own.

Turn the current conversation into a draft local spec in specs/ using this repository's spec template and Nightmanager conventions. Synthesis, not an interview.

Break a spec, plan, or conversation into vertically-sliced Nightmanager tickets — local TODOs.md entries, each declaring what it delivers and what blocks it.

Plan a huge, foggy chunk of work — more than one agent session can hold — as a shared local map of investigation tickets, then resolve them one at a time until the way to the destination is clear.

Promote draft Nightmanager specs and their draft TODOs to ready state, then commit only those promotion changes.