[ENHANCEMENT] sub-task or subagent should support load skill and mode-rules

[Haijie-Lee]

Problem (one or two sentences)

Currently, when starting a subtask in orchestrator mode, the subtask cannot read the corresponding skill or rule based on its own mode.

Context (who is affected and when)

All user, When using orchestrator mode or other modes that may activate the subagent。

Desired behavior (conceptual, not technical)

The subagent should be able to dynamically load skills or rules based on the task content and its own mode prompt, just like a normal mode.

Constraints / preferences (optional)

It would be perfect if the work was like a commander directing many different executors; it doesn't need to be complicated.

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I have been investigating this issue and wanted to share my analysis before proposing a plan.

After tracing through the codebase, the current subtask creation flow via the new_task tool works as follows:

1. NewTaskTool.execute() calls provider.delegateParentAndOpenChild() with the target mode
2. delegateParentAndOpenChild() calls handleModeSwitch(mode) to switch the provider state to the child mode before creating the child task
3. When the child task generates its system prompt (in Task.getSystemPrompt()), it reads the mode from provider.getState(), which should reflect the child mode
4. SYSTEM_PROMPT() then calls getSkillsSection(skillsManager, mode) to filter skills by the child mode, and addCustomInstructions(..., mode, ...) to load mode-specific rules from .roo/rules-{mode}/
5. The skill tool is in ALWAYS_AVAILABLE_TOOLS, so it is available in all modes including subtasks

Based on this analysis, the current implementation appears to already support loading mode-specific skills and rules for subtasks. To help me identify where the actual gap is, could you clarify:

• Could you describe a specific scenario where a subtask fails to load skills/rules? For example: "I have a skill in .roo/skills-code/ and when orchestrator creates a subtask in code mode, the skill is not listed in the system prompt."
• Are you seeing this with skills specifically, mode-specific rules (.roo/rules-{mode}/), or both?
• Is this happening with the built-in new_task tool (orchestrator mode), or with a custom subagent mechanism?
• Could you share any logs or debug output showing the generated system prompt for the subtask? (The system prompt would show whether the AVAILABLE SKILLS section and Rules section are correctly populated for the child mode.)

This will help me pinpoint the exact failure point and propose a targeted fix.

Please tag @roomote in your response with the answers, and I will be happy to implement the fix once I have this information.