executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
explicit-identityExplicit Identity Across Boundaries
Independent GitHub snapshot · Automated classification · Original documentation governs
Never rely on "latest" or "current" when crossing process or async boundaries.
Pass explicit identifiers through the entire pipeline. "Most recent" is a race condition.
--session-id $ID when spawning processessession_id = Claude Code session (human-facing)root_span_id = Braintrust trace (query key)turn_span_id = Braintrust turn within session// BAD: race condition at session boundaries
spawn('analyzer', ['--learn']) // defaults to "most recent"
// GOOD: explicit identity
spawn('analyzer', ['--learn', '--session-id', input.session_id])