[BUG] Nested skill execution: parent skill cannot resume after nested skill completes

Resolved 💬 4 comments Opened Feb 27, 2026 by jaried Closed Mar 2, 2026

What's Wrong?
When a skill invokes another skill (nested skill execution), the parent skill loses its execution context after the nested skill completes. The parent skill does not resume — execution stops entirely, leaving the remaining steps of the parent skill unexecuted.

What Should Happen?
After a nested skill finishes execution, control should return to the calling (parent) skill at the point where the nested skill was invoked, allowing the parent skill to continue with its remaining steps.

Steps to Reproduce

  1. Create a parent skill that invokes a child skill using the Skill tool mid-execution (e.g., step 3 of 5 calls another skill)
  2. Run the parent skill
  3. When the child skill completes, observe that the parent skill does not resume

Actual Behavior
The parent skill halts after the nested skill returns. Steps following the nested skill invocation in the parent skill are never executed.

Expected Behavior
Parent skill resumes execution from the step immediately after the nested skill call.

Related Issue
Similar to #17351 (reported 2026-02-09, still open). This report provides an additional repro case from a different user on Windows.

Environment

  • Claude Code version: 2.1.61 (Claude Code)
  • OS: Windows 10 Pro (Build 10.0.19045)
  • Terminal: Windows Terminal 1.23.20211.0
  • Platform: Anthropic Max

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗