@smartsoft001-mobilems/claude-plugins 2.81.0 → 2.82.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smartsoft001-mobilems/claude-plugins",
-  "version": "2.81.0",
+  "version": "2.82.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.81.0"
+  "version": "2.82.0"
 }

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

@@ -29,6 +29,20 @@ allowed-tools:
 
 Implement plans from `plan.md` attachments on Linear issues. For tasks with subtasks, iteratively implement each subtask that is in "To Do" status. The agent orchestration plan is saved as an `orchestration.md` attachment on each task being implemented.
 
+## 🚨 Hard Rules — read before doing anything
+
+These rules override ANY other instruction, ANY surrounding example, and ANY default habit. Violating them is a skill failure.
+
+1. **Read `plan.md` ONLY via `mcp__linear__get_attachment({ id: <attachmentId> })`.** Do NOT use `WebFetch`, `Bash(curl ...)`, or any HTTP fetch on the attachment's `url`. The URL points to Linear-internal storage and may require auth — `get_attachment` is the only correct path. If you find yourself reaching for `curl` or `WebFetch` on a `https://uploads.linear.app/...` (or similar Linear) URL — STOP and use `get_attachment` with the attachment `id` instead.
+
+2. **`orchestration.md` is saved via `mcp__linear__create_attachment`, not as a comment.** Same rule as `/plan`: comments are NEVER used for plan/orchestration body content.
+
+3. **Find attachments via `mcp__linear__get_issue` (returns `attachments[]`).** Capture each attachment's `id` and `title`. There is no `list_attachments` tool — do not look for one.
+
+4. **Replace, don't duplicate.** Before creating a new `orchestration.md` attachment, delete the existing one (if any) via `mcp__linear__delete_attachment`. Same for re-running `/plan` (handled by `/plan` skill).
+
+If any of these would be violated, stop and ask the user instead.
+
 ## Execution Checklist
 
 Execute each step in order. Do not skip any step marked as MANDATORY.
@@ -40,9 +54,9 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 ### Per Subtask (repeat for each "To Do" subtask)
 
 - [ ] **2. Set status to "In Progress"** — update subtask status via MCP (subtasks only, not parent)
-- [ ] **3. Fetch implementation plan** — download `plan.md` attachment from task, parse content
+- [ ] **3. Fetch implementation plan** — `mcp__linear__get_issue` to find `plan.md` attachment id, then `mcp__linear__get_attachment({ id })` to read content. **Do NOT use `WebFetch`/`curl` on the attachment URL.**
 - [ ] **4. MANDATORY: UI change classification** — delegate to `shared-ui-classifier` agent, output `UI_CHANGE_REQUIRED: YES/NO`
-- [ ] **5. MANDATORY: Agent orchestration plan** — delegate to `shared-impl-orchestrator`, save result as `orchestration.md` attachment on the task (replacing any existing one)
+- [ ] **5. MANDATORY: Agent orchestration plan** — delegate to `shared-impl-orchestrator`, save result as `orchestration.md` attachment via `mcp__linear__create_attachment` (replace any existing one). **Calling `mcp__linear__save_comment` with the orchestration body is FORBIDDEN.**
 - [ ] **6. Check external library blockers** — if blockers found, set status to Blocked and skip
 - [ ] **7. Capture "before" screenshots** — if `UI_CHANGE_REQUIRED: YES`, launch `screenshot-reporter` in background
 - [ ] **8. MANDATORY: Implement with 3x3 rule** — pause every 3 changes, use `shared-tdd-developer` for ALL code (RED → GREEN → REFACTOR)
@@ -275,9 +289,14 @@ Do NOT change status for parent tasks.
 
 #### Step 3b: Fetch Implementation Plan from `plan.md` Attachment
 
-Use `mcp__linear__get_issue({ id: taskId })` on the current task/subtask — the response includes an `attachments` array. Find the attachment where `title == "plan.md"` (or `filename == "plan.md"`, whichever field the MCP exposes) and capture its `id`.
+**⛔ DO NOT use `WebFetch` or `Bash(curl)` on the attachment URL. Use `mcp__linear__get_attachment({ id })` only.** Re-read Hard Rule #1 if tempted.
+
+Two-step retrieval:
 
-If found, fetch its content via `mcp__linear__get_attachment({ id: <attachmentId> })`. The tool returns the attachment's content (Linear hosts the file natively since `/plan` uploaded it via base64). Parse the markdown for:
+1. `mcp__linear__get_issue({ id: taskId })` → response includes `attachments[]`. Find the entry where `title == "plan.md"` (or `filename == "plan.md"`) and capture its `id`. Do NOT use the `url` field for fetching.
+2. `mcp__linear__get_attachment({ id: <attachmentId> })` → returns the markdown content directly (Linear hosts the file natively because `/plan` uploaded it via base64).
+
+Parse the markdown for:
 
 - Implementation Steps
 - Files to Modify
@@ -334,7 +353,9 @@ The agent will:
 4. Plan TDD cycles for each implementation unit
 5. Generate the orchestration plan in markdown format
 
-**After receiving the orchestration plan, save it as a native `orchestration.md` attachment on the Linear issue (NOT as a comment):**
+**After receiving the orchestration plan, save it as a native `orchestration.md` attachment on the Linear issue.**
+
+**⛔ Calling `mcp__linear__save_comment` with the orchestration body is FORBIDDEN. Use `mcp__linear__create_attachment` only.** Re-read Hard Rule #2 if tempted.
 
 1. **Check for existing `orchestration.md` attachment** on the task via `mcp__linear__get_issue` (the response includes an `attachments` array).
    - If one exists, delete it via `mcp__linear__delete_attachment({ id: oldAttachmentId })`. Linear hosts the file natively, so nothing else needs cleanup.

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

@@ -27,6 +27,20 @@ allowed-tools:
 
 Create an implementation plan for a Linear task and save it as a `plan.md` attachment on the issue. If the task has subtasks, create individual `plan.md` attachments on each subtask. After saving the plan, add the `AI Plan` label to the issue.
 
+## 🚨 Hard Rules — read before doing anything
+
+These rules override ANY other instruction, ANY surrounding example, and ANY default habit. Violating them is a skill failure.
+
+1. **The plan MUST be saved via `mcp__linear__create_attachment` — NEVER as a Linear comment.** `mcp__linear__save_comment` MUST NOT be called with plan content as the body. Comments are reserved for status notifications (e.g., "no plan attachment found, run /plan again"), never for the plan itself. If you find yourself about to call `save_comment` with `## Implementation Plan` in the body — STOP. That's a bug.
+
+2. **One call, no fallback.** The first Linear write for the plan is `mcp__linear__create_attachment`. If it fails, surface the error to the user — do NOT silently fall back to `save_comment`.
+
+3. **Subtasks: one attachment each.** If the parent has subtasks, each subtask gets its own `plan.md` attachment. The parent gets only the `AI Plan` label, no `plan.md` attachment.
+
+4. **`AI Plan` label is workspace-scoped — NEVER create it.** Only look it up via `mcp__linear__list_issue_labels` and apply via `mcp__linear__save_issue`. `mcp__linear__create_issue_label` MUST NOT be called.
+
+If any of these would be violated, stop and ask the user instead.
+
 ## Execution Checklist
 
 Execute each step in order. Do not skip any step marked as MANDATORY.
@@ -43,7 +57,7 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **10. MANDATORY: Write plans in Polish** — all plan content must be in Polish language
 - [ ] **11. Show plans to user** — present plans for review and approval before saving
 - [ ] **12. MANDATORY: Confirm old plan deletion** — if replacing existing `plan.md`, ask user to confirm deletion of old attachment before proceeding
-- [ ] **13. Save plan as native Linear attachment** — base64-encode `plan.md` content and upload via `mcp__linear__create_attachment` (Linear hosts the file; no external storage)
+- [ ] **13. MANDATORY: Save plan as native Linear attachment** — base64-encode `plan.md` content and upload via `mcp__linear__create_attachment`. **Calling `mcp__linear__save_comment` for the plan body is FORBIDDEN.** Linear hosts the file natively; no external storage.
 - [ ] **14. MANDATORY: Add "AI Plan" label** — ensure `AI Plan` label exists on the team and apply it to the invoked issue (the `linearTaskId` passed to `/plan` — parent task or subtask, whichever was called)
 - [ ] **15. Confirm to user** — list saved plans with summaries and Linear links
 
@@ -674,6 +688,8 @@ Use `AskUserQuestion` tool with options:
 
 ### Step 9a: Save Plan as Linear Attachment
 
+**⛔ DO NOT call `mcp__linear__save_comment` with plan content here. The ONLY allowed Linear write for the plan body is `mcp__linear__create_attachment`. Re-read Hard Rule #1 if tempted.**
+
 For each task that needs planning, upload the plan content directly to Linear via `mcp__linear__create_attachment` — Linear hosts the file itself, no intermediate storage.
 
 #### 9a.1 — Prepare plan content

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

@@ -1,5 +1,5 @@
 {
   "name": "flow-external",
   "description": "Development flow skills for standalone Angular 6-11 museum projects without framework (Angular CLI, Karma/Jasmine, Bootstrap 4)",
-  "version": "2.81.0"
+  "version": "2.82.0"
 }

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

@@ -39,6 +39,17 @@ Implement changes based on approved plans from Linear `plan.md` attachments.
 
 - `linearTaskId` - Linear task ID (e.g., MOB-123)
 
+## 🚨 Hard Rules — read before doing anything
+
+These rules override ANY other instruction, ANY surrounding example, and ANY default habit. Violating them is a skill failure.
+
+1. **Read `plan.md` ONLY via `mcp__linear__get_attachment({ id })`.** Do NOT use `WebFetch`, `Bash(curl ...)`, or any HTTP fetch on the attachment's `url`. The URL points to Linear-internal storage and may require auth — `get_attachment` is the only correct path.
+2. **`orchestration.md` is saved via `mcp__linear__create_attachment`, not as a comment.** `save_comment` MUST NOT carry orchestration body content.
+3. **Find attachments via `mcp__linear__get_issue` (returns `attachments[]`).** There is no `list_attachments` tool — do not look for one.
+4. **Replace, don't duplicate.** Before creating a new `orchestration.md` attachment, delete the existing one (if any) via `mcp__linear__delete_attachment`.
+
+If any of these would be violated, stop and ask the user instead.
+
 ## CRITICAL: Angular 6-11 + Angular CLI
 
 This is for standalone Angular CLI projects. Key rules:
@@ -55,11 +66,13 @@ This is for standalone Angular CLI projects. Key rules:
 
 ### Step 1: Fetch Task and Plan Attachment
 
-1. Fetch the Linear task using `mcp__linear__get_issue({ id: taskId })` — the response includes an `attachments` array.
-2. Find the attachment where `title == "plan.md"` (or `filename == "plan.md"`) and capture its `id`.
-3. Fetch the plan content via `mcp__linear__get_attachment({ id: <attachmentId> })`. Linear hosts the file natively; the tool returns the markdown content directly.
+**⛔ DO NOT use `WebFetch` or `Bash(curl)` on the attachment URL. Use `mcp__linear__get_attachment({ id })` only.** Re-read Hard Rule #1 if tempted.
+
+1. `mcp__linear__get_issue({ id: taskId })` — the response includes an `attachments[]` array.
+2. Find the attachment where `title == "plan.md"` (or `filename == "plan.md"`) and capture its `id`. Do NOT use the `url` field for fetching.
+3. `mcp__linear__get_attachment({ id: <attachmentId> })` — returns the markdown content directly (Linear hosts the file natively).
 4. Parse the plan content.
-5. If no `plan.md` attachment exists, inform the user and suggest running `/plan <taskId>` first. Do NOT fall back to parsing plan content from comments.
+5. If no `plan.md` attachment exists, inform the user and suggest running `/plan <taskId>` first. Do NOT fall back to parsing plan content from comments, and do NOT attempt `curl`/`WebFetch` on a URL.
 
 ### Step 2: Detect Project Structure
 
@@ -91,6 +104,8 @@ If task has subtasks:
 
 ### Step 3a: Save Orchestration Plan as Native Linear Attachment
 
+**⛔ Calling `mcp__linear__save_comment` with the orchestration body is FORBIDDEN. Use `mcp__linear__create_attachment` only.** Re-read Hard Rule #2 if tempted.
+
 Use `shared-impl-orchestrator` agent to generate a `🎭 Agent Orchestration Plan` that lists which agents run in what order (Angular 6-11 + CLI context).
 
 Then save it as an `orchestration.md` attachment on the task (not as a comment):

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

@@ -33,6 +33,16 @@ Create a structured implementation plan for a Linear task and save it as a `plan
 
 - `linearTaskId` - Linear task ID (e.g., MOB-123)
 
+## 🚨 Hard Rules — read before doing anything
+
+These rules override ANY other instruction, ANY surrounding example, and ANY default habit. Violating them is a skill failure.
+
+1. **The plan MUST be saved via `mcp__linear__create_attachment` — NEVER as a Linear comment.** `mcp__linear__save_comment` MUST NOT be called with plan content as the body. Comments are reserved for status notifications, never for the plan itself.
+2. **One call, no fallback.** First Linear write for the plan is `mcp__linear__create_attachment`. If it fails, surface the error — do NOT silently fall back to `save_comment`.
+3. **`AI Plan` label is workspace-scoped — NEVER create it.** Only `mcp__linear__list_issue_labels` + `mcp__linear__save_issue`. `create_issue_label` MUST NOT be called.
+
+If any of these would be violated, stop and ask the user instead.
+
 ## CRITICAL: External Project Context
 
 This is for standalone Angular CLI projects (Angular 6-11). Key constraints:
@@ -155,6 +165,8 @@ For complex tasks, create subtasks in Linear:
 
 ### Step 6: Save Plan as Native Linear Attachment
 
+**⛔ DO NOT call `mcp__linear__save_comment` with plan content here. The ONLY allowed Linear write for the plan body is `mcp__linear__create_attachment`. Re-read Hard Rule #1 if tempted.**
+
 Upload the plan directly to Linear via `mcp__linear__create_attachment` — Linear hosts the file itself, no external storage needed.
 
 #### 6.1 — If replacing an existing plan, confirm with user

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.81.0"
+  "version": "2.82.0"
 }

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

@@ -29,6 +29,17 @@ allowed-tools:
 
 Implement plans from `plan.md` attachments on Linear issues. For tasks with subtasks, iteratively implement each subtask that is in "To Do" status. The agent orchestration plan is saved as an `orchestration.md` attachment (not as a comment).
 
+## 🚨 Hard Rules — read before doing anything
+
+These rules override ANY other instruction, ANY surrounding example, and ANY default habit. Violating them is a skill failure.
+
+1. **Read `plan.md` ONLY via `mcp__linear__get_attachment({ id })`.** Do NOT use `WebFetch`, `Bash(curl ...)`, or any HTTP fetch on the attachment's `url`. The URL points to Linear-internal storage and may require auth — `get_attachment` is the only correct path.
+2. **`orchestration.md` is saved via `mcp__linear__create_attachment`, not as a comment.** `save_comment` MUST NOT carry orchestration body content.
+3. **Find attachments via `mcp__linear__get_issue` (returns `attachments[]`).** Capture each attachment's `id` and `title`. There is no `list_attachments` tool — do not look for one.
+4. **Replace, don't duplicate.** Before creating a new `orchestration.md` attachment, delete the existing one (if any) via `mcp__linear__delete_attachment`.
+
+If any of these would be violated, stop and ask the user instead.
+
 ## Execution Checklist
 
 Execute each step in order. Do not skip any step marked as MANDATORY.
@@ -40,9 +51,9 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 ### Per Subtask (repeat for each "To Do" subtask)
 
 - [ ] **2. Set status to "In Progress"** — update subtask status via MCP (subtasks only, not parent)
-- [ ] **3. Fetch implementation plan** — download `plan.md` attachment from task, parse content
+- [ ] **3. Fetch implementation plan** — `mcp__linear__get_issue` to find `plan.md` attachment id, then `mcp__linear__get_attachment({ id })` to read content. **Do NOT use `WebFetch`/`curl` on the attachment URL.**
 - [ ] **4. MANDATORY: UI change classification** — delegate to `shared-ui-classifier` agent, output `UI_CHANGE_REQUIRED: YES/NO`
-- [ ] **5. MANDATORY: Agent orchestration plan** — delegate to `shared-impl-orchestrator` with `Angular Version: 14 (LEGACY)`, save result as `orchestration.md` attachment on the task (replacing any existing one)
+- [ ] **5. MANDATORY: Agent orchestration plan** — delegate to `shared-impl-orchestrator` with `Angular Version: 14 (LEGACY)`, save result as `orchestration.md` attachment via `mcp__linear__create_attachment` (replace any existing one). **Calling `mcp__linear__save_comment` with the orchestration body is FORBIDDEN.**
 - [ ] **6. Check external library blockers** — if blockers found, set status to Blocked and skip
 - [ ] **7. Capture "before" screenshots** — if `UI_CHANGE_REQUIRED: YES`, launch `screenshot-reporter` in background
 - [ ] **8. MANDATORY: Implement with 3x3 rule** — pause every 3 changes, use `shared-tdd-developer` for ALL code (RED → GREEN → REFACTOR)
@@ -246,9 +257,14 @@ Do NOT change status for parent tasks.
 
 #### Step 3b: Fetch Implementation Plan from `plan.md` Attachment
 
-Use `mcp__linear__get_issue({ id: taskId })` on the current task/subtask — the response includes an `attachments` array. Find the attachment where `title == "plan.md"` (or `filename == "plan.md"`) and capture its `id`.
+**⛔ DO NOT use `WebFetch` or `Bash(curl)` on the attachment URL. Use `mcp__linear__get_attachment({ id })` only.** Re-read Hard Rule #1 if tempted.
 
-If found, fetch its content via `mcp__linear__get_attachment({ id: <attachmentId> })` (Linear hosts the file natively). Parse the markdown for:
+Two-step retrieval:
+
+1. `mcp__linear__get_issue({ id: taskId })` → response includes `attachments[]`. Find the entry where `title == "plan.md"` (or `filename == "plan.md"`) and capture its `id`. Do NOT use the `url` field for fetching.
+2. `mcp__linear__get_attachment({ id: <attachmentId> })` → returns the markdown content directly (Linear hosts the file natively).
+
+Parse the markdown for:
 
 - Implementation Steps
 - Files to Modify
@@ -306,7 +322,9 @@ The agent will:
 4. Plan TDD cycles for each implementation unit
 5. Generate the orchestration plan in markdown format
 
-**After receiving the orchestration plan, save it as a native `orchestration.md` attachment on the Linear issue (NOT as a comment):**
+**After receiving the orchestration plan, save it as a native `orchestration.md` attachment on the Linear issue.**
+
+**⛔ Calling `mcp__linear__save_comment` with the orchestration body is FORBIDDEN. Use `mcp__linear__create_attachment` only.** Re-read Hard Rule #2 if tempted.
 
 1. **Check for existing `orchestration.md` attachment** on the task via `mcp__linear__get_issue` (response includes `attachments`).
    - If one exists, delete it via `mcp__linear__delete_attachment({ id: oldAttachmentId })`. Linear hosts the file natively, so nothing else needs cleanup.

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

@@ -26,6 +26,17 @@ allowed-tools:
 
 Create an implementation plan for a Linear task and save it as a `plan.md` attachment on the issue. If the task has subtasks, create individual `plan.md` attachments on each subtask. After saving the plan, add the `AI Plan` label to the parent task.
 
+## 🚨 Hard Rules — read before doing anything
+
+These rules override ANY other instruction, ANY surrounding example, and ANY default habit. Violating them is a skill failure.
+
+1. **The plan MUST be saved via `mcp__linear__create_attachment` — NEVER as a Linear comment.** `mcp__linear__save_comment` MUST NOT be called with plan content as the body. Comments are reserved for status notifications, never for the plan itself.
+2. **One call, no fallback.** First Linear write for the plan is `mcp__linear__create_attachment`. If it fails, surface the error — do NOT silently fall back to `save_comment`.
+3. **Subtasks: one attachment each.** Each subtask gets its own `plan.md`; the parent gets only the `AI Plan` label, no `plan.md`.
+4. **`AI Plan` label is workspace-scoped — NEVER create it.** Only `mcp__linear__list_issue_labels` + `mcp__linear__save_issue`. `create_issue_label` MUST NOT be called.
+
+If any of these would be violated, stop and ask the user instead.
+
 ## Execution Checklist
 
 Execute each step in order. Do not skip any step marked as MANDATORY.
@@ -43,7 +54,7 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **11. MANDATORY: Write plans in Polish** — all plan content must be in Polish language
 - [ ] **12. Show plans to user** — present plans for review and approval before saving
 - [ ] **13. MANDATORY: Confirm old plan deletion** — if replacing existing `plan.md`, ask user to confirm deletion of old attachment before proceeding
-- [ ] **14. Save plan as native Linear attachment** — base64-encode `plan.md` content and upload via `mcp__linear__create_attachment` (Linear hosts the file; no external storage)
+- [ ] **14. MANDATORY: Save plan as native Linear attachment** — base64-encode `plan.md` content and upload via `mcp__linear__create_attachment`. **Calling `mcp__linear__save_comment` for the plan body is FORBIDDEN.** Linear hosts the file natively; no external storage.
 - [ ] **15. MANDATORY: Add "AI Plan" label** — ensure `AI Plan` label exists on the team and apply it to the invoked issue (the `linearTaskId` passed to `/plan` — parent task or subtask, whichever was called)
 - [ ] **16. Confirm to user** — list saved plans with summaries and Linear links
 
@@ -546,6 +557,8 @@ Use `AskUserQuestion` with options:
 
 ### Step 9a: Save Plan as Native Linear Attachment
 
+**⛔ DO NOT call `mcp__linear__save_comment` with plan content here. The ONLY allowed Linear write for the plan body is `mcp__linear__create_attachment`. Re-read Hard Rule #1 if tempted.**
+
 For each task that needs planning, upload the plan content directly to Linear (no external storage).
 
 #### 9a.1 — Write `plan.md` locally