Skip to content

Conversation

@xlyk
Copy link
Contributor

@xlyk xlyk commented Jan 28, 2026

Summary

  • Add write_plan tool for creating detailed task plans with title, explanation, and actionable steps
  • Add planner sub-agent specialized for breaking down complex tasks into structured plans
  • Update system prompt documentation for both new capabilities

Details

write_plan Tool

Creates detailed task plans distinct from update_plan (which tracks progress):

  • title: Plan title
  • explanation: High-level explanation
  • steps[]: Array of steps with step description and status (pending/in_progress/completed)

planner Sub-agent

Specialized for task decomposition with structured output format including:

  • Plan title and overview
  • Steps with descriptions, dependencies, acceptance criteria
  • Risk assessment and assumptions

Test plan

  • Code compiles (cargo check passes)
  • Manual testing of write_plan tool
  • Manual testing of planner sub-agent delegation

xlyk added 3 commits January 27, 2026 13:47
Convert rig Image types to OpenAI InputImageContent format, handling base64, URL, and raw byte sources with proper media type and detail level mapping.
Add a new `write_plan` tool for creating detailed task plans with title,
explanation, and actionable steps. This is semantically distinct from
`update_plan` which tracks progress on existing tasks.

Also add a new `planner` sub-agent specialized for breaking down complex
tasks into structured, actionable plans with dependencies and priorities.
The write_plan tool was defined in the tool definitions but not
registered in the ToolRegistry, which meant sub-agents couldn't
execute it. This fix:

- Creates a WritePlanTool struct implementing the Tool trait
- Adds it to qbit-planner crate alongside the existing PlanManager
- Registers it in qbit-tools ToolRegistry
- Adds test coverage for write_plan registration

Sub-agents (like the planner) now have access to write_plan through
the ToolRegistry.execute_tool() path.
@xlyk xlyk closed this Jan 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants