Menu
Bootstrap an NHK workspace when first-time setup is needed or any required instruction, routing, governance, or archive surface is missing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Archive one completed NHK workstream when the human has explicitly approved its active-to-archive transition.
Repair NHK drift when an established workspace's instruction, routing, governance, archive index, or tracking descriptions no longer match reality.
Route NHK work when dependency readiness, instruction topology, foundation state, or lifecycle stage is unresolved.
Based on SOC occupation classification
| name | nhk-bootstrap |
| description | Bootstrap an NHK workspace when first-time setup is needed or any required instruction, routing, governance, or archive surface is missing. |
Establish or repair the minimum NHK foundation. Preserve correct existing surfaces and add or repair only what is missing or explicitly selected; do not rebuild a healthy workspace from scratch.
Reuse a welcome-to-nhk handoff only when it is for the current workspace and current NHK run, and its Route selects this skill. If the handoff is absent, unresolved, or stale, run welcome-to-nhk first. If it selects another route, hand off and do not continue bootstrap.
Use the handoff's dependency state, canonical instruction source, topology, and missing foundation surfaces as the bootstrap input. Do not persist the handoff. After bootstrap changes the foundation, rerun welcome-to-nhk before continuing any earlier upkeep or archive intent.
The finished workspace must have:
AGENTS.md or standalone CLAUDE.mdCLAUDE.md adapter importing canonical AGENTS.mdcoding-agent-guide.mddocumentation-governance.mdarchive/archive/README.mdSimple workspaces may keep these surfaces short, but may not omit them.
Once the canonical source is known:
coding-agent-guide.md from ../references/coding-agent-guide-template.mddocumentation-governance.md from ../references/documentation-governance-template.mdarchive/ when missing and add or repair archive/README.md from ../references/archive-readme-template.mdUse backticked literal paths for both companion docs. In Claude Code, only a thin adapter may import canonical AGENTS; neither thin nor standalone CLAUDE may @ import a companion doc.
Never overwrite correct project-specific content merely to match template wording.
Do not create root task_plan.md, findings.md, or progress.md merely because bootstrap runs. Create them only when the current work genuinely needs multi-session recovery, an active plan/spec, multiple packets, or explicit progress tracking. The archive foundation is still mandatory in a simple workspace.
If bootstrap is creating or structurally repairing the instruction surface, open only the generation contract that matches the handoff's canonical source: ../references/AGENTS-template.md or ../references/CLAUDE-template.md. Do not load the other platform template. Do not load an instruction template when only a companion or archive surface is missing.
CLAUDE.md must contain a valid import, only necessary Claude-specific notes, and no more than 35 lines; after producing thin mode, do not process standalone blocks.FINAL_VERBATIM content exactly unless the user approves a change.FINAL_ADAPT; include OPTIONAL_BY_COMPLEXITY only when justified.coding-agent-guide.md at or below 80 lines with one Task Routing table using Task or Symptom, Read First, Likely Change Surface, and Targeted Verification.documentation-governance.md at or below 100 lines and limited to document roles, active surfaces, the workspace/document map, lifecycle, naming/loading, and archive invariants.Before finishing:
archive/, and the archive index exist and cross-references resolve