メニュー
Check Claude Code version and identify new features relevant to the D-ND ecosystem. Use after Claude Code updates to discover what capabilities have changed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | version-check |
| description | Check Claude Code version and identify new features relevant to the D-ND ecosystem. Use after Claude Code updates to discover what capabilities have changed. |
After a Claude Code update, run this to understand what changed and whether the D-ND plugin should adapt.
The system_awareness hook reports Claude Code version at session start. If you see a version change, investigate.
# Check changelog
# Search web for: "Claude Code [version] changelog"
# Or check: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
| Claude Code Feature | D-ND Relevance | Current status |
|---|---|---|
| HTTP hooks | Could replace shell hooks for node messaging | Not yet used |
| Agent worktree isolation | Experimental branches per node | Available |
| Fast mode 1M context | Full context in fast mode | Available |
| Background agents | Async work across nodes | Available |
| Plugin marketplace | Public seed distribution | Ready to use |
| Auto-memory | Supplements our MEMORY.md system | Active |
| /simplify command | Post-session code review | Available |
| MCP servers | External tool connections | Available |
$ARGUMENTS
Business, outreach and public-relations manager for AI projects and technical teams. Use when an agent must turn a collaboration opportunity, partner request, portfolio update, public claim, outreach message, follow-up, sponsorship path or service proposal into a bounded decision, safe communication package and tracked next action without sending or publishing autonomously.
Deploy paper content from configured site_ready files to d-nd.com VPS. Handles md-to-HTML conversion, bilingual merge, figure path resolution, and pages.json update.
Five mechanical gates for any content publish pipeline with CMS + rendering layers. Prevents false security: 'API returned 200' does not mean 'visitor sees clean content'. Use when writing content to a multi-layer serving system (CMS API, static files, prerendered HTML, cached copies).
Multi-node consultation protocol for high-leverage decisions. Dispatches the same question to N independent LLM/agent nodes in isolation, then synthesizes their responses into a summa that exposes convergence (high-confidence claims), dissensus (real uncertainty zones), and emergent points (insights no single node produced). Reduces single-node training bias. Supports recursive escalation for stable-state convergence. Use for decisions that propagate via A14 cascade — seed updates, crystallizations, advisory→mechanical promotions, high-visibility copy, lab result interpretation.
Closure reflection protocol. After a significant work block concludes (feature shipped, session ending, major commit landed, cross-node coordination resolved), runs a 10-question interview that extracts meaning, impact, and next questions — then emits multiple audience-specific artifacts (changelog, external editorial, AI integration docs, memory crystal, backlog seed). Turns implicit maturation into explicit narrative. Use at the end of meaningful work, not after trivial edits.
Pre-commit check for public-facing copy (knowledge base definitions, page content, docs). Detects apologetic hedging — phrases that declare 'degrees of truth' (possible/necessary, current/future, one-of-many/the) and open a dualistic framing the model transcends. Use when drafting or reviewing any copy that describes the model, its transductions, or its tools.