Agiflow

Delete a task comment (only by original author)

delete_task_comment

Delete a work unit by ID or slug. WARNING: This action is permanent and will cascade delete all child work units and disassociate tasks.

delete_work_unit

<toolkit id="d15e96f0"> <instruction> Describe registered capabilities available in this connection. Provide at least one listed capability name; multiple names can be requested together. - For tools: Returns descriptions and input schemas for the selected registered tools. - For skills: Returns instruction text to guide your work, not an executed action. Use this tool to inspect inputs before executing an unfamiliar capability. This call does not execute tools, grant permissions, register connected-service actions, or guarantee that a subsequent action will be authorized. External catalog entries are not additional directly registered tools. How to invoke: - For MCP tools: Call the tool directly with the tool name and arguments based on the schema - For skills: Use this tool with the skill name to get expanded instructions </instruction> <available_capabilities> <group name="tools"> <item name="create_project"><description>Create a project from a template, or return a case-insensitive same-name match found among the first ten search results without applying the requested changes. templateId defaults to software. Template creation seeds statuses, starter tasks, missing organization agent members, and template color/icon defaults. Call list_templates to choose a different template and pass its ID with a user-approved project name.</description></item> <item name="list_projects"><description>List projects with minimal information by pagination & filtering. For detailed project information, use get_project_detail tool.</description></item> <item name="list_project_statuses"><description>List all available statuses for a project. Use this to discover valid status names before creating or updating tasks and work units.</description></item> <item name="get_project_detail"><description>Use this to retrieve a project by ID or Slug. This returns the full project details including name, description, settings, and metadata.</description></item> <item name="update_project"><description>Update a project by ID or slug. Replace supplied name, description, color, icon, organizationId, or archive flag; omitted fields remain unchanged. Null clears description, color, or icon, while null organizationId is ignored. Renaming regenerates the project slug. Archiving changes visibility without deleting project data. Previous field values are overwritten.</description></item> <item name="list_templates"><description>List built-in and organization-owned project templates available for creating projects. Next action: choose one template through the UI or ask the user which template to use, then call create_project with templates[].id as templateId.</description></item> <item name="manage_project_template"><description>Manage an organization-owned project template using one action: 'create' requires a full template payload; 'update' requires templateId and a full replacement payload; 'delete' requires templateId. Update replaces the stored definition rather than merging it, and omitted starterTasks or agents become empty lists. Delete removes the template from the active catalog: unused organization templates are hard-deleted, while templates referenced by projects are deactivated. Existing projects are not re-seeded. Built-in templates cannot be modified or deleted. Call list_templates afterwards to verify the change.</description></item> <item name="list_members"><description>List all agent members in the organization.</description></item> <item name="create_member"><description>Create a new AI agent member in the organization.</description></item> <item name="get_organization_summary"><description>Retrieve summary statistics for the organization including project counts, task counts by status, recent activity, and team member information. Use this for a high-level dashboard overview.</description></item> <item name="batch_create_work_units"><description>Create multiple work units at once (epic, feature, or initiative). Call list_project_statuses to discover valid status names.</description></item> <item name="list_work_units"><description>List work units with optional filtering and pagination. Call list_project_statuses to discover valid status names for filtering.</description></item> <item name="get_work_unit"><description>Retrieve a work unit by ID or slug. Returns the work unit details including title, description, type, status, priority, dates, and hierarchical relationships.</description></item> <item name="update_work_unit"><description>Update a work unit by ID or slug. Call list_project_statuses to discover valid status names. Modify title, description, type, status, priority, dates, owner, effort, or development/test information. Supplied fields replace existing values; omitted fields remain unchanged. Null clears nullable fields, and parentWorkUnitId can change hierarchy or become null for a root work unit. devInfo and testCases replace their stored values rather than merging. A completion status sets completedAt when omitted; a non-completion status can clear it. Repeated completion updates can refresh that timestamp. Completion-evidence checks still apply. Updates are recorded in activity logs.</description></item> <item name="delete_work_unit"><description>Delete a work unit by ID or slug. WARNING: This action is permanent and will cascade delete all child work units and disassociate tasks.</description></item> <item name="get_work_unit_progress"><description>Get progress information for a work unit by ID or slug. Returns overall progress percentage (0-100), completed and total task counts, and child work unit completion status.</description></item> <item name="create_task"><description>Create a task toward the project objective. An identical idempotencyKey retry returns the original task; without a key, a matching title in the searched project tasks may reuse an existing task. Optional mcpTools sets exact external tool permissions and may replace access on a reused task; [] revokes external access on keyless title reuse. Response hydration may contact connected services for tool catalogs and refresh credentials or initiate authorization; it does not execute those tools. If connected tools may help accomplish the task, follow find_connected_tools, select the smallest relevant set, then use update_task with practical usage instructions and the exact mcpTools selection.</description></item> <item name="batch_create_tasks"><description>Create multiple tasks at once inside a project. Call list_project_statuses first to discover valid status names. Available agent members for the 'assignee' field: No agent members available.</description></item> <item name="list_tasks"><description>List project tasks. Use view attention for the shared prioritized dashboard queue, including organization-wide attention when no project is bound. Status-name filters require a project. Call list_project_statuses to discover valid status names.</description></item> <item name="get_task"><description>Read task context, comments, current completion evidence, and permitted tool information to plan or resume work toward the task objective. Use view handoff for bounded resumable context or detail for full task fields and available tool schemas. Task fields and permissions are not changed. Artifact render URLs are prepared in hidden metadata. Response hydration may contact connected services for tool catalogs and refresh credentials or initiate authorization; it does not execute those tools.</description></item> <item name="complete_task_step"><description>Record completion of the current task workflow step with optional notes and evidence. Approval steps wait for a different owner or admin in the Agiflow browser app; this tool cannot approve them.</description></item> <item name="attach_task_artifact"><description>Attach task evidence by downloading a ChatGPT/OpenAI file, uploading it to project artifact storage, upserting its metadata, and linking it to the task. Reusing a filename can overwrite existing project-wide bytes and metadata, affecting other linked tasks; reattachment can replace clip metadata. Signed render URLs remain in hidden metadata.</description></item> <item name="app_prepare_task_artifact_upload"><description>Prepare a signed task artifact upload target for the Agiflow task widget.</description></item> <item name="app_attach_task_artifact"><description>Finalize a widget-uploaded task artifact, mark it uploaded, and link it to the task.</description></item> <item name="list_active_tasks_by_org"><description>List active tasks (in progress and review) across all projects in the organization. Excludes todo and completed tasks. Use this for a dashboard-style overview of work currently being worked on.</description></item> <item name="update_task"><description>Update a task using expectedRevision from the last read. Supplied fields and checklists can replace existing values; supported nullable fields can clear content. Work-unit association and status changes affect task lifecycle timestamps. Revision and completion-evidence guards apply. Omitted fields are preserved. mcpTools is an exact permission replacement: omit to preserve access, [] to revoke all external tools, or provide only the required selections. Response hydration may contact connected services for tool catalogs and refresh credentials or initiate authorization; it does not execute those tools. Returns saved values and a receipt. Never retry a revision conflict blindly.</description></item> <item name="delete_task"><description>Delete a task by ID or slug (e.g., "LXX-2"). This action is permanent and will remove all associated comments and activity logs.</description></item> <item name="reorder_tasks"><description>Reorder tasks inside a status. Call list_project_statuses to discover valid status names.</description></item> <item name="create_task_comment"><description>Create a new comment on a task</description></item> <item name="list_task_comments"><description>List comments for a specific task</description></item> <item name="update_task_comment"><description>Replace an existing task comment content with nonempty text, only when the caller is its original author and has access to the parent task. Replaces the previous content, updates the edit timestamp, and broadcasts the change; repeated edits can refresh the timestamp. Does not create a new comment or change the task.</description></item> <item name="delete_task_comment"><description>Delete a task comment (only by original author)</description></item> <item name="find_connected_tools"><description>Find connected tools relevant to the user-requested task objective so the smallest suitable set can be selected under the task’s Tools & access. Searches enabled external server catalogs and returns matching tool contracts with pagination or authorization guidance. Catalog retrieval may refresh credentials or initiate OAuth authorization setup. This call does not grant task permissions or execute the discovered actions.</description></item> <item name="task_exec"><description>Execute an action toward the selected Agiflow task’s objective using a connected tool allowed under that task’s Tools & access. Use this for work needed to accomplish the task, with arguments matching the selected tool’s input schema. Agiflow checks the task’s connected scope, enabled server, exact tool permission, and available server catalog. The action may modify or delete external data. Returns the action’s result without automatically marking the task complete. Follow authorization guidance when required, and do not automatically retry an action whose execution outcome is unknown.</description></item> <item name="task_exec_code"><description>Run sandboxed JavaScript/TypeScript that can call the task's allowed external MCP tools. `code` is the body of an async function: use `await` and `return` directly. In scope: `input`; `tools.<server>.<tool>(args)` (server by name or id; returns structuredContent, else parsed text; throws on tool errors); `console.*` (captured, 50 lines); `require(name)` for declared `dependencies` (exact npm versions, max 10). `env` holds an approved script's declared variables (secrets are opaque placeholders, usable only in allowed request headers); `fetch(url, {method, headers, body: string})` works only in approved scripts, only over HTTPS to hosts bound to their secrets, and never follows redirects. One-off code has `env` = {} and no network. No timers. Limits: 50 tool and fetch calls per run, 10 s per tool call (a timed-out call may still complete upstream), 55 s per run, 64 KiB input and return value. Alternatively pass `script` to run an approved project script (see list_task_scripts).</description></item> <item name="list_task_scripts"><description>List the project's code scripts with their latest approved version and whether each can run on this task (all required tools allowed and the approved environment ready).</description></item> <item name="propose_task_script"><description>Propose a reusable project script (same code rules as task_exec_code). It is compiled now and becomes runnable with task_exec_code({script}) only after an organization owner or admin approves it. requiredTools must already be allowed on the task. requiredEnv lists agent env variable names the script reads; the approver picks the agent profile that supplies them.</description></item> </group> <group name="skills"> <item name="getting-started"><description>Onboarding guide with workflow overview, decision framework, and tool reference. Use when user says: "help me get started", "what should I do first", "I'm new to this project", or "where do I begin". Does NOT create or modify anything — read-only orientation. Use project-plan to start creating tasks.</description></item> <item name="project-plan"><description>Break down requirements into tasks with decomposition. Handles both new projects and adding features to existing ones. Use when user says: "plan this feature", "break this down", "create tasks for", "start a new project", or "plan sprint". Creates tasks in Planning status with tags. Do NOT use for promoting tasks to Todo (use backlog-grooming) or executing tasks (use run-work/run-task).</description></item> <item name="refine-task"><description>Enrich task descriptions so AI agents can work autonomously without clarification. Use when user says: "refine this task", "add more detail", "make this clearer", or when tasks lack acceptance criteria, file paths, or scope boundaries. Do NOT use for creating new tasks (use project-plan) or executing tasks (use run-task).</description></item> <item name="backlog-grooming"><description>Prioritize Planning tasks, promote to Todo, and group into work units. The ONLY way tasks move from Planning to Todo. Use when user says: "groom the backlog", "prioritize tasks", "move tasks to todo", "create work units", or "organize the backlog". Do NOT use for creating tasks (use project-plan) or executing tasks (use run-work/run-task).</description></item> <item name="run-work"><description>Execute a complete work unit by implementing all its Todo tasks sequentially with testing between each. Use when user says: "run this work unit", "implement this feature", "execute the sprint", or "start working on [feature]". Only works with Todo tasks (not Planning). Do NOT use for single standalone tasks (use run-task) or planning (use project-plan).</description></item> <item name="run-task"><description>Execute a single task by implementing all its acceptance criteria with architect validation. Use when user says: "work on this task", "fix this bug", "implement [specific task]", or "run task [slug]". Only works with Todo tasks (not Planning). Do NOT use for multiple related tasks (use run-work) or planning (use project-plan).</description></item> <item name="review-work"><description>Verify completed work meets acceptance criteria with PASS/FAIL/PARTIAL verdicts and quality checks. Use when user says: "review this work", "check if it's done", "audit quality", "verify the feature", or before merging. Do NOT use for executing tasks (use run-work/run-task) or diagnosing stuck projects (use triage).</description></item> <item name="triage"><description>Diagnose stalled or blocked projects with severity classification. Also handles: cancel/archive obsolete tasks, re-prioritize Todo back to Planning, and fast-track incoming bugs. Use when user says: "why is this stuck", "cancel this task", "re-prioritize", "incoming bug", "clean up backlog", or "project health check". Do NOT use for daily status (use daily-standup) or executing work (use run-work).</description></item> <item name="daily-standup"><description>Quick read-only pulse: done/doing/blocked/next status with recommendations. Use when user says: "standup", "what's the status", "daily update", "morning check", or "what happened yesterday". Do NOT use for deep diagnosis (use triage) or executing work (use run-work/run-task).</description></item> </group> </available_capabilities> </toolkit>

describe_capabilities

Execute a named external MCP tool only when that exact server and tool are selected under Tools & access for the target task.

task_exec

Find external tools that match an explicit user-requested action before attaching the smallest suitable set to a task.

find_connected_tools

Use this to get contextual information about the current session including MCP scope, organization, project, work unit, and task details. Use this to understand your current context and available capabilities. Use this to answer user's questions about current Agiflow's access scope, which organization, project, work unit or task has been granted by user.

get_current_scope

Retrieve summary statistics for the organization including project counts, task counts by status, recent activity, and team member information. Use this for a high-level dashboard overview.

get_organization_summary

Use this to retrieve a project by ID or Slug. This returns the full project details including name, description, settings, and metadata.

get_project_detail

Retrieve the task details and its authoritative allowedMcpTools list, including input schemas for execution through task_exec.

get_task

Retrieve a work unit by ID or slug. Returns the work unit details including title, description, type, status, priority, dates, and hierarchical relationships.

get_work_unit

Get progress information for a work unit by ID or slug. Returns overall progress percentage (0-100), completed and total task counts, and child work unit completion status.

get_work_unit_progress

List active tasks (in progress and review) across all projects in the organization. Excludes todo and completed tasks. Use this for a dashboard-style overview of work currently being worked on.

list_active_tasks_by_org

List all agent members in the organization. Returns agent members with their details including: - Member ID, role, description, and prompt - Associated user information (name, email, image) - Creation timestamp Use this to discover available agents that can be assigned to tasks and work units.

list_members

List all available statuses for a project. Use this to discover valid status names before creating or updating tasks and work units.

list_project_statuses

List built-in and organization-owned project templates available for creating projects. Next action: choose one template through the UI or ask the user which template to use, then call create_project with templates[].id as templateId.

list_templates

List projects with minimal information by pagination & filtering. For detailed project information, use get_project_detail tool.

list_projects

List comments for a specific task

list_task_comments

List project tasks. Use view attention for the shared prioritized dashboard queue, including organization-wide attention when no project is bound. Status-name filters require a project. Call list_project_statuses to discover valid status names.

list_tasks

List work units with optional filtering and pagination. Call list_project_statuses to discover valid status names for filtering. Omit projectId in an organization-wide session to list unfinished work across projects. Explicit status, statusId, statusIds, or excludeStatus filters override this default. Supplying a project ID or slug (or using a project-bound session) preserves project listing defaults. Filter by: type, status, priority, ownerId, parentWorkUnitId, search Sort by: createdAt, updatedAt, title, priority, targetDate

list_work_units

Manage an organization-owned project template using one action: 'create' requires a full template payload; 'update' requires templateId and a full replacement payload; 'delete' requires templateId. Update replaces the stored definition rather than merging it, and omitted starterTasks or agents become empty lists. Delete removes the template from the active catalog: unused organization templates are hard-deleted, while templates referenced by projects are deactivated. Existing projects are not re-seeded. Built-in templates cannot be modified or deleted. Call list_templates afterwards to verify the change.

manage_project_template

Prepare a signed task artifact upload target for the Agiflow task widget.

app_prepare_task_artifact_upload

Reorder tasks inside a status. Call list_project_statuses to discover valid status names.

reorder_tasks

Update a project by ID or slug. Replace supplied name, description, color, icon, organizationId, or archive flag; omitted fields remain unchanged. Null clears description, color, or icon, while null organizationId is ignored. Renaming regenerates the project slug. Archiving changes visibility without deleting project data. Previous field values are overwritten.

update_project

Update a task. mcpTools is an exact replacement: omit it to keep access unchanged, pass [] to revoke all external tools, or pass only the smallest tool set needed. Add practical tool usage instructions to the task description.

update_task

Replace an existing task comment content with nonempty text, only when the caller is its original author and has access to the parent task. Replaces the previous content, updates the edit timestamp, and broadcasts the change; repeated edits can refresh the timestamp. Does not create a new comment or change the task.

update_task_comment

Update a work unit by ID or slug. Call list_project_statuses to discover valid status names. Modify title, description, type, status, priority, dates, owner, effort, or development/test information. Supplied fields replace existing values; omitted fields remain unchanged. Null clears nullable fields, and parentWorkUnitId can change hierarchy or become null for a root work unit. devInfo and testCases replace their stored values rather than merging. A completion status sets completedAt when omitted; a non-completion status can clear it. Repeated completion updates can refresh that timestamp. Completion-evidence checks still apply. Updates are recorded in activity logs.

update_work_unit