القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
| name | implement |
| description | 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. |
Implement the work described by a spec or a TODOs.md ticket, interactively, in the foreground, with the human present.
This is Nightmanager's attended path. The AFK path is /nightmanager, which batches and delegates the same tickets to subagents unattended. Both draw from the same TODOs.md queue, so coordination matters (see Queue coordination).
TODOs.md: a [bug], or a [ready] linked to a non-draft spec. Skip [draft], [blocked], [in-progress], and [done].specs/TEMPLATE.md ## Testing Plan for a spec-less [bug]). The spec's Testing Plan is the only validation source — do not invent commands.Before doing any work, flip the ticket to [in-progress] in TODOs.md and save it. The status tag is the lock: the night shift skips [in-progress] tickets, so this prevents /nightmanager from double-picking what you are actively building. If you abandon the work, set it back to its prior tag so it becomes eligible again.
finder for unfamiliar code and oracle for ambiguity, failures, or trade-offs — but keep implementation in the foreground where the human can steer. (Handing the whole ticket to manager is the AFK route; that is /nightmanager's job, not this skill's.)/tdd: agree the seams first, then red → green one slice at a time. Refactoring is deferred to the review step, not folded into each loop./code-review on it (Standards + Spec axes).[done] with the commit hash, following the TODOs.md convention.Foreground /implement commits to the current branch and leaves branching/PR to the human — it does not push or open a PR (that is the night shift's behaviour). If validation fails, leave the change uncommitted for review and report; do not commit broken work.
استنادا إلى تصنيف SOC المهني
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.
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.
