Menu
Promote draft Nightmanager specs and their draft TODOs to ready state, then commit only those promotion changes.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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.
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.
| name | to-ready |
| description | Promote draft Nightmanager specs and their draft TODOs to ready state, then commit only those promotion changes. |
Promote reviewed Day Shift artifacts so /nightmanager can run. Perform the edits and Git commit; do not just describe them.
/to-ready: consider all specs/draft-*.md./to-ready <slug>: consider only exact specs/draft-<slug>.md; if missing, stop with no matching draft spec and make no changes.Skip/report a draft when:
specs/<slug>.md already exists;<title>, <human>, <yyyy-mm-dd>, other <...>);-, - , - [ ], - [ ] ).Do not reject - None, explicit deferred questions, or non-empty bullets.
A TODO belongs to a draft spec only when it is [draft] and has exact Spec: path specs/draft-<slug>.md in backticks. Promote only those TODOs:
[draft] -> [ready]Spec: specs/draft-<slug>.md -> Spec: specs/<slug>.mdDo not alter [blocked], [ready], [bug], [in-progress], [done], or unrelated TODOs. If no associated [draft] TODO exists, skip and say run to-issues (for exact slug, make no changes).
For each promotable slug:
specs/draft-<slug>.md to specs/<slug>.md.Status: draft to Status: active.promoting x,y,z specs.If nothing promotable, make no commit.
Report promoted specs, TODOs changed, commit hash if created, and skipped/invalid drafts with reasons.