​
Overview

​
Tool Name

project_manager_tools

​
Purpose

The project_manager_tools group is designed to streamline project and task management workflows. It includes functionality for creating, tracking, and managing projects, associated todos, dependencies, and related assets, ensuring efficient execution of deliverables.

​
Key Features & Functions

Manage Todos

Creates, updates, or manages task-based todos and their progress.

Manage Projects

Manages high-level project details, including creation, updates, and deletion of projects.

Record Todo Work

Logs incremental progress or significant updates for a specific todo.

Get Project Todos

Retrieves all todos linked to a specific project.

Get Todo Dependencies

Retrieves dependencies for a specific todo or identifies tasks that depend on a given todo.

Manage Todo Dependencies

Adds or removes dependencies between todos to enforce order in task execution.

Manage Project Assets

Organizes and tracks assets associated with a project (e.g., files, scripts, or Git-managed resources).

​
Input Parameters for Each Function

​
1. manage_todos

Parameters
NameDefinitionFormat
actionSpecifies "CREATE", "UPDATE", "CHANGE_STATUS", or "LIST" (string, required).String
todo_detailsA JSON object containing fields such as:JSON/Object
– project_id (string)The project the todo is linked to (required for CREATE).String
– todo_name (string)Name of the todo (required for CREATE).String
– what_to_do (string)Description of the task (required for CREATE).String
– depends_on (string or list)Optional: other todos this task depends on.String/List
– new_status (string)New status for the todo (required for CHANGE_STATUS).String

​
2. manage_projects

Parameters
NameDefinitionFormat
actionSpecifies "CREATE", "UPDATE", or "DELETE" (string, required).String
project_detailsA JSON object with fields like:JSON/Object
– project_name (string)Name of the project (required for CREATE).String
– description (string)Summary of project goals (optional).String
– new_status (string)Updated status for the project (required for UPDATE).String
Genbot Tip Use descriptive and concise project_name values for easier tracking across multiple active projects.

​
3. record_todo_work

Parameters
NameDefinitionFormat
todo_idUnique identifier of the todo to log work against (required).String
work_descriptionDetailed update or summary of progress (required).String
work_results(Optional) Results or outcomes from the work process.String

​
4. get_project_todos

Parameters
NameDefinitionFormat
project_idUnique ID of the project to retrieve associated todos (required).String

​
5. get_todo_dependencies

Parameters
NameDefinitionFormat
todo_idUnique ID of the todo to retrieve dependencies for (required).String
include_reverse(Optional) Boolean indicating if tasks depending on this todo should be returned (default: false).Boolean

​
6. manage_todo_dependencies

Parameters
NameDefinitionFormat
actionSpecifies "ADD" or "REMOVE" (required).String
todo_idThe todo being linked (string, required).String
depends_on_todo_idThe todo that must be completed first (required for "ADD").String
IMPORTANT: Be cautious when adding dependencies—circular references can cause deadlocks or block workflow progress.

​
7. manage_project_assets

Parameters
NameDefinitionFormat
actionSpecifies "CREATE", "UPDATE", "CHANGE_STATUS", or "LIST" (required).String
project_idUnique project ID for asset association (required for CREATE).String
asset_idAsset ID for updates or status changes (required for UPDATE / CHANGE_STATUS).String
asset_detailsA JSON object with fields such as:JSON/Object
– description (string, optional)Describes asset purpose or context.String
– git_path (string, optional)Points to asset location in Git.String
NOTE: It’s recommended to keep asset_details concise but clear to ensure quick identification and traceability in future audits.

​
Use Cases

  1. Project Creation & Tracking
    • Use manage_projects to launch new projects and track overall status changes.
    • Example: “Data Pipeline Optimization” with timelines and multiple tasks.
  2. Task Dependencies
    • Add dependencies with manage_todo_dependencies to enforce correct execution order.
    • Example: “Load Dataset” must complete before “Run Analysis.”
  3. Detailed Task Logs
    • Use record_todo_work for granular updates or intermediate outcomes.
    • Example: Logging code review details or test results for a crucial script.
  4. Asset Tracking
    • Apply manage_project_assets to associate scripts, files, or Git resources with a project.
    • Example: Linking a Git-managed version of a dashboard to a project deliverable.

​
Workflow/How It Works

  1. Step 1: Create & Initiate Projects
    • Start by creating one or more high-level projects (manage_projects). Define goals, timelines, statuses.
  2. Step 2: Define Todos & Dependencies
    • Break projects into actionable tasks using manage_todos, and specify dependencies to control order.
  3. Step 3: Track Progress & Record Work
    • Update todos with record_todo_work for incremental reporting and change statuses upon completion.
  4. Step 4: Manage Project Assets
    • Use manage_project_assets to add or update relevant files, scripts, or documents for reference.
  5. Step 5: Retrieve & Adjust
    • Access project-wide todos (get_project_todos) or refine task dependencies (get_todo_dependencies).

​
Integration Relevance

  • File Management: Works with google_drive_tools or git_action to associate files within tasks or projects.
  • Task Scheduling: Combine with scheduler utilities for automated project task execution or reminders.
  • Data Development: Integrates with data_connector_tools for data-centric projects requiring database interactions.

​
Configuration Details

  • Use clear, descriptive naming for both projects and tasks to improve visibility, especially in large organizations.
  • Avoid cyclical dependencies by carefully planning or reviewing task relationships.
  • Keep asset descriptions aligned with repository structures for hassle-free retrieval.

​
Limitations or Notes

  1. Complex Projects
    • Very large or intricate projects may reduce manageability—consider dividing into multiple sub-projects or phases.
  2. Dependency Chains
    • Undefined or missing dependencies can lead to out-of-order execution in automated systems.
  3. Asset Storage
    • Ensure assets remain updated and accessible within configured repositories; stale file references complicate audits or retrieval.