1.8 KiB
1.8 KiB
allowed-tools, description
| allowed-tools | description |
|---|---|
| mcp__taskmaster-ai__update, mcp__taskmaster-ai__update_task, mcp__taskmaster-ai__update_subtask, mcp__taskmaster-ai__get_tasks | Update tasks interactively with clarifying questions |
Update Tasks Interactively
Context
- User Request: $ARGUMENTS
- Current Tag: !
jq -r '.currentTag // "master"' .taskmaster/state.json 2>/dev/null || echo "master"
Goal
Update tasks based on implementation changes by asking clarifying questions to ensure accurate updates.
Process
-
Analyze Change: Think deeply about the implications of the change.
-
Ask Clarifying Questions:
- Ask 4-6 targeted questions about the change
- Provide lettered/numbered options for easy response
- Focus on understanding impact and scope
-
Update Tasks:
- Update affected tasks based on answers
- Show what was changed
Clarifying Questions Framework
Adapt questions based on the change described above. Consider these areas:
- Scope: "Which tasks are affected by this change?"
- Reason: "Why was this change made?"
- Impact: "How does this affect the implementation approach?"
- Dependencies: "Does this change affect task dependencies?"
- Testing: "How should test strategies be updated?"
- Documentation: "What additional context should be added?"
Final Instructions
- Think deeply about the change and its implications
- Ask clarifying questions with lettered/numbered options
- Update tasks based on the answers
- Confirm what was updated
Example Usage
/project:task:update-interactive switching to microservices architecture
This will:
- Ask about which components are affected
- Understand the migration approach
- Update relevant tasks with new architecture details