Overview
Tool Name
Purpose
The project_manager_tools suite organizes work into missions and todos. It supports creation, assignment, dependencies, bulk operations, work recording, and asset management so projects move from plan to done with clear ownership and traceability.Key Features & Functions
Plan Missions
Create and update missions with descriptions, status, and timelines.
Track Todos
Create, assign, and update todos with rich details and statuses.
Manage Dependencies
Add or remove todo relationships to enforce execution order.
Record Progress
Log work done with outcomes for audit-ready history.
Handle Assets
Attach and manage mission assets like files, links, and git paths.
Scale With Bulk Ops
Create or delete many todos at once with optional dependency wiring.
See Data Agent Involvement
List data agents assigned to missions and todos for load visibility.
Use a short, action-oriented mission name and a precise todo title. It keeps lists scannable and status meetings fast.
Input Parameters for Each Function
manage_todos
Parameters
| Name | Definition | Format |
|---|---|---|
| action | Operation to perform. One of CREATE, UPDATE, GET_TODO_DETAILS, CHANGE_STATUS, LIST. | String |
| for_bot_id | Act on behalf of another data agent. | String |
| todo_details | Structured details payload for create or update. | Object |
| project_id | Mission id that owns the todo. Required for CREATE. | String |
| todo_name | Todo title. Required for CREATE. | String |
| what_to_do | Detailed description of the work. Required for CREATE. | String |
| depends_on | One or many todo ids that must complete first. | String or List |
| assigned_to_bot_id | Data Agent id to assign the todo to. | String |
| new_status | Target status for CHANGE_STATUS. One of NEW, IN_PROGRESS, PAUSED, COMPLETED, CANCELLED. | String |
| todo_id | Target todo id for UPDATE and CHANGE_STATUS. | String |
manage_projects
Parameters
| Name | Definition | Format |
|---|---|---|
| action | Operation to perform. One of CREATE, UPDATE, CHANGE_STATUS, LIST. | String |
| for_bot_id | Act on behalf of another data agent. | String |
| project_details | Structured details payload for create or update. | Object |
| project_name | Mission name. Required for CREATE. | String |
| description | Mission description. Required for CREATE. | String |
| new_status | New status for UPDATE. | String |
| project_id | Mission id for CREATE response mapping and for UPDATE. | String |
Project and todo ids are generated by the platform. Store them in your automation so later updates and dependency wiring are reliable.
record_todo_work
Parameters
| Name | Definition | Format |
|---|---|---|
| todo_id | Todo id to record work against. | String |
| work_description | Narrative of what was done. | String |
| work_results | Outputs, findings, or links to artifacts. | String |
| for_bot_id | Act on behalf of another data agent. | String |
get_todo_history
Parameters
| Name | Definition | Format |
|---|---|---|
| todo_id | Todo id whose history to return. | String |
get_project_todos
Parameters
| Name | Definition | Format |
|---|---|---|
| project_id | Mission id to list todos for. | String |
| for_bot_id | Act on behalf of another data agent. | String |
get_todo_dependencies
Parameters
| Name | Definition | Format |
|---|---|---|
| todo_id | Todo id whose dependencies to retrieve. | String |
| for_bot_id | Act on behalf of another data agent. | String |
| include_reverse | Include todos that depend on this todo when true. | Boolean |
manage_todo_dependencies
Parameters
| Name | Definition | Format |
|---|---|---|
| action | One of ADD or REMOVE. | String |
| todo_id | The dependent todo id. | String |
| depends_on_todo_id | The prerequisite todo id that must complete first. | String |
| for_bot_id | Act on behalf of another data agent. | String |
delete_todos_bulk
Parameters
| Name | Definition | Format |
|---|---|---|
| todo_ids | Array of todo ids to delete. | List of String |
| for_bot_id | Act on behalf of another data agent. | String |
create_todos_bulk
Parameters
| Name | Definition | Format |
|---|---|---|
| project_id | Mission id for all created todos. | String |
| todos | Array of todo objects. Each supports todo_name, what_to_do, optional depends_on, assigned_to_bot_id, todo_type, fields. | List of Objects |
| for_bot_id | Act on behalf of another data agent. | String |
manage_project_assets
Parameters
| Name | Definition | Format |
|---|---|---|
| action | One of CREATE, UPDATE, DELETE, LIST, GET_DETAILS. | String |
| project_id | Mission id that owns the asset. | String |
| asset_id | Asset id for UPDATE, DELETE, GET_DETAILS. | String |
| asset_details | Structured details payload. | Object |
| description | Asset description for CREATE and UPDATE. | String |
| asset_type | Type such as GIT, FILE, LINK, G-SHEET. | String |
| git_path | Git path when asset type is GIT. | String |
| data | Arbitrary JSON metadata. | String |
get_project_bots
Parameters
| Name | Definition | Format |
|---|---|---|
| project_id | Mission id to summarize data agent use. | String |
get_todo_bots
Parameters
| Name | Definition | Format |
|---|---|---|
| todo_id | Todo id to list associated data agents for. | String |
Use Cases
- Managing complex data engineering projects with multiple interdependent tasks
- Coordinating team workflows with automated task assignment and progress tracking
- Building project documentation and asset libraries with organized file management
- Tracking mission progress with detailed work logs and completion metrics
- Managing dependencies between tasks to ensure proper execution sequencing
- Creating comprehensive project dashboards with data agent assignment and progress visibility
- Coordinating cross-functional projects with multiple stakeholders and deliverables
Workflow/How It Works
- Create a mission with name and purpose.
- Break down work into todos and assign to data agents or people.
- Wire dependencies so prerequisites complete first.
- Record work as progress is made, attaching outputs and links.
- Manage assets at the mission level for easy retrieval.
- Scale with bulk create or delete when scope shifts.
Avoid circular dependencies. If A depends on B and B depends on A, scheduling will stall. Use
get_todo_dependencies to verify the graph before large changes.Integration Relevance
- file_manager_tools for storing specs, outputs, and evidence.
- make_baby_bot to assign specialized agents to todos.
- data_connector_tools to link data work directly to tasks.
- git_action for versioned assets and code paths.
- delegate_work to orchestrate multi-agent workflows.
- slack_tools to notify owners on status changes.
Configuration Details
- Status values must match the allowed set for reliable dashboards.
- Use
for_bot_idwhen automations act on behalf of a controller agent. - Store returned ids from create calls for subsequent updates and dependency wiring.
- Choose asset types that reflect storage location and retrieval method.
Limitations or Notes
- Deletions are permanent. Export state before bulk removals.
- Very large dependency graphs can be hard to visualize. Document key chains in the mission description.
- Bulk operations may take time on large projects. Plan during low-traffic windows.
- Data Agent assignment depends on availability and permissions.
- Asset references require valid external integrations where applicable.
Output
- Task Operations Creation confirmations, detail payloads, and status updates.
- Mission Operations Creation confirmations, status changes, and listings.
- Work Recording Timestamped entries with descriptions and results.
- History Full audit trails of changes and actors.
- Dependencies Add or remove confirmations and resolved trees.
- Bulk Ops Summaries with success and failure counts.
- Assets Created or updated records, listings, and detail views.
- Data Agents
Assignment summaries and participation metrics. - Errors Clear messages for invalid ids, status mismatches, or permission failures.