complete_task
Mark a task as finished in Task Trellis MCP by providing task ID, summary, and file changes. Updates task status, records details, and triggers dependent tasks for accurate project progression.
Instructions
Completes a task in the task trellis system
Use this tool to mark a task as finished and record completion details. Critical for task lifecycle management and maintaining accurate project status.
Required completion data:
'taskId': Unique identifier of the task being completed
'summary': Concise description of what was accomplished
'filesChanged': Map of modified files with descriptions of changes made
Completion process:
Validates task is in a completable state ('in-progress')
Updates task status to 'done'
Records completion timestamp and summary
Associates file changes with the task for traceability
Updates parent-child relationships and dependency chains
Triggers any dependent tasks that were waiting for this completion
File change tracking:
Key: relative file path from project root
Value: description of changes made to that file
Example: {'src/api/users.ts': 'Added user authentication endpoints', 'tests/auth.test.ts': 'Added comprehensive auth test coverage'}
Best practices:
Provide clear, actionable summaries that explain the outcome
Document all meaningful file changes for future reference
Complete tasks only when all acceptance criteria are met
Verify dependent tasks can now proceed before completion
Include any important notes or lessons learned in the summary
Task completion automatically notifies dependent tasks and may trigger workflow progression for related work items.
Input Schema
Name | Required | Description | Default |
---|---|---|---|
filesChanged | Yes | Map of files changed with their descriptions | |
summary | Yes | Summary of the completed task | |
taskId | Yes | ID of the task to complete |