telos-framework 0.1.4 → 0.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/agents/behavioral-transformation-agent.md +144 -0
- package/.claude/agents/command-system-agent.md +335 -0
- package/.claude/agents/completion-gate.md +71 -0
- package/.claude/agents/component-implementation-agent.md +174 -0
- package/.claude/agents/devops-agent.md +128 -0
- package/.claude/agents/dynamic-agent-creator.md +103 -0
- package/.claude/agents/enhanced-project-manager-agent.md +145 -0
- package/.claude/agents/enhanced-quality-gate.md +54 -0
- package/.claude/agents/feature-implementation-agent.md +148 -0
- package/.claude/agents/functional-testing-agent.md +51 -0
- package/.claude/agents/hook-integration-agent.md +204 -0
- package/.claude/agents/infrastructure-implementation-agent.md +175 -0
- package/.claude/agents/lib/research-analyzer.js +470 -0
- package/.claude/agents/metrics-collection-agent.md +374 -0
- package/.claude/agents/npx-package-agent.md +246 -0
- package/.claude/agents/polish-implementation-agent.md +151 -0
- package/.claude/agents/prd-agent.md +76 -0
- package/.claude/agents/prd-mvp.md +101 -0
- package/.claude/agents/prd-research-agent.md +482 -0
- package/.claude/agents/quality-agent.md +128 -0
- package/.claude/agents/readiness-gate.md +104 -0
- package/.claude/agents/research-agent.md +173 -0
- package/.claude/agents/routing-agent.md +108 -0
- package/.claude/agents/task-checker.md +163 -0
- package/.claude/agents/task-executor.md +107 -0
- package/.claude/agents/task-orchestrator.md +343 -0
- package/.claude/agents/tdd-validation-agent.md +187 -0
- package/.claude/agents/testing-implementation-agent.md +151 -0
- package/.claude/agents/van-maintenance-agent.md +64 -0
- package/.claude/agents/workflow-agent.md +87 -0
- package/.claude/commands/autocompact.md +41 -0
- package/.claude/commands/continue-handoff.md +98 -0
- package/.claude/commands/mock.md +45 -0
- package/.claude/commands/reset-handoff.md +59 -0
- package/.claude/commands/telos/init.md +326 -0
- package/.claude/commands/telos/quick.md +90 -0
- package/.claude/commands/telos/reset.md +100 -0
- package/.claude/commands/telos/status.md +170 -0
- package/.claude/commands/telos/validate.md +143 -0
- package/.claude/commands/tm/add-dependency/add-dependency.md +55 -0
- package/.claude/commands/tm/add-subtask/add-subtask.md +76 -0
- package/.claude/commands/tm/add-subtask/convert-task-to-subtask.md +71 -0
- package/.claude/commands/tm/add-task/add-task.md +78 -0
- package/.claude/commands/tm/analyze-complexity/analyze-complexity.md +121 -0
- package/.claude/commands/tm/clear-subtasks/clear-all-subtasks.md +93 -0
- package/.claude/commands/tm/clear-subtasks/clear-subtasks.md +86 -0
- package/.claude/commands/tm/complexity-report/complexity-report.md +117 -0
- package/.claude/commands/tm/expand/expand-all-tasks.md +51 -0
- package/.claude/commands/tm/expand/expand-task.md +49 -0
- package/.claude/commands/tm/fix-dependencies/fix-dependencies.md +81 -0
- package/.claude/commands/tm/generate/generate-tasks.md +121 -0
- package/.claude/commands/tm/help.md +81 -0
- package/.claude/commands/tm/init/init-project-quick.md +46 -0
- package/.claude/commands/tm/init/init-project.md +50 -0
- package/.claude/commands/tm/learn.md +103 -0
- package/.claude/commands/tm/list/list-tasks-by-status.md +39 -0
- package/.claude/commands/tm/list/list-tasks-with-subtasks.md +29 -0
- package/.claude/commands/tm/list/list-tasks.md +43 -0
- package/.claude/commands/tm/models/setup-models.md +51 -0
- package/.claude/commands/tm/models/view-models.md +51 -0
- package/.claude/commands/tm/next/next-task.md +66 -0
- package/.claude/commands/tm/parse-prd/parse-prd-with-research.md +48 -0
- package/.claude/commands/tm/parse-prd/parse-prd.md +49 -0
- package/.claude/commands/tm/remove-dependency/remove-dependency.md +62 -0
- package/.claude/commands/tm/remove-subtask/remove-subtask.md +84 -0
- package/.claude/commands/tm/remove-task/remove-task.md +107 -0
- package/.claude/commands/tm/set-status/to-cancelled.md +55 -0
- package/.claude/commands/tm/set-status/to-deferred.md +47 -0
- package/.claude/commands/tm/set-status/to-done.md +44 -0
- package/.claude/commands/tm/set-status/to-in-progress.md +36 -0
- package/.claude/commands/tm/set-status/to-pending.md +32 -0
- package/.claude/commands/tm/set-status/to-review.md +40 -0
- package/.claude/commands/tm/setup/install-taskmaster.md +117 -0
- package/.claude/commands/tm/setup/quick-install-taskmaster.md +22 -0
- package/.claude/commands/tm/show/show-task.md +82 -0
- package/.claude/commands/tm/status/project-status.md +64 -0
- package/.claude/commands/tm/sync-readme/sync-readme.md +117 -0
- package/.claude/commands/tm/tm-main.md +146 -0
- package/.claude/commands/tm/update/update-single-task.md +119 -0
- package/.claude/commands/tm/update/update-task.md +72 -0
- package/.claude/commands/tm/update/update-tasks-from-id.md +108 -0
- package/.claude/commands/tm/utils/analyze-project.md +97 -0
- package/.claude/commands/tm/validate-dependencies/validate-dependencies.md +71 -0
- package/.claude/commands/tm/workflows/auto-implement-tasks.md +97 -0
- package/.claude/commands/tm/workflows/command-pipeline.md +77 -0
- package/.claude/commands/tm/workflows/smart-workflow.md +55 -0
- package/.claude/commands/van.md +150 -0
- package/.claude/docs/README.md +214 -0
- package/.claude/docs/TROUBLESHOOTING.md +126 -0
- package/.claude/hooks/block-destructive-commands.sh +243 -0
- package/.claude/hooks/collective-metrics.sh +291 -0
- package/.claude/hooks/directive-enforcer.sh +117 -0
- package/.claude/hooks/load-behavioral-system.sh +49 -0
- package/.claude/hooks/routing-executor.sh +4 -0
- package/.claude/hooks/test-driven-handoff.sh +653 -0
- package/.claude/settings.json +125 -0
- package/README.md +39 -15
- package/lib/commands/init-state.js +102 -0
- package/lib/commands/init.js +58 -95
- package/lib/installers/memory-files.js +77 -0
- package/lib/installers/slash-commands.js +77 -0
- package/package.json +7 -2
- package/templates/AGENTS.md +79 -0
- package/templates/CLAUDE.md +54 -0
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
Remove a subtask from its parent task.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS
|
|
4
|
+
|
|
5
|
+
Parse subtask ID to remove, with option to convert to standalone task.
|
|
6
|
+
|
|
7
|
+
## Removing Subtasks
|
|
8
|
+
|
|
9
|
+
Remove a subtask and optionally convert it back to a standalone task.
|
|
10
|
+
|
|
11
|
+
## Argument Parsing
|
|
12
|
+
|
|
13
|
+
- "remove subtask 5.1"
|
|
14
|
+
- "delete 5.1"
|
|
15
|
+
- "convert 5.1 to task" → remove and convert
|
|
16
|
+
- "5.1 standalone" → convert to standalone
|
|
17
|
+
|
|
18
|
+
## Execution Options
|
|
19
|
+
|
|
20
|
+
### 1. Delete Subtask
|
|
21
|
+
```bash
|
|
22
|
+
task-master remove-subtask --id=<parentId.subtaskId>
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
### 2. Convert to Standalone
|
|
26
|
+
```bash
|
|
27
|
+
task-master remove-subtask --id=<parentId.subtaskId> --convert
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
## Pre-Removal Checks
|
|
31
|
+
|
|
32
|
+
1. **Validate Subtask**
|
|
33
|
+
- Verify subtask exists
|
|
34
|
+
- Check completion status
|
|
35
|
+
- Review dependencies
|
|
36
|
+
|
|
37
|
+
2. **Impact Analysis**
|
|
38
|
+
- Other subtasks that depend on it
|
|
39
|
+
- Parent task implications
|
|
40
|
+
- Data that will be lost
|
|
41
|
+
|
|
42
|
+
## Removal Process
|
|
43
|
+
|
|
44
|
+
### For Deletion:
|
|
45
|
+
1. Confirm if subtask has work done
|
|
46
|
+
2. Update parent task estimates
|
|
47
|
+
3. Remove subtask and its data
|
|
48
|
+
4. Clean up dependencies
|
|
49
|
+
|
|
50
|
+
### For Conversion:
|
|
51
|
+
1. Assign new standalone task ID
|
|
52
|
+
2. Preserve all task data
|
|
53
|
+
3. Update dependency references
|
|
54
|
+
4. Maintain task history
|
|
55
|
+
|
|
56
|
+
## Smart Features
|
|
57
|
+
|
|
58
|
+
- Warn if subtask is in-progress
|
|
59
|
+
- Show impact on parent task
|
|
60
|
+
- Preserve important data
|
|
61
|
+
- Update related estimates
|
|
62
|
+
|
|
63
|
+
## Example Flows
|
|
64
|
+
|
|
65
|
+
```
|
|
66
|
+
/project:tm/remove-subtask 5.1
|
|
67
|
+
→ Warning: Subtask #5.1 is in-progress
|
|
68
|
+
→ This will delete all subtask data
|
|
69
|
+
→ Parent task #5 will be updated
|
|
70
|
+
Confirm deletion? (y/n)
|
|
71
|
+
|
|
72
|
+
/project:tm/remove-subtask 5.1 convert
|
|
73
|
+
→ Converting subtask #5.1 to standalone task #89
|
|
74
|
+
→ Preserved: All task data and history
|
|
75
|
+
→ Updated: 2 dependency references
|
|
76
|
+
→ New task #89 is now independent
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
## Post-Removal
|
|
80
|
+
|
|
81
|
+
- Update parent task status
|
|
82
|
+
- Recalculate estimates
|
|
83
|
+
- Show updated hierarchy
|
|
84
|
+
- Suggest next actions
|
|
@@ -0,0 +1,107 @@
|
|
|
1
|
+
Remove a task permanently from the project.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS (task ID)
|
|
4
|
+
|
|
5
|
+
Delete a task and handle all its relationships properly.
|
|
6
|
+
|
|
7
|
+
## Task Removal
|
|
8
|
+
|
|
9
|
+
Permanently removes a task while maintaining project integrity.
|
|
10
|
+
|
|
11
|
+
## Argument Parsing
|
|
12
|
+
|
|
13
|
+
- "remove task 5"
|
|
14
|
+
- "delete 5"
|
|
15
|
+
- "5" → remove task 5
|
|
16
|
+
- Can include "-y" for auto-confirm
|
|
17
|
+
|
|
18
|
+
## Execution
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
task-master remove-task --id=<id> [-y]
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
## Pre-Removal Analysis
|
|
25
|
+
|
|
26
|
+
1. **Task Details**
|
|
27
|
+
- Current status
|
|
28
|
+
- Work completed
|
|
29
|
+
- Time invested
|
|
30
|
+
- Associated data
|
|
31
|
+
|
|
32
|
+
2. **Relationship Check**
|
|
33
|
+
- Tasks that depend on this
|
|
34
|
+
- Dependencies this task has
|
|
35
|
+
- Subtasks that will be removed
|
|
36
|
+
- Blocking implications
|
|
37
|
+
|
|
38
|
+
3. **Impact Assessment**
|
|
39
|
+
```
|
|
40
|
+
Task Removal Impact
|
|
41
|
+
━━━━━━━━━━━━━━━━━━
|
|
42
|
+
Task: #5 "Implement authentication" (in-progress)
|
|
43
|
+
Status: 60% complete (~8 hours work)
|
|
44
|
+
|
|
45
|
+
Will affect:
|
|
46
|
+
- 3 tasks depend on this (will be blocked)
|
|
47
|
+
- Has 4 subtasks (will be deleted)
|
|
48
|
+
- Part of critical path
|
|
49
|
+
|
|
50
|
+
⚠️ This action cannot be undone
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
## Smart Warnings
|
|
54
|
+
|
|
55
|
+
- Warn if task is in-progress
|
|
56
|
+
- Show dependent tasks that will be blocked
|
|
57
|
+
- Highlight if part of critical path
|
|
58
|
+
- Note any completed work being lost
|
|
59
|
+
|
|
60
|
+
## Removal Process
|
|
61
|
+
|
|
62
|
+
1. Show comprehensive impact
|
|
63
|
+
2. Require confirmation (unless -y)
|
|
64
|
+
3. Update dependent task references
|
|
65
|
+
4. Remove task and subtasks
|
|
66
|
+
5. Clean up orphaned dependencies
|
|
67
|
+
6. Log removal with timestamp
|
|
68
|
+
|
|
69
|
+
## Alternative Actions
|
|
70
|
+
|
|
71
|
+
Suggest before deletion:
|
|
72
|
+
- Mark as cancelled instead
|
|
73
|
+
- Convert to documentation
|
|
74
|
+
- Archive task data
|
|
75
|
+
- Transfer work to another task
|
|
76
|
+
|
|
77
|
+
## Post-Removal
|
|
78
|
+
|
|
79
|
+
- List affected tasks
|
|
80
|
+
- Show broken dependencies
|
|
81
|
+
- Update project statistics
|
|
82
|
+
- Suggest dependency fixes
|
|
83
|
+
- Recalculate timeline
|
|
84
|
+
|
|
85
|
+
## Example Flows
|
|
86
|
+
|
|
87
|
+
```
|
|
88
|
+
/project:tm/remove-task 5
|
|
89
|
+
→ Task #5 is in-progress with 8 hours logged
|
|
90
|
+
→ 3 other tasks depend on this
|
|
91
|
+
→ Suggestion: Mark as cancelled instead?
|
|
92
|
+
Remove anyway? (y/n)
|
|
93
|
+
|
|
94
|
+
/project:tm/remove-task 5 -y
|
|
95
|
+
→ Removed: Task #5 and 4 subtasks
|
|
96
|
+
→ Updated: 3 task dependencies
|
|
97
|
+
→ Warning: Tasks #7, #8, #9 now have missing dependency
|
|
98
|
+
→ Run /project:tm/fix-dependencies to resolve
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
## Safety Features
|
|
102
|
+
|
|
103
|
+
- Confirmation required
|
|
104
|
+
- Impact preview
|
|
105
|
+
- Removal logging
|
|
106
|
+
- Suggest alternatives
|
|
107
|
+
- No cascade delete of dependents
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
Cancel a task permanently.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS (task ID)
|
|
4
|
+
|
|
5
|
+
## Cancelling a Task
|
|
6
|
+
|
|
7
|
+
This status indicates a task is no longer needed and won't be completed.
|
|
8
|
+
|
|
9
|
+
## Valid Reasons for Cancellation
|
|
10
|
+
|
|
11
|
+
- Requirements changed
|
|
12
|
+
- Feature deprecated
|
|
13
|
+
- Duplicate of another task
|
|
14
|
+
- Strategic pivot
|
|
15
|
+
- Technical approach invalidated
|
|
16
|
+
|
|
17
|
+
## Pre-Cancellation Checks
|
|
18
|
+
|
|
19
|
+
1. Confirm no critical dependencies
|
|
20
|
+
2. Check for partial implementation
|
|
21
|
+
3. Verify cancellation rationale
|
|
22
|
+
4. Document lessons learned
|
|
23
|
+
|
|
24
|
+
## Execution
|
|
25
|
+
|
|
26
|
+
```bash
|
|
27
|
+
task-master set-status --id=$ARGUMENTS --status=cancelled
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
## Cancellation Impact
|
|
31
|
+
|
|
32
|
+
When cancelling:
|
|
33
|
+
1. **Dependency Updates**
|
|
34
|
+
- Notify dependent tasks
|
|
35
|
+
- Update project scope
|
|
36
|
+
- Recalculate timelines
|
|
37
|
+
|
|
38
|
+
2. **Clean-up Actions**
|
|
39
|
+
- Remove related branches
|
|
40
|
+
- Archive any work done
|
|
41
|
+
- Update documentation
|
|
42
|
+
- Close related issues
|
|
43
|
+
|
|
44
|
+
3. **Learning Capture**
|
|
45
|
+
- Document why cancelled
|
|
46
|
+
- Note what was learned
|
|
47
|
+
- Update estimation models
|
|
48
|
+
- Prevent future duplicates
|
|
49
|
+
|
|
50
|
+
## Historical Preservation
|
|
51
|
+
|
|
52
|
+
- Keep for reference
|
|
53
|
+
- Tag with cancellation reason
|
|
54
|
+
- Link to replacement if any
|
|
55
|
+
- Maintain audit trail
|
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
Defer a task for later consideration.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS (task ID)
|
|
4
|
+
|
|
5
|
+
## Deferring a Task
|
|
6
|
+
|
|
7
|
+
This status indicates a task is valid but not currently actionable or prioritized.
|
|
8
|
+
|
|
9
|
+
## Valid Reasons for Deferral
|
|
10
|
+
|
|
11
|
+
- Waiting for external dependencies
|
|
12
|
+
- Reprioritized for future sprint
|
|
13
|
+
- Blocked by technical limitations
|
|
14
|
+
- Resource constraints
|
|
15
|
+
- Strategic timing considerations
|
|
16
|
+
|
|
17
|
+
## Execution
|
|
18
|
+
|
|
19
|
+
```bash
|
|
20
|
+
task-master set-status --id=$ARGUMENTS --status=deferred
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Deferral Management
|
|
24
|
+
|
|
25
|
+
When deferring:
|
|
26
|
+
1. **Document Reason**
|
|
27
|
+
- Capture why it's being deferred
|
|
28
|
+
- Set reactivation criteria
|
|
29
|
+
- Note any partial work completed
|
|
30
|
+
|
|
31
|
+
2. **Impact Analysis**
|
|
32
|
+
- Check dependent tasks
|
|
33
|
+
- Update project timeline
|
|
34
|
+
- Notify affected stakeholders
|
|
35
|
+
|
|
36
|
+
3. **Future Planning**
|
|
37
|
+
- Set review reminders
|
|
38
|
+
- Tag for specific milestone
|
|
39
|
+
- Preserve context for reactivation
|
|
40
|
+
- Link to blocking issues
|
|
41
|
+
|
|
42
|
+
## Smart Tracking
|
|
43
|
+
|
|
44
|
+
- Monitor deferral duration
|
|
45
|
+
- Alert when criteria met
|
|
46
|
+
- Prevent scope creep
|
|
47
|
+
- Regular review cycles
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
Mark a task as completed.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS (task ID)
|
|
4
|
+
|
|
5
|
+
## Completing a Task
|
|
6
|
+
|
|
7
|
+
This command validates task completion and updates project state intelligently.
|
|
8
|
+
|
|
9
|
+
## Pre-Completion Checks
|
|
10
|
+
|
|
11
|
+
1. Verify test strategy was followed
|
|
12
|
+
2. Check if all subtasks are complete
|
|
13
|
+
3. Validate acceptance criteria met
|
|
14
|
+
4. Ensure code is committed
|
|
15
|
+
|
|
16
|
+
## Execution
|
|
17
|
+
|
|
18
|
+
```bash
|
|
19
|
+
task-master set-status --id=$ARGUMENTS --status=done
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
## Post-Completion Actions
|
|
23
|
+
|
|
24
|
+
1. **Update Dependencies**
|
|
25
|
+
- Identify newly unblocked tasks
|
|
26
|
+
- Update sprint progress
|
|
27
|
+
- Recalculate project timeline
|
|
28
|
+
|
|
29
|
+
2. **Documentation**
|
|
30
|
+
- Generate completion summary
|
|
31
|
+
- Update CLAUDE.md with learnings
|
|
32
|
+
- Log implementation approach
|
|
33
|
+
|
|
34
|
+
3. **Next Steps**
|
|
35
|
+
- Show newly available tasks
|
|
36
|
+
- Suggest logical next task
|
|
37
|
+
- Update velocity metrics
|
|
38
|
+
|
|
39
|
+
## Celebration & Learning
|
|
40
|
+
|
|
41
|
+
- Show impact of completion
|
|
42
|
+
- Display unblocked work
|
|
43
|
+
- Recognize achievement
|
|
44
|
+
- Capture lessons learned
|
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
Start working on a task by setting its status to in-progress.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS (task ID)
|
|
4
|
+
|
|
5
|
+
## Starting Work on Task
|
|
6
|
+
|
|
7
|
+
This command does more than just change status - it prepares your environment for productive work.
|
|
8
|
+
|
|
9
|
+
## Pre-Start Checks
|
|
10
|
+
|
|
11
|
+
1. Verify dependencies are met
|
|
12
|
+
2. Check if another task is already in-progress
|
|
13
|
+
3. Ensure task details are complete
|
|
14
|
+
4. Validate test strategy exists
|
|
15
|
+
|
|
16
|
+
## Execution
|
|
17
|
+
|
|
18
|
+
```bash
|
|
19
|
+
task-master set-status --id=$ARGUMENTS --status=in-progress
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
## Environment Setup
|
|
23
|
+
|
|
24
|
+
After setting to in-progress:
|
|
25
|
+
1. Create/checkout appropriate git branch
|
|
26
|
+
2. Open relevant documentation
|
|
27
|
+
3. Set up test watchers if applicable
|
|
28
|
+
4. Display task details and acceptance criteria
|
|
29
|
+
5. Show similar completed tasks for reference
|
|
30
|
+
|
|
31
|
+
## Smart Suggestions
|
|
32
|
+
|
|
33
|
+
- Estimated completion time based on complexity
|
|
34
|
+
- Related files from similar tasks
|
|
35
|
+
- Potential blockers to watch for
|
|
36
|
+
- Recommended first steps
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
Set a task's status to pending.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS (task ID)
|
|
4
|
+
|
|
5
|
+
## Setting Task to Pending
|
|
6
|
+
|
|
7
|
+
This moves a task back to the pending state, useful for:
|
|
8
|
+
- Resetting erroneously started tasks
|
|
9
|
+
- Deferring work that was prematurely begun
|
|
10
|
+
- Reorganizing sprint priorities
|
|
11
|
+
|
|
12
|
+
## Execution
|
|
13
|
+
|
|
14
|
+
```bash
|
|
15
|
+
task-master set-status --id=$ARGUMENTS --status=pending
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
## Validation
|
|
19
|
+
|
|
20
|
+
Before setting to pending:
|
|
21
|
+
- Warn if task is currently in-progress
|
|
22
|
+
- Check if this will block other tasks
|
|
23
|
+
- Suggest documenting why it's being reset
|
|
24
|
+
- Preserve any work already done
|
|
25
|
+
|
|
26
|
+
## Smart Actions
|
|
27
|
+
|
|
28
|
+
After setting to pending:
|
|
29
|
+
- Update sprint planning if needed
|
|
30
|
+
- Notify about freed resources
|
|
31
|
+
- Suggest priority reassessment
|
|
32
|
+
- Log the status change with context
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
Set a task's status to review.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS (task ID)
|
|
4
|
+
|
|
5
|
+
## Marking Task for Review
|
|
6
|
+
|
|
7
|
+
This status indicates work is complete but needs verification before final approval.
|
|
8
|
+
|
|
9
|
+
## When to Use Review Status
|
|
10
|
+
|
|
11
|
+
- Code complete but needs peer review
|
|
12
|
+
- Implementation done but needs testing
|
|
13
|
+
- Documentation written but needs proofreading
|
|
14
|
+
- Design complete but needs stakeholder approval
|
|
15
|
+
|
|
16
|
+
## Execution
|
|
17
|
+
|
|
18
|
+
```bash
|
|
19
|
+
task-master set-status --id=$ARGUMENTS --status=review
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
## Review Preparation
|
|
23
|
+
|
|
24
|
+
When setting to review:
|
|
25
|
+
1. **Generate Review Checklist**
|
|
26
|
+
- Link to PR/MR if applicable
|
|
27
|
+
- Highlight key changes
|
|
28
|
+
- Note areas needing attention
|
|
29
|
+
- Include test results
|
|
30
|
+
|
|
31
|
+
2. **Documentation**
|
|
32
|
+
- Update task with review notes
|
|
33
|
+
- Link relevant artifacts
|
|
34
|
+
- Specify reviewers if known
|
|
35
|
+
|
|
36
|
+
3. **Smart Actions**
|
|
37
|
+
- Create review reminders
|
|
38
|
+
- Track review duration
|
|
39
|
+
- Suggest reviewers based on expertise
|
|
40
|
+
- Prepare rollback plan if needed
|
|
@@ -0,0 +1,117 @@
|
|
|
1
|
+
Check if Task Master is installed and install it if needed.
|
|
2
|
+
|
|
3
|
+
This command helps you get Task Master set up globally on your system.
|
|
4
|
+
|
|
5
|
+
## Detection and Installation Process
|
|
6
|
+
|
|
7
|
+
1. **Check Current Installation**
|
|
8
|
+
```bash
|
|
9
|
+
# Check if task-master command exists
|
|
10
|
+
which task-master || echo "Task Master not found"
|
|
11
|
+
|
|
12
|
+
# Check npm global packages
|
|
13
|
+
npm list -g task-master-ai
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
2. **System Requirements Check**
|
|
17
|
+
```bash
|
|
18
|
+
# Verify Node.js is installed
|
|
19
|
+
node --version
|
|
20
|
+
|
|
21
|
+
# Verify npm is installed
|
|
22
|
+
npm --version
|
|
23
|
+
|
|
24
|
+
# Check Node version (need 16+)
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
3. **Install Task Master Globally**
|
|
28
|
+
If not installed, run:
|
|
29
|
+
```bash
|
|
30
|
+
npm install -g task-master-ai
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
4. **Verify Installation**
|
|
34
|
+
```bash
|
|
35
|
+
# Check version
|
|
36
|
+
task-master --version
|
|
37
|
+
|
|
38
|
+
# Verify command is available
|
|
39
|
+
which task-master
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
5. **Initial Setup**
|
|
43
|
+
```bash
|
|
44
|
+
# Initialize in current directory
|
|
45
|
+
task-master init
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
6. **Configure AI Provider**
|
|
49
|
+
Ensure you have at least one AI provider API key set:
|
|
50
|
+
```bash
|
|
51
|
+
# Check current configuration
|
|
52
|
+
task-master models --status
|
|
53
|
+
|
|
54
|
+
# If no API keys found, guide setup
|
|
55
|
+
echo "You'll need at least one API key:"
|
|
56
|
+
echo "- ANTHROPIC_API_KEY for Claude"
|
|
57
|
+
echo "- OPENAI_API_KEY for GPT models"
|
|
58
|
+
echo "- PERPLEXITY_API_KEY for research"
|
|
59
|
+
echo ""
|
|
60
|
+
echo "Set them in your shell profile or .env file"
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
7. **Quick Test**
|
|
64
|
+
```bash
|
|
65
|
+
# Create a test PRD
|
|
66
|
+
echo "Build a simple hello world API" > test-prd.txt
|
|
67
|
+
|
|
68
|
+
# Try parsing it
|
|
69
|
+
task-master parse-prd test-prd.txt -n 3
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
## Troubleshooting
|
|
73
|
+
|
|
74
|
+
If installation fails:
|
|
75
|
+
|
|
76
|
+
**Permission Errors:**
|
|
77
|
+
```bash
|
|
78
|
+
# Try with sudo (macOS/Linux)
|
|
79
|
+
sudo npm install -g task-master-ai
|
|
80
|
+
|
|
81
|
+
# Or fix npm permissions
|
|
82
|
+
npm config set prefix ~/.npm-global
|
|
83
|
+
export PATH=~/.npm-global/bin:$PATH
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
**Network Issues:**
|
|
87
|
+
```bash
|
|
88
|
+
# Use different registry
|
|
89
|
+
npm install -g task-master-ai --registry https://registry.npmjs.org/
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
**Node Version Issues:**
|
|
93
|
+
```bash
|
|
94
|
+
# Install Node 18+ via nvm
|
|
95
|
+
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
|
|
96
|
+
nvm install 18
|
|
97
|
+
nvm use 18
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
## Success Confirmation
|
|
101
|
+
|
|
102
|
+
Once installed, you should see:
|
|
103
|
+
```
|
|
104
|
+
✅ Task Master v0.16.2 (or higher) installed
|
|
105
|
+
✅ Command 'task-master' available globally
|
|
106
|
+
✅ AI provider configured
|
|
107
|
+
✅ Ready to use slash commands!
|
|
108
|
+
|
|
109
|
+
Try: /project:task-master:init your-prd.md
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
## Next Steps
|
|
113
|
+
|
|
114
|
+
After installation:
|
|
115
|
+
1. Run `/project:utils:check-health` to verify setup
|
|
116
|
+
2. Configure AI providers with `/project:task-master:models`
|
|
117
|
+
3. Start using Task Master commands!
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
Quick install Task Master globally if not already installed.
|
|
2
|
+
|
|
3
|
+
Execute this streamlined installation:
|
|
4
|
+
|
|
5
|
+
```bash
|
|
6
|
+
# Check and install in one command
|
|
7
|
+
task-master --version 2>/dev/null || npm install -g task-master-ai
|
|
8
|
+
|
|
9
|
+
# Verify installation
|
|
10
|
+
task-master --version
|
|
11
|
+
|
|
12
|
+
# Quick setup check
|
|
13
|
+
task-master models --status || echo "Note: You'll need to set up an AI provider API key"
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
If you see "command not found" after installation, you may need to:
|
|
17
|
+
1. Restart your terminal
|
|
18
|
+
2. Or add npm global bin to PATH: `export PATH=$(npm bin -g):$PATH`
|
|
19
|
+
|
|
20
|
+
Once installed, you can use all the Task Master commands!
|
|
21
|
+
|
|
22
|
+
Quick test: Run `/project:help` to see all available commands.
|
|
@@ -0,0 +1,82 @@
|
|
|
1
|
+
Show detailed task information with rich context and insights.
|
|
2
|
+
|
|
3
|
+
Arguments: $ARGUMENTS
|
|
4
|
+
|
|
5
|
+
## Enhanced Task Display
|
|
6
|
+
|
|
7
|
+
Parse arguments to determine what to show and how.
|
|
8
|
+
|
|
9
|
+
### 1. **Smart Task Selection**
|
|
10
|
+
|
|
11
|
+
Based on $ARGUMENTS:
|
|
12
|
+
- Number → Show specific task with full context
|
|
13
|
+
- "current" → Show active in-progress task(s)
|
|
14
|
+
- "next" → Show recommended next task
|
|
15
|
+
- "blocked" → Show all blocked tasks with reasons
|
|
16
|
+
- "critical" → Show critical path tasks
|
|
17
|
+
- Multiple IDs → Comparative view
|
|
18
|
+
|
|
19
|
+
### 2. **Contextual Information**
|
|
20
|
+
|
|
21
|
+
For each task, intelligently include:
|
|
22
|
+
|
|
23
|
+
**Core Details**
|
|
24
|
+
- Full task information (id, title, description, details)
|
|
25
|
+
- Current status with history
|
|
26
|
+
- Test strategy and acceptance criteria
|
|
27
|
+
- Priority and complexity analysis
|
|
28
|
+
|
|
29
|
+
**Relationships**
|
|
30
|
+
- Dependencies (what it needs)
|
|
31
|
+
- Dependents (what needs it)
|
|
32
|
+
- Parent/subtask hierarchy
|
|
33
|
+
- Related tasks (similar work)
|
|
34
|
+
|
|
35
|
+
**Time Intelligence**
|
|
36
|
+
- Created/updated timestamps
|
|
37
|
+
- Time in current status
|
|
38
|
+
- Estimated vs actual time
|
|
39
|
+
- Historical completion patterns
|
|
40
|
+
|
|
41
|
+
### 3. **Visual Enhancements**
|
|
42
|
+
|
|
43
|
+
```
|
|
44
|
+
📋 Task #45: Implement User Authentication
|
|
45
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
46
|
+
Status: 🟡 in-progress (2 hours)
|
|
47
|
+
Priority: 🔴 High | Complexity: 73/100
|
|
48
|
+
|
|
49
|
+
Dependencies: ✅ #41, ✅ #42, ⏳ #43 (blocked)
|
|
50
|
+
Blocks: #46, #47, #52
|
|
51
|
+
|
|
52
|
+
Progress: ████████░░ 80% complete
|
|
53
|
+
|
|
54
|
+
Recent Activity:
|
|
55
|
+
- 2h ago: Status changed to in-progress
|
|
56
|
+
- 4h ago: Dependency #42 completed
|
|
57
|
+
- Yesterday: Task expanded with 3 subtasks
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
### 4. **Intelligent Insights**
|
|
61
|
+
|
|
62
|
+
Based on task analysis:
|
|
63
|
+
- **Risk Assessment**: Complexity vs time remaining
|
|
64
|
+
- **Bottleneck Analysis**: Is this blocking critical work?
|
|
65
|
+
- **Recommendation**: Suggested approach or concerns
|
|
66
|
+
- **Similar Tasks**: How others completed similar work
|
|
67
|
+
|
|
68
|
+
### 5. **Action Suggestions**
|
|
69
|
+
|
|
70
|
+
Context-aware next steps:
|
|
71
|
+
- If blocked → Show how to unblock
|
|
72
|
+
- If complex → Suggest expansion
|
|
73
|
+
- If in-progress → Show completion checklist
|
|
74
|
+
- If done → Show dependent tasks ready to start
|
|
75
|
+
|
|
76
|
+
### 6. **Multi-Task View**
|
|
77
|
+
|
|
78
|
+
When showing multiple tasks:
|
|
79
|
+
- Common dependencies
|
|
80
|
+
- Optimal completion order
|
|
81
|
+
- Parallel work opportunities
|
|
82
|
+
- Combined complexity analysis
|