[BUG] Parent skill halts entirely after nested skill completes — remaining steps never execute

What's Wrong?
When a skill invokes another skill using the Skill tool (nested skill execution), the parent skill stops executing entirely after the nested skill completes. The remaining steps defined in the parent skill are never run — the execution halts at the point of the nested skill call.

This is distinct from #17351, which describes control returning to the main session context. Here, the parent skill does not resume at all — its subsequent steps are completely dropped, regardless of whether context: fork or custom model directives are used.

What Should Happen?
After the nested skill finishes, execution should return to the parent skill at the step immediately following the nested skill invocation, and the parent skill should continue to completion.

Steps to Reproduce

1. Create a parent skill with 5 steps, where step 3 invokes a child skill via the Skill tool
2. Create a child skill with its own instructions
3. Run the parent skill
4. Observe that steps 4 and 5 of the parent skill are never executed after the child skill returns

Actual Behavior
The parent skill halts after the nested skill returns. No subsequent steps are executed. The session returns to the main context as if the parent skill had completed.

Expected Behavior
Parent skill resumes execution from the step immediately after the nested Skill tool call and continues until all remaining steps are complete.

Note

• Previously reported as #29191, which was incorrectly auto-closed as a duplicate of #17351.
• That issue has a comment explaining the differences in detail.
• Reproducible with standard nested skill invocation (no context: fork required).

Environment

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