[DOCS] Rename 'context: fork' - term implies opposite of actual behavior

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/skills#available-metadata-fields

Section/Topic

The context field and its fork value

Current Documentation

"Set to fork to run in a forked subagent context. The skill content becomes the prompt that drives the subagent."

What's Wrong

The term fork implies copying parent state (like Unix fork(), git fork, etc.), but it actually means isolated/blank context. This is semantically backwards and causes confusion.

User expectation: context: fork = "fork from parent, inheriting conversation history"
Actual behavior: context: fork = "spawn isolated, no parent context"

This naming collision is compounded by:

1. Existing feature request #16153 proposing fork_context: true on Task() for full context inheritance
2. Existing feature request #20304 proposing isolated: true on Task() for zero context

The skill frontmatter's context: fork does what isolated: true describes, not what "fork" typically means.

Suggested Improvement

Option A: Rename fork to isolated or spawn

context: isolated  # Clearer - runs in isolated subagent context

Option B: Support both values with distinct semantics

context: fork      # Full parent context (true fork behavior)
context: isolated  # Blank context (current "fork" behavior)
context: inline    # Default - inject into current context

Option C: Match the Task tool proposal vocabulary

context: isolated      # Maps to proposed Task(isolated: true)
context: fork          # Maps to proposed Task(fork_context: true)
context: inline        # Default

Impact

Medium - Causes confusion but feature still works once understood

Additional Context

Related issues:

• #16153 - Proposes fork_context: true for Task() (full parent context)
• #20304 - Proposes isolated: true for Task() (zero parent context)

The naming inconsistency between skill frontmatter (fork = isolated) and proposed Task parameters (fork_context = full inheritance) will create further confusion if both ship as-is.