@smartsoft001-mobilems/claude-plugins 2.72.0 → 2.73.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/package.json +1 -1
- package/plugins/flow/.claude-plugin/plugin.json +1 -1
- package/plugins/flow/skills/commit/SKILL.md +25 -0
- package/plugins/flow/skills/impl/SKILL.md +36 -0
- package/plugins/flow/skills/plan/SKILL.md +25 -0
- package/plugins/flow/skills/push/SKILL.md +26 -0
- package/plugins/flow-legacy/.claude-plugin/plugin.json +1 -1
- package/plugins/flow-legacy/skills/commit/SKILL.md +25 -0
- package/plugins/flow-legacy/skills/impl/SKILL.md +36 -0
- package/plugins/flow-legacy/skills/plan/SKILL.md +25 -0
- package/plugins/flow-legacy/skills/push/SKILL.md +26 -0
package/package.json
CHANGED
|
@@ -7,6 +7,10 @@ allowed-tools:
|
|
|
7
7
|
- Glob
|
|
8
8
|
- Grep
|
|
9
9
|
- AskUserQuestion
|
|
10
|
+
- TaskCreate
|
|
11
|
+
- TaskUpdate
|
|
12
|
+
- TaskList
|
|
13
|
+
- TaskGet
|
|
10
14
|
- mcp__linear-server__get_issue
|
|
11
15
|
- mcp__linear-server__list_comments
|
|
12
16
|
---
|
|
@@ -39,6 +43,27 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
39
43
|
- [ ] **8. Create commit** — execute `git commit` with the approved message
|
|
40
44
|
- [ ] **9. Parallelization analysis (optional)** — fetch Linear comments, search for orchestration plan, delegate to `shared-parallelization-analyzer` if found
|
|
41
45
|
|
|
46
|
+
### Task Progress Tracking
|
|
47
|
+
|
|
48
|
+
**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
|
|
49
|
+
|
|
50
|
+
**At skill start**: Create tasks for each checklist step using `TaskCreate`:
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
TaskCreate({
|
|
54
|
+
subject: "Fetch Linear task",
|
|
55
|
+
description: "Get title, description, labels/type from MCP Linear server",
|
|
56
|
+
activeForm: "Fetching Linear task"
|
|
57
|
+
})
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
**During execution**:
|
|
61
|
+
|
|
62
|
+
- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
|
|
63
|
+
- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
|
|
64
|
+
|
|
65
|
+
**At checkpoints**: Use `TaskList` to review overall progress before presenting status to user.
|
|
66
|
+
|
|
42
67
|
## Instructions
|
|
43
68
|
|
|
44
69
|
You are tasked with creating a git commit based on a Linear task and staged changes.
|
|
@@ -10,6 +10,10 @@ allowed-tools:
|
|
|
10
10
|
- Grep
|
|
11
11
|
- AskUserQuestion
|
|
12
12
|
- Task
|
|
13
|
+
- TaskCreate
|
|
14
|
+
- TaskUpdate
|
|
15
|
+
- TaskList
|
|
16
|
+
- TaskGet
|
|
13
17
|
- mcp__linear-server__get_issue
|
|
14
18
|
- mcp__linear-server__list_issues
|
|
15
19
|
- mcp__linear-server__list_comments
|
|
@@ -54,6 +58,38 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
54
58
|
- [ ] **18. Session-wide evolution** — analyze all feedback across session
|
|
55
59
|
- [ ] **19. ALWAYS pause** — wait for user confirmation at end
|
|
56
60
|
|
|
61
|
+
### Task Progress Tracking
|
|
62
|
+
|
|
63
|
+
**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
|
|
64
|
+
|
|
65
|
+
**At skill start**: Create tasks for the initial setup and each subtask processing round using `TaskCreate`:
|
|
66
|
+
|
|
67
|
+
```
|
|
68
|
+
TaskCreate({
|
|
69
|
+
subject: "Fetch task and subtasks",
|
|
70
|
+
description: "Delegate to shared-linear-subtask-iterator agent",
|
|
71
|
+
activeForm: "Fetching task and subtasks"
|
|
72
|
+
})
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
**Per subtask**: Create a parent task for the subtask, then child tasks for each step:
|
|
76
|
+
|
|
77
|
+
```
|
|
78
|
+
TaskCreate({
|
|
79
|
+
subject: "Implement subtask MOB-123",
|
|
80
|
+
description: "Full implementation cycle: classify → orchestrate → implement → verify",
|
|
81
|
+
activeForm: "Implementing subtask MOB-123"
|
|
82
|
+
})
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
**During execution**:
|
|
86
|
+
|
|
87
|
+
- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
|
|
88
|
+
- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
|
|
89
|
+
- At 3x3 checkpoints → `TaskList` to show progress overview
|
|
90
|
+
|
|
91
|
+
**At pause points**: Use `TaskList` to present a clear status summary to the user before waiting for confirmation.
|
|
92
|
+
|
|
57
93
|
## Role
|
|
58
94
|
|
|
59
95
|
**You are a highly experienced senior TypeScript developer** with:
|
|
@@ -7,6 +7,10 @@ allowed-tools:
|
|
|
7
7
|
- Glob
|
|
8
8
|
- Grep
|
|
9
9
|
- AskUserQuestion
|
|
10
|
+
- TaskCreate
|
|
11
|
+
- TaskUpdate
|
|
12
|
+
- TaskList
|
|
13
|
+
- TaskGet
|
|
10
14
|
- mcp__linear-server__get_issue
|
|
11
15
|
- mcp__linear-server__list_issues
|
|
12
16
|
- mcp__linear-server__list_comments
|
|
@@ -37,6 +41,27 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
37
41
|
- [ ] **13. Delete old plan comments and save new ones** — delete outdated plan comments from Linear, then post new plans via MCP
|
|
38
42
|
- [ ] **14. Confirm to user** — list saved plans with summaries and Linear links
|
|
39
43
|
|
|
44
|
+
### Task Progress Tracking
|
|
45
|
+
|
|
46
|
+
**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
|
|
47
|
+
|
|
48
|
+
**At skill start**: Create tasks for each checklist step using `TaskCreate`:
|
|
49
|
+
|
|
50
|
+
```
|
|
51
|
+
TaskCreate({
|
|
52
|
+
subject: "Fetch Linear task",
|
|
53
|
+
description: "Get title, description, labels, priority, estimate from MCP Linear server",
|
|
54
|
+
activeForm: "Fetching Linear task"
|
|
55
|
+
})
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
**During execution**:
|
|
59
|
+
|
|
60
|
+
- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
|
|
61
|
+
- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
|
|
62
|
+
|
|
63
|
+
**Before user review**: Use `TaskList` to show progress overview before presenting plans for approval.
|
|
64
|
+
|
|
40
65
|
## Role
|
|
41
66
|
|
|
42
67
|
**You are a highly experienced software architect** with:
|
|
@@ -8,6 +8,10 @@ allowed-tools:
|
|
|
8
8
|
- Grep
|
|
9
9
|
- AskUserQuestion
|
|
10
10
|
- WebFetch
|
|
11
|
+
- TaskCreate
|
|
12
|
+
- TaskUpdate
|
|
13
|
+
- TaskList
|
|
14
|
+
- TaskGet
|
|
11
15
|
- mcp__linear-server__get_issue
|
|
12
16
|
- mcp__linear-server__list_issues
|
|
13
17
|
- mcp__linear-server__list_comments
|
|
@@ -58,6 +62,28 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
58
62
|
|
|
59
63
|
- [ ] **12. Show final status** — complete summary of all actions taken
|
|
60
64
|
|
|
65
|
+
### Task Progress Tracking
|
|
66
|
+
|
|
67
|
+
**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
|
|
68
|
+
|
|
69
|
+
**At skill start**: Create tasks for each checklist step using `TaskCreate`:
|
|
70
|
+
|
|
71
|
+
```
|
|
72
|
+
TaskCreate({
|
|
73
|
+
subject: "Check git status",
|
|
74
|
+
description: "Verify branch, commits ahead, warn about uncommitted changes",
|
|
75
|
+
activeForm: "Checking git status"
|
|
76
|
+
})
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
**During execution**:
|
|
80
|
+
|
|
81
|
+
- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
|
|
82
|
+
- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
|
|
83
|
+
- For branch-specific steps, only create tasks for the applicable branch path (development OR feature)
|
|
84
|
+
|
|
85
|
+
**Before user decisions**: Use `TaskList` to show progress overview before asking user about status changes or PR creation.
|
|
86
|
+
|
|
61
87
|
## Usage
|
|
62
88
|
|
|
63
89
|
```
|
|
@@ -7,6 +7,10 @@ allowed-tools:
|
|
|
7
7
|
- Glob
|
|
8
8
|
- Grep
|
|
9
9
|
- AskUserQuestion
|
|
10
|
+
- TaskCreate
|
|
11
|
+
- TaskUpdate
|
|
12
|
+
- TaskList
|
|
13
|
+
- TaskGet
|
|
10
14
|
- mcp__linear-server__get_issue
|
|
11
15
|
- mcp__linear-server__list_comments
|
|
12
16
|
---
|
|
@@ -39,6 +43,27 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
39
43
|
- [ ] **8. Create commit** — execute `git commit` with the approved message
|
|
40
44
|
- [ ] **9. Parallelization analysis (optional)** — fetch Linear comments, search for orchestration plan, delegate to `shared-parallelization-analyzer` if found
|
|
41
45
|
|
|
46
|
+
### Task Progress Tracking
|
|
47
|
+
|
|
48
|
+
**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
|
|
49
|
+
|
|
50
|
+
**At skill start**: Create tasks for each checklist step using `TaskCreate`:
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
TaskCreate({
|
|
54
|
+
subject: "Fetch Linear task",
|
|
55
|
+
description: "Get title, description, labels/type from MCP Linear server",
|
|
56
|
+
activeForm: "Fetching Linear task"
|
|
57
|
+
})
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
**During execution**:
|
|
61
|
+
|
|
62
|
+
- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
|
|
63
|
+
- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
|
|
64
|
+
|
|
65
|
+
**At checkpoints**: Use `TaskList` to review overall progress before presenting status to user.
|
|
66
|
+
|
|
42
67
|
## Instructions
|
|
43
68
|
|
|
44
69
|
You are tasked with creating a git commit based on a Linear task and staged changes.
|
|
@@ -10,6 +10,10 @@ allowed-tools:
|
|
|
10
10
|
- Grep
|
|
11
11
|
- AskUserQuestion
|
|
12
12
|
- Task
|
|
13
|
+
- TaskCreate
|
|
14
|
+
- TaskUpdate
|
|
15
|
+
- TaskList
|
|
16
|
+
- TaskGet
|
|
13
17
|
- mcp__linear-server__get_issue
|
|
14
18
|
- mcp__linear-server__list_issues
|
|
15
19
|
- mcp__linear-server__list_comments
|
|
@@ -54,6 +58,38 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
54
58
|
- [ ] **18. Final summary** — present summary of all subtasks with statuses
|
|
55
59
|
- [ ] **19. ALWAYS pause** — wait for user confirmation at end
|
|
56
60
|
|
|
61
|
+
### Task Progress Tracking
|
|
62
|
+
|
|
63
|
+
**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
|
|
64
|
+
|
|
65
|
+
**At skill start**: Create tasks for the initial setup and each subtask processing round using `TaskCreate`:
|
|
66
|
+
|
|
67
|
+
```
|
|
68
|
+
TaskCreate({
|
|
69
|
+
subject: "Fetch task and subtasks",
|
|
70
|
+
description: "Delegate to shared-linear-subtask-iterator agent",
|
|
71
|
+
activeForm: "Fetching task and subtasks"
|
|
72
|
+
})
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
**Per subtask**: Create a parent task for the subtask, then child tasks for each step:
|
|
76
|
+
|
|
77
|
+
```
|
|
78
|
+
TaskCreate({
|
|
79
|
+
subject: "Implement subtask MOB-123",
|
|
80
|
+
description: "Full implementation cycle: classify → orchestrate → implement → verify",
|
|
81
|
+
activeForm: "Implementing subtask MOB-123"
|
|
82
|
+
})
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
**During execution**:
|
|
86
|
+
|
|
87
|
+
- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
|
|
88
|
+
- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
|
|
89
|
+
- At 3x3 checkpoints → `TaskList` to show progress overview
|
|
90
|
+
|
|
91
|
+
**At pause points**: Use `TaskList` to present a clear status summary to the user before waiting for confirmation.
|
|
92
|
+
|
|
57
93
|
## Role
|
|
58
94
|
|
|
59
95
|
**You are a highly experienced senior TypeScript developer** with:
|
|
@@ -7,6 +7,10 @@ allowed-tools:
|
|
|
7
7
|
- Glob
|
|
8
8
|
- Grep
|
|
9
9
|
- AskUserQuestion
|
|
10
|
+
- TaskCreate
|
|
11
|
+
- TaskUpdate
|
|
12
|
+
- TaskList
|
|
13
|
+
- TaskGet
|
|
10
14
|
- mcp__linear-server__get_issue
|
|
11
15
|
- mcp__linear-server__list_issues
|
|
12
16
|
- mcp__linear-server__list_comments
|
|
@@ -38,6 +42,27 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
38
42
|
- [ ] **14. Delete old plan comments and save new ones** — delete outdated plan comments from Linear, then post new plans via MCP
|
|
39
43
|
- [ ] **15. Confirm to user** — list saved plans with summaries and Linear links
|
|
40
44
|
|
|
45
|
+
### Task Progress Tracking
|
|
46
|
+
|
|
47
|
+
**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
|
|
48
|
+
|
|
49
|
+
**At skill start**: Create tasks for each checklist step using `TaskCreate`:
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
TaskCreate({
|
|
53
|
+
subject: "Fetch Linear task",
|
|
54
|
+
description: "Get title, description, labels, priority, estimate from MCP Linear server",
|
|
55
|
+
activeForm: "Fetching Linear task"
|
|
56
|
+
})
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
**During execution**:
|
|
60
|
+
|
|
61
|
+
- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
|
|
62
|
+
- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
|
|
63
|
+
|
|
64
|
+
**Before user review**: Use `TaskList` to show progress overview before presenting plans for approval.
|
|
65
|
+
|
|
41
66
|
## Role
|
|
42
67
|
|
|
43
68
|
**You are a highly experienced software architect** with:
|
|
@@ -8,6 +8,10 @@ allowed-tools:
|
|
|
8
8
|
- Grep
|
|
9
9
|
- AskUserQuestion
|
|
10
10
|
- WebFetch
|
|
11
|
+
- TaskCreate
|
|
12
|
+
- TaskUpdate
|
|
13
|
+
- TaskList
|
|
14
|
+
- TaskGet
|
|
11
15
|
- mcp__linear-server__get_issue
|
|
12
16
|
- mcp__linear-server__list_issues
|
|
13
17
|
- mcp__linear-server__list_comments
|
|
@@ -58,6 +62,28 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
58
62
|
|
|
59
63
|
- [ ] **12. Show final status** — complete summary of all actions taken
|
|
60
64
|
|
|
65
|
+
### Task Progress Tracking
|
|
66
|
+
|
|
67
|
+
**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
|
|
68
|
+
|
|
69
|
+
**At skill start**: Create tasks for each checklist step using `TaskCreate`:
|
|
70
|
+
|
|
71
|
+
```
|
|
72
|
+
TaskCreate({
|
|
73
|
+
subject: "Check git status",
|
|
74
|
+
description: "Verify branch, commits ahead, warn about uncommitted changes",
|
|
75
|
+
activeForm: "Checking git status"
|
|
76
|
+
})
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
**During execution**:
|
|
80
|
+
|
|
81
|
+
- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
|
|
82
|
+
- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
|
|
83
|
+
- For branch-specific steps, only create tasks for the applicable branch path (development OR feature)
|
|
84
|
+
|
|
85
|
+
**Before user decisions**: Use `TaskList` to show progress overview before asking user about status changes or PR creation.
|
|
86
|
+
|
|
61
87
|
## Usage
|
|
62
88
|
|
|
63
89
|
```
|