LLMGraphDAGジョブのライフサイクルと registry 観察パターン

Capture LLMGraphDAG node results via onComplete and observe registry state from handlers.

3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/transreal/claudecode --skill llmgraphdag-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: LLMGraphDAGジョブのライフサイクルと registry 観察パターン
Source: https://github.com/transreal/claudecode/tree/main/Claude%20Directives/skills/llmgraph-dag-job-lifecycle
Command: npx skills add https://github.com/transreal/claudecode --skill llmgraphdag-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents confusion when LLMGraphDAG jobs disappear from the registry after successful completion, and when external observation of $iLLMGraphDAGJobs fails due to context resolution differences.

Core Features & Use Cases

  • Registry lifecycle awareness: Explains that fully successful DAG jobs are intentionally removed from $iLLMGraphDAGJobs, so LLMGraphDAGStatus may return Missing["JobNotFound", jobId].
  • Correct result capture pattern: Shows how to reliably extract node results via the onComplete callback and store them in external variables.
  • Safe registry observation: Describes why directly referencing ClaudeCode`$iLLMGraphDAGJobs externally can resolve to a different symbol, and provides the correct approach—observing from inside the node handler where context matches.
  • Targeted debugging checklist: Provides a verification list to avoid false diagnoses when testing DAG behavior.

Quick Start

Ask Claude Code to run an LLMGraphDAGCreate test that saves the final node result inside the job's onComplete callback rather than relying on LLMGraphDAGStatus after completion.

Frequently Asked Questions about LLMGraphDAGジョブのライフサイクルと registry 観察パターン

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does LLMGraphDAGStatus return Missing JobNotFound after a job completes successfully?

LLMGraphDAGStatus returns Missing["JobNotFound", jobId] because fully successful DAG jobs are intentionally removed from the $iLLMGraphDAGJobs registry upon completion. To capture results reliably, use the onComplete callback instead of querying the registry after completion.

How do I retrieve LLMGraphDAG node results without losing them from the registry?

To retrieve LLMGraphDAG node results reliably, save the final node output inside the job's onComplete callback and store it in an external variable. This prevents data loss when the registry automatically removes completed-success jobs.

Why does external inspection of $iLLMGraphDAGJobs resolve to the wrong context in Mathematica?

Directly referencing ClaudeCode`$iLLMGraphDAGJobs externally can resolve to a different symbol due to context resolution differences. Observe the registry state from inside the node handler where the context matches to avoid misinterpretation.

What is the best way to debug LLMGraphDAG jobs that disappear from the registry?

The best way to debug LLMGraphDAG registry issues is to use a targeted verification checklist that checks for intentional job removal, verifies onComplete result capture, and ensures registry observation happens inside the node handler for correct context resolution.

Can I use LLMGraphDAGStatus to check a completed DAG job in testing scenarios?

No, you cannot use LLMGraphDAGStatus to check a completed DAG job because successful jobs are purged from the registry. For DAG testing, capture deterministic node results via the onComplete callback rather than relying on post-completion status checks.