@smartsoft001-mobilems/claude-plugins 2.72.0 → 2.74.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smartsoft001-mobilems/claude-plugins",
-  "version": "2.72.0",
+  "version": "2.74.0",
   "publishConfig": {
     "access": "public"
   },

package/plugins/flow/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "flow",
   "description": "Development flow skills for Linear-driven development workflow",
-  "version": "2.72.0"
+  "version": "2.74.0"
 }

package/plugins/flow/skills/commit/SKILL.md

@@ -7,6 +7,10 @@ allowed-tools:
   - Glob
   - Grep
   - AskUserQuestion
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
   - mcp__linear-server__get_issue
   - mcp__linear-server__list_comments
 ---
@@ -39,6 +43,38 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **8. Create commit** — execute `git commit` with the approved message
 - [ ] **9. Parallelization analysis (optional)** — fetch Linear comments, search for orchestration plan, delegate to `shared-parallelization-analyzer` if found
 
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for each checklist step using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "MM-123 Fetch Linear task",
+  description: "Get title, description, labels/type from MCP Linear server",
+  activeForm: "MM-123 Fetching Linear task"
+})
+TaskCreate({
+  subject: "MM-123 Analyze staged changes",
+  description: "Run git diff --cached to understand scope",
+  activeForm: "MM-123 Analyzing staged changes"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+
+**At checkpoints**: Use `TaskList` to review overall progress before presenting status to user.
+
 ## Instructions
 
 You are tasked with creating a git commit based on a Linear task and staged changes.

package/plugins/flow/skills/impl/SKILL.md

@@ -10,6 +10,10 @@ allowed-tools:
   - Grep
   - AskUserQuestion
   - Task
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
   - mcp__linear-server__get_issue
   - mcp__linear-server__list_issues
   - mcp__linear-server__list_comments
@@ -54,6 +58,54 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **18. Session-wide evolution** — analyze all feedback across session
 - [ ] **19. ALWAYS pause** — wait for user confirmation at end
 
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID (parent or subtask):
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for the initial setup using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "MM-123 Fetch task and subtasks",
+  description: "Delegate to shared-linear-subtask-iterator agent",
+  activeForm: "MM-123 Fetching task and subtasks"
+})
+```
+
+**Per subtask**: Create a parent task for the subtask, then child tasks for each step — all prefixed with the subtask ID:
+
+```
+TaskCreate({
+  subject: "MM-123-1 Implement subtask",
+  description: "Full implementation cycle: classify → orchestrate → implement → verify",
+  activeForm: "MM-123-1 Implementing subtask"
+})
+TaskCreate({
+  subject: "MM-123-1 UI change classification",
+  description: "Delegate to shared-ui-classifier agent",
+  activeForm: "MM-123-1 Classifying UI changes"
+})
+TaskCreate({
+  subject: "MM-123-1 Verify implementation",
+  description: "Run tests, lint, build check",
+  activeForm: "MM-123-1 Verifying implementation"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+- At 3x3 checkpoints → `TaskList` to show progress overview
+
+**At pause points**: Use `TaskList` to present a clear status summary to the user before waiting for confirmation.
+
 ## Role
 
 **You are a highly experienced senior TypeScript developer** with:

package/plugins/flow/skills/plan/SKILL.md

@@ -7,6 +7,10 @@ allowed-tools:
   - Glob
   - Grep
   - AskUserQuestion
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
   - mcp__linear-server__get_issue
   - mcp__linear-server__list_issues
   - mcp__linear-server__list_comments
@@ -37,6 +41,38 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **13. Delete old plan comments and save new ones** — delete outdated plan comments from Linear, then post new plans via MCP
 - [ ] **14. Confirm to user** — list saved plans with summaries and Linear links
 
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for each checklist step using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "MM-123 Fetch Linear task",
+  description: "Get title, description, labels, priority, estimate from MCP Linear server",
+  activeForm: "MM-123 Fetching Linear task"
+})
+TaskCreate({
+  subject: "MM-123 Analyze codebase",
+  description: "Explore affected files, patterns, dependencies, and test coverage",
+  activeForm: "MM-123 Analyzing codebase"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+
+**Before user review**: Use `TaskList` to show progress overview before presenting plans for approval.
+
 ## Role
 
 **You are a highly experienced software architect** with:

package/plugins/flow/skills/push/SKILL.md

@@ -8,6 +8,10 @@ allowed-tools:
   - Grep
   - AskUserQuestion
   - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
   - mcp__linear-server__get_issue
   - mcp__linear-server__list_issues
   - mcp__linear-server__list_comments
@@ -58,6 +62,39 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 - [ ] **12. Show final status** — complete summary of all actions taken
 
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for each checklist step using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "MM-123 Check git status",
+  description: "Verify branch, commits ahead, warn about uncommitted changes",
+  activeForm: "MM-123 Checking git status"
+})
+TaskCreate({
+  subject: "MM-123 Push to remote",
+  description: "Execute git push and handle errors",
+  activeForm: "MM-123 Pushing to remote"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+- For branch-specific steps, only create tasks for the applicable branch path (development OR feature)
+
+**Before user decisions**: Use `TaskList` to show progress overview before asking user about status changes or PR creation.
+
 ## Usage
 
 ```

package/plugins/flow-legacy/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "flow-legacy",
   "description": "Development flow skills for legacy Angular 14 projects with Linear-driven workflow",
-  "version": "2.72.0"
+  "version": "2.74.0"
 }

package/plugins/flow-legacy/skills/commit/SKILL.md

@@ -7,6 +7,10 @@ allowed-tools:
   - Glob
   - Grep
   - AskUserQuestion
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
   - mcp__linear-server__get_issue
   - mcp__linear-server__list_comments
 ---
@@ -39,6 +43,38 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **8. Create commit** — execute `git commit` with the approved message
 - [ ] **9. Parallelization analysis (optional)** — fetch Linear comments, search for orchestration plan, delegate to `shared-parallelization-analyzer` if found
 
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for each checklist step using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "MM-123 Fetch Linear task",
+  description: "Get title, description, labels/type from MCP Linear server",
+  activeForm: "MM-123 Fetching Linear task"
+})
+TaskCreate({
+  subject: "MM-123 Analyze staged changes",
+  description: "Run git diff --cached to understand scope",
+  activeForm: "MM-123 Analyzing staged changes"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+
+**At checkpoints**: Use `TaskList` to review overall progress before presenting status to user.
+
 ## Instructions
 
 You are tasked with creating a git commit based on a Linear task and staged changes.

package/plugins/flow-legacy/skills/impl/SKILL.md

@@ -10,6 +10,10 @@ allowed-tools:
   - Grep
   - AskUserQuestion
   - Task
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
   - mcp__linear-server__get_issue
   - mcp__linear-server__list_issues
   - mcp__linear-server__list_comments
@@ -54,6 +58,54 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **18. Final summary** — present summary of all subtasks with statuses
 - [ ] **19. ALWAYS pause** — wait for user confirmation at end
 
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID (parent or subtask):
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for the initial setup using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "MM-123 Fetch task and subtasks",
+  description: "Delegate to shared-linear-subtask-iterator agent",
+  activeForm: "MM-123 Fetching task and subtasks"
+})
+```
+
+**Per subtask**: Create a parent task for the subtask, then child tasks for each step — all prefixed with the subtask ID:
+
+```
+TaskCreate({
+  subject: "MM-123-1 Implement subtask",
+  description: "Full implementation cycle: classify → orchestrate → implement → verify",
+  activeForm: "MM-123-1 Implementing subtask"
+})
+TaskCreate({
+  subject: "MM-123-1 UI change classification",
+  description: "Delegate to shared-ui-classifier agent",
+  activeForm: "MM-123-1 Classifying UI changes"
+})
+TaskCreate({
+  subject: "MM-123-1 Verify implementation",
+  description: "Run tests, lint, build check",
+  activeForm: "MM-123-1 Verifying implementation"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+- At 3x3 checkpoints → `TaskList` to show progress overview
+
+**At pause points**: Use `TaskList` to present a clear status summary to the user before waiting for confirmation.
+
 ## Role
 
 **You are a highly experienced senior TypeScript developer** with:

package/plugins/flow-legacy/skills/plan/SKILL.md

@@ -7,6 +7,10 @@ allowed-tools:
   - Glob
   - Grep
   - AskUserQuestion
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
   - mcp__linear-server__get_issue
   - mcp__linear-server__list_issues
   - mcp__linear-server__list_comments
@@ -38,6 +42,38 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **14. Delete old plan comments and save new ones** — delete outdated plan comments from Linear, then post new plans via MCP
 - [ ] **15. Confirm to user** — list saved plans with summaries and Linear links
 
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for each checklist step using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "MM-123 Fetch Linear task",
+  description: "Get title, description, labels, priority, estimate from MCP Linear server",
+  activeForm: "MM-123 Fetching Linear task"
+})
+TaskCreate({
+  subject: "MM-123 Analyze codebase",
+  description: "Explore affected files, patterns, dependencies, and test coverage",
+  activeForm: "MM-123 Analyzing codebase"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+
+**Before user review**: Use `TaskList` to show progress overview before presenting plans for approval.
+
 ## Role
 
 **You are a highly experienced software architect** with:

package/plugins/flow-legacy/skills/push/SKILL.md

@@ -8,6 +8,10 @@ allowed-tools:
   - Grep
   - AskUserQuestion
   - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
   - mcp__linear-server__get_issue
   - mcp__linear-server__list_issues
   - mcp__linear-server__list_comments
@@ -58,6 +62,39 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 
 - [ ] **12. Show final status** — complete summary of all actions taken
 
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**Task naming convention**: Every task subject MUST be prefixed with the Linear task ID:
+
+```
+<linearTaskId> <step description>
+```
+
+**At skill start**: Create tasks for each checklist step using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "MM-123 Check git status",
+  description: "Verify branch, commits ahead, warn about uncommitted changes",
+  activeForm: "MM-123 Checking git status"
+})
+TaskCreate({
+  subject: "MM-123 Push to remote",
+  description: "Execute git push and handle errors",
+  activeForm: "MM-123 Pushing to remote"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+- For branch-specific steps, only create tasks for the applicable branch path (development OR feature)
+
+**Before user decisions**: Use `TaskList` to show progress overview before asking user about status changes or PR creation.
+
 ## Usage
 
 ```