@smartsoft001-mobilems/claude-plugins 2.60.0 → 2.61.0

package/package.json

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

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

@@ -1,5 +1,5 @@
 {
   "name": "flow",
   "description": "Development flow",
-  "version": "2.60.0"
+  "version": "2.61.0"
 }

package/plugins/flow/agents/shared-parallelization-analyzer.md

@@ -95,15 +95,33 @@ For each opportunity, calculate:
 
 Output the analysis as a structured markdown report (see Output Format).
 
-### Step 5: Propose Orchestrator Improvements
+### Step 5: File Orchestrator Improvement Suggestions
 
 If recurring patterns are found across multiple analyses:
 
 1. Identify the pattern (e.g., "scaffolding agents for independent files are always falsely sequentialized")
-2. Propose a rule change to `shared-impl-orchestrator.md`
-3. Include the specific section and wording to modify
+2. Formulate a rule change for `shared-impl-orchestrator.md`
+3. **Delegate to `linear-suggestion` skill** to create a Linear issue in the "MobileMS Framework" project:
 
-Only propose permanent orchestrator changes for **recurring** patterns, not one-off task-specific opportunities.
+   ```
+   title: [short description of the recurring pattern and proposed rule]
+   description: |
+     ### Observation
+     [description of the recurring pattern with evidence from multiple tasks]
+
+     ### Proposed Change
+     [target file, section, and exact wording to add/modify]
+
+     ### Evidence
+     [list of task IDs where this pattern was observed]
+   source: shared-parallelization-analyzer
+   targetFile: packages/shared/claude-plugins/src/plugins/flow/agents/shared-impl-orchestrator.md
+   category: OPTIMIZATION
+   ```
+
+4. Include the created issue ID in the console report
+
+Only file Linear issues for **recurring** patterns, not one-off task-specific opportunities. Task-specific opportunities are reported in the console only.
 
 ## Output Format
 
@@ -155,13 +173,14 @@ Only propose permanent orchestrator changes for **recurring** patterns, not one-
 - **Proposed steps**: 4 (2 parallel groups + 2 sequential)
 - **Reduction**: 2 fewer sequential steps
 
-### Orchestrator Improvement Proposals
+### Orchestrator Improvement Suggestions
 
-> Only shown if recurring patterns detected across multiple tasks
+> Only shown if recurring patterns detected across multiple tasks.
+> Suggestions are filed as Linear issues in the "MobileMS Framework" project via `linear-suggestion` skill.
 
-**Proposal**: [description of recurring pattern and suggested orchestrator rule change]
+**Suggestion**: [description of recurring pattern and suggested orchestrator rule change]
 **Target**: `shared-impl-orchestrator.md` → [section name]
-**Suggested addition**: [exact wording to add]
+**Linear issue**: [issue ID] — [issue URL]
 
 ---
 
@@ -197,7 +216,7 @@ _Analysis generated by shared-parallelization-analyzer_
 2. **Conservative analysis**: When uncertain whether a dependency exists, treat it as real. False parallelization is worse than missed optimization.
 3. **Same-file operations are always sequential**: If two agents modify the same file, they must remain sequential regardless of which parts they modify.
 4. **Only recurring patterns proposed as permanent changes**: Task-specific opportunities are reported but NOT proposed as orchestrator modifications. Only patterns observed repeatedly should be suggested as `shared-impl-orchestrator.md` changes.
-5. **Non-blocking and advisory**: This analysis is informational only. It does not block any workflow and proposals are shown to the user without auto-applying.
+5. **Non-blocking and advisory**: This analysis is informational only. It does not block any workflow. Recurring pattern suggestions are filed as Linear issues via `linear-suggestion` skill — never auto-applied to agent files.
 6. **Respect existing PARALLEL annotations**: If the orchestration plan already marks agents as PARALLEL, confirm or flag them rather than re-proposing.
 
 ## Examples

package/plugins/flow/commands/commit.md

@@ -135,7 +135,7 @@ After the commit is created, perform an optional parallelization analysis:
 
 - This step is **non-blocking** and **advisory only**
 - The analysis report is shown to the user in the console but is NOT auto-applied
-- Orchestrator improvement proposals (if any) are presented for the user to review
+- Recurring orchestrator improvement suggestions (if any) are filed as Linear issues in the "MobileMS Framework" project via `linear-suggestion` skill — no user interaction required
 - A commit failure or missing orchestration plan should never cause this step to error
 
 ### Guidelines
@@ -146,7 +146,7 @@ After the commit is created, perform an optional parallelization analysis:
 4. If task type is unclear, analyze the code changes to determine type
 5. Always include the Linear task reference in the footer
 6. If there are no staged changes, warn the user and don't create commit
-7. After a successful commit, run the optional parallelization analysis (Step 6) to surface optimization opportunities from the orchestration plan
+7. After a successful commit, run the optional parallelization analysis (Step 6) to surface optimization opportunities from the orchestration plan. Recurring patterns are filed as Linear issues automatically via `linear-suggestion` skill
 
 ### Example
 
@@ -176,11 +176,19 @@ For Linear task "ENG-123: Add dark mode toggle to settings":
 - **Proposed steps**: 4 (1 parallel group + 3 sequential)
 - **Reduction**: 1 fewer sequential step
 
+### Orchestrator Improvement Suggestions
+
+**Suggestion**: Independent scaffolding agents are always falsely sequentialized
+**Target**: `shared-impl-orchestrator.md` → Parallel vs Sequential
+**Linear issue**: MOB-815 — https://linear.app/mobilems/issue/MOB-815
+
 ---
 
 _Analysis generated by shared-parallelization-analyzer_
 ```
 
+If a recurring pattern is detected, a Linear issue is automatically created in "MobileMS Framework" via `linear-suggestion` skill.
+
 If no orchestration plan is found in Linear comments, this step is silently skipped.
 
 ---

package/plugins/flow/skills/linear-suggestion/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: linear-suggestion
+description: Create a Linear issue in the "MobileMS Framework" project with a suggestion for agent, command, or skill improvements.
+allowed-tools: mcp__linear-server__create_issue
+---
+
+# Linear Suggestion
+
+Create a Linear issue in the **MobileMS Framework** project containing a suggestion for improving agent definitions, commands, or skills. Used by automated analysis agents to propose changes without blocking the workflow.
+
+## When to Use
+
+- When an automated agent (e.g., `shared-parallelization-analyzer`) identifies a recurring pattern that could improve an agent, command, or skill
+- When proposing orchestrator rule changes based on parallelization analysis
+- When any non-interactive process needs to suggest framework improvements
+
+## Input Parameters
+
+The invoking agent must provide:
+
+| Parameter     | Required | Description                                                     |
+| ------------- | -------- | --------------------------------------------------------------- |
+| `title`       | YES      | Short summary of the suggestion (max 100 chars)                 |
+| `description` | YES      | Full markdown description with rationale and proposed changes    |
+| `source`      | YES      | Agent that generated the suggestion (e.g., `shared-parallelization-analyzer`) |
+| `targetFile`  | NO       | Path to the file to be modified (e.g., `agents/shared-impl-orchestrator.md`) |
+| `category`    | NO       | One of: `OPTIMIZATION`, `NEW_RULE`, `PATTERN_UPDATE`, `BUG_FIX` |
+
+## Issue Format
+
+### Title
+
+```
+[Agent Suggestion] {title}
+```
+
+### Description
+
+```markdown
+## Agent Improvement Suggestion
+
+**Source agent**: `{source}`
+**Category**: {category}
+**Target file**: `{targetFile}`
+
+---
+
+{description}
+
+---
+
+_This issue was automatically created by `{source}` via the `linear-suggestion` skill._
+_Review and apply manually if the suggestion is valid._
+```
+
+## Process
+
+1. **Format the issue title** with `[Agent Suggestion]` prefix
+2. **Build the description** using the template above, inserting all provided parameters
+3. **Create the issue** using MCP Linear server:
+
+   ```
+   Create issue in project "MobileMS Framework":
+   - Title: [Agent Suggestion] {title}
+   - Description: {formatted description}
+   - Label: agent-evolution
+   ```
+
+4. **Return the issue ID and URL** to the invoking agent
+
+## Output Format
+
+After successful creation, return:
+
+```
+Linear issue created:
+- ID: {issueId}
+- Title: [Agent Suggestion] {title}
+- URL: {issueUrl}
+```
+
+## Error Handling
+
+If issue creation fails (e.g., MCP Linear server unavailable):
+
+- Log the error silently
+- Do NOT block the parent workflow
+- Return a failure notice without throwing
+
+```
+Linear suggestion skipped: {error reason}
+```
+
+## Example
+
+**Input from `shared-parallelization-analyzer`:**
+
+```
+title: Add parallel scaffolding rule to orchestrator
+description: |
+  ### Observation
+
+  In 3 out of 5 recent tasks, scaffolding agents for independent files
+  (e.g., `angular-component-scaffolder` + `angular-service-builder`) were
+  marked as SEQ despite having no shared output files.
+
+  ### Proposed Change
+
+  Add to `shared-impl-orchestrator.md` → Execution Patterns → Parallel vs Sequential:
+
+  | Scenario                                | Pattern  | Reason                          |
+  | --------------------------------------- | -------- | ------------------------------- |
+  | Multiple scaffolding for independent files | PARALLEL | No shared output files between scaffolders |
+
+  ### Evidence
+
+  - MOB-700: scaffold-component + scaffold-service (independent)
+  - MOB-705: scaffold-directive + scaffold-service (independent)
+  - MOB-710: scaffold-component + scaffold-pipe (independent)
+source: shared-parallelization-analyzer
+targetFile: packages/shared/claude-plugins/src/plugins/flow/agents/shared-impl-orchestrator.md
+category: OPTIMIZATION
+```
+
+**Created issue:**
+
+```
+Linear issue created:
+- ID: MOB-815
+- Title: [Agent Suggestion] Add parallel scaffolding rule to orchestrator
+- URL: https://linear.app/mobilems/issue/MOB-815
+```