メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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.
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.
| name | research |
| description | 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. |
Answer a question from primary sources and leave a durable note behind.
Nightmanager already has a research engine — the librarian tool (OSS research, upstream code evidence, GitHub permalinks). This skill is a thin wrapper: it dispatches librarian to do the reading so the main session keeps working, then lands the findings as a Markdown file.
Dispatch librarian with the question. Instruct it to:
librarian is best at).Write the findings to docs/research/<slug>.md — one Markdown file, each claim citing its source (URL or permalink). If docs/research/ does not exist yet, create it; that is Nightmanager's convention for research notes. If the repo clearly keeps such notes elsewhere, match that instead and say where you put it.
Report the note's path and a short summary so the finding can feed a to-spec, a ticket, or a Wayfinder map ticket.
Keep the note factual and sourced — it is reference material for later planning, not a decision. Decisions still go through grill-me / to-spec.