new_task

The new_task utility enables Sypha to initialize Subtasks. This is a critical feature for complex, multi-phase initiatives where maintaining a single, massive conversation thread would lead to fragmented context or token limitations.

Parameters

• mode (required): The operational persona assigned to the new subtask (e.g., code, architect).
• message (required): The specific objective or problem statement for this isolated task.

Execution Flow

1. State Preservation: The primary "parent" task is paused, and its current state is securely cached.
2. Context Isolation: A fresh "child" task is launched in the designated mode, utilizing a dedicated, clean conversation history.
3. Targeted Completion: You and Sypha work exclusively on the sub-objective within this more focused environment.
4. Resumption: Upon completion (via attempt_completion), the subtask's results are summarized and transmitted back to the parent task, which then resumes with the new data integrated.

Strategic Advantages

• Component Isolation: Keeps architectural strategy and brainstorming separate from active coding and implementation.
• Role Optimization: Use architect mode for designing a system, then delegate the implementation to a code mode subtask.
• Improved Performance: Smaller, focused threads are significantly faster, more reliable, and more context-efficient.

Implementation Example

<new_task>
  <mode>architect</mode>
  <message>Examine the secondary service layer and propose a refactoring plan to support async data streams.</message>
</new_task>