@smartsoft001-mobilems/claude-plugins 2.79.0 → 2.81.0

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

@@ -1,6 +1,6 @@
 ---
 name: impl
-description: Implement plans from Linear task comments. Reads approved implementation plan, orchestrates agents, and executes changes step by step.
+description: Implement plans from `plan.md` attachments on Linear issues. Reads approved plan attachment, orchestrates agents (saving `orchestration.md` attachment), and executes changes step by step.
 allowed-tools:
   - Bash
   - Read
@@ -9,12 +9,15 @@ allowed-tools:
   - Glob
   - Grep
   - AskUserQuestion
-  - mcp__linear-server__get_issue
-  - mcp__linear-server__list_issues
-  - mcp__linear-server__list_comments
-  - mcp__linear-server__create_comment
-  - mcp__linear-server__update_issue
-  - mcp__linear-server__list_issue_statuses
+  - mcp__linear__get_issue
+  - mcp__linear__list_issues
+  - mcp__linear__list_comments
+  - mcp__linear__save_comment
+  - mcp__linear__save_issue
+  - mcp__linear__list_issue_statuses
+  - mcp__linear__create_attachment
+  - mcp__linear__get_attachment
+  - mcp__linear__delete_attachment
   - mcp__playwright__browser_navigate
   - mcp__playwright__browser_snapshot
   - mcp__playwright__browser_take_screenshot
@@ -24,7 +27,7 @@ allowed-tools:
 
 # Implementation Skill
 
-Implement changes based on approved plans from Linear task comments.
+Implement changes based on approved plans from Linear `plan.md` attachments.
 
 ## Usage
 
@@ -50,12 +53,13 @@ This is for standalone Angular CLI projects. Key rules:
 
 ## Execution Steps
 
-### Step 1: Fetch Task and Plan
+### Step 1: Fetch Task and Plan Attachment
 
-1. Fetch the Linear task using `mcp__linear-server__get_issue`
-2. Fetch task comments using `mcp__linear-server__list_comments`
-3. Search comments for an approved implementation plan (look for "## Plan" or "## Implementation Plan")
-4. If no plan found, inform user and suggest running `/plan` first
+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.
+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.
 
 ### Step 2: Detect Project Structure
 
@@ -70,6 +74,7 @@ cat package.json 2>/dev/null || cat app/package.json 2>/dev/null
 ```
 
 Key things to detect:
+
 - Angular version (6-11)
 - CSS framework (Bootstrap 4 / custom SCSS / none)
 - NgRx version and patterns
@@ -80,10 +85,28 @@ Key things to detect:
 
 If task has subtasks:
 
-1. Fetch subtasks using `mcp__linear-server__list_issues` with parent filter
+1. Fetch subtasks using `mcp__linear__list_issues` with parent filter
 2. Sort by priority/creation order
 3. Process each subtask in order
 
+### Step 3a: Save Orchestration Plan as Native Linear Attachment
+
+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):
+
+1. **Replace existing orchestration**: use `mcp__linear__get_issue` to list attachments; if one titled `orchestration.md` exists, delete it via `mcp__linear__delete_attachment({ id: oldAttachmentId })`. Linear hosts the file natively, so nothing else needs cleanup.
+2. **Write locally**: `Write` the orchestration markdown to `/tmp/claude-plans/<taskId>-orchestration.md`.
+3. **Base64-encode**: `b64=$(base64 -i /tmp/claude-plans/<taskId>-orchestration.md)`.
+4. **Create Linear attachment** via `mcp__linear__create_attachment`:
+   - `issue`: the task ID
+   - `filename`: `orchestration.md`
+   - `contentType`: `text/markdown`
+   - `title`: `orchestration.md` (exact)
+   - `subtitle`: `Plan orkiestracji wygenerowany przez Claude Code (external)`
+   - `base64Content`: the base64 string from step 3
+5. **Clean up** local `/tmp/claude-plans/<taskId>-orchestration.md` file after the attachment is created.
+
 ### Step 4: Implement Each Step
 
 For each step in the plan:
@@ -114,16 +137,16 @@ Create a summary comment on the Linear task:
 
 ### Zrealizowane
 
-| Podzadanie | Tytul | Status |
-|-----------|-------|--------|
-| MOB-549 | [title] | Zrealizowane |
+| Podzadanie | Tytul   | Status       |
+| ---------- | ------- | ------------ |
+| MOB-549    | [title] | Zrealizowane |
 
 ### Zmiany
 
-| Plik | Typ | Opis |
-|------|-----|------|
-| `src/app/components/feature.component.ts` | Nowy | Komponent |
-| `src/app/components/feature.module.ts` | Zmodyfikowany | Dodano deklaracje |
+| Plik                                      | Typ           | Opis              |
+| ----------------------------------------- | ------------- | ----------------- |
+| `src/app/components/feature.component.ts` | Nowy          | Komponent         |
+| `src/app/components/feature.module.ts`    | Zmodyfikowany | Dodano deklaracje |
 
 ### Build
 
@@ -136,15 +159,15 @@ _Raport wygenerowany przez Claude Code_
 
 ## Agent Selection
 
-| Task Type | Agent |
-|-----------|-------|
-| New component | `angular-component-scaffolder` |
-| New service | `angular-service-builder` |
-| NgRx state | `angular-state-builder` |
-| New directive | `angular-directive-builder` |
-| New pipe | `angular-pipe-builder` |
+| Task Type      | Agent                                                |
+| -------------- | ---------------------------------------------------- |
+| New component  | `angular-component-scaffolder`                       |
+| New service    | `angular-service-builder`                            |
+| NgRx state     | `angular-state-builder`                              |
+| New directive  | `angular-directive-builder`                          |
+| New pipe       | `angular-pipe-builder`                               |
 | Guard/resolver | `angular-guard-builder` / `angular-resolver-builder` |
-| Styling | `ui-web-designer` |
+| Styling        | `ui-web-designer`                                    |
 
 ## Guidelines
 

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

@@ -1,7 +1,7 @@
 ---
 name: linear-suggestion
 description: Create a Linear issue in the "MobileMS Framework" project with a suggestion for agent or skill improvements.
-allowed-tools: mcp__linear-server__create_issue
+allowed-tools: mcp__linear__save_issue
 ---
 
 # Linear Suggestion
@@ -16,13 +16,13 @@ Create a Linear issue in the **MobileMS Framework** project containing a suggest
 
 ## Input Parameters
 
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| `title` | YES | Short summary (max 100 chars) |
-| `description` | YES | Full markdown description with rationale |
-| `source` | YES | Agent that generated the suggestion |
-| `targetFile` | NO | Path to the file to be modified |
-| `category` | NO | One of: `OPTIMIZATION`, `NEW_RULE`, `PATTERN_UPDATE`, `BUG_FIX` |
+| Parameter     | Required | Description                                                     |
+| ------------- | -------- | --------------------------------------------------------------- |
+| `title`       | YES      | Short summary (max 100 chars)                                   |
+| `description` | YES      | Full markdown description with rationale                        |
+| `source`      | YES      | Agent that generated the suggestion                             |
+| `targetFile`  | NO       | Path to the file to be modified                                 |
+| `category`    | NO       | One of: `OPTIMIZATION`, `NEW_RULE`, `PATTERN_UPDATE`, `BUG_FIX` |
 
 ## Issue Format
 

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

@@ -1,23 +1,27 @@
 ---
 name: plan
-description: Create implementation plan and save to Linear. Analyzes codebase, understands task requirements, and generates structured plan.
+description: Create implementation plan and save it as a `plan.md` attachment on the Linear issue. Analyzes codebase, understands task requirements, and generates structured plan.
 allowed-tools:
   - Bash
   - Read
+  - Write
   - Glob
   - Grep
   - AskUserQuestion
-  - mcp__linear-server__get_issue
-  - mcp__linear-server__list_issues
-  - mcp__linear-server__list_comments
-  - mcp__linear-server__create_comment
-  - mcp__linear-server__create_issue
-  - mcp__linear-server__update_issue
+  - mcp__linear__get_issue
+  - mcp__linear__list_issues
+  - mcp__linear__list_comments
+  - mcp__linear__save_comment
+  - mcp__linear__save_issue
+  - mcp__linear__save_issue
+  - mcp__linear__create_attachment
+  - mcp__linear__delete_attachment
+  - mcp__linear__list_issue_labels
 ---
 
 # Plan Skill
 
-Create a structured implementation plan for a Linear task and save it as a comment.
+Create a structured implementation plan for a Linear task and save it as a `plan.md` attachment on the issue. After saving, add the `AI Plan` label to the task.
 
 ## Usage
 
@@ -41,11 +45,21 @@ This is for standalone Angular CLI projects (Angular 6-11). Key constraints:
 
 ## Execution Steps
 
-### Step 1: Fetch Task Details
+### Step 1: Fetch Task Details, Attachments and Comments
 
-1. Fetch the Linear task using `mcp__linear-server__get_issue`
-2. Read task title, description, and any attachments
-3. Fetch existing comments for context
+1. Fetch the Linear task using `mcp__linear__get_issue`.
+2. Fetch task attachments with `mcp__linear__get_issue` (attachments included in response). Look for one titled exactly `plan.md`.
+3. Fetch comments with `mcp__linear__list_comments` — keep `id`, `createdAt`, body.
+
+#### Regeneration decision (mtime rule)
+
+- If no `plan.md` attachment exists → generate a new plan.
+- If `plan.md` exists AND at least one comment's `createdAt` is greater than `plan.md.updatedAt` (fall back to `createdAt`) → regenerate (the comment is treated as feedback on the plan).
+- Otherwise skip — the plan is still fresh.
+
+Secondary signal: if `plan.md` is fresh but the user's latest prompt uses plan-change keywords ("zmień plan", "zaktualizuj plan", "popraw plan", etc.), ask explicitly before regenerating.
+
+When regenerating, record the old `plan.md` attachment ID so it can be deleted via `mcp__linear__delete_attachment` before the new one is created.
 
 ### Step 2: Analyze Codebase
 
@@ -71,6 +85,7 @@ ls -la src/app/ 2>/dev/null || ls -la app/src/app/ 2>/dev/null
 ### Step 3: Identify Affected Areas
 
 Based on the task:
+
 1. Find relevant existing files
 2. Identify what needs to be created vs modified
 3. Check for existing patterns to follow
@@ -101,14 +116,15 @@ Structure the plan as follows:
 
 **Pliki do zmiany:**
 
-| Plik | Akcja | Opis |
-|------|-------|------|
-| `src/app/components/feature.component.ts` | Nowy | Komponent widoku |
-| `src/app/components/feature.component.html` | Nowy | Szablon |
-| `src/app/components/feature.component.scss` | Nowy | Style |
-| `src/app/feature.module.ts` | Modyfikacja | Dodanie deklaracji |
+| Plik                                        | Akcja       | Opis               |
+| ------------------------------------------- | ----------- | ------------------ |
+| `src/app/components/feature.component.ts`   | Nowy        | Komponent widoku   |
+| `src/app/components/feature.component.html` | Nowy        | Szablon            |
+| `src/app/components/feature.component.scss` | Nowy        | Style              |
+| `src/app/feature.module.ts`                 | Modyfikacja | Dodanie deklaracji |
 
 **Wzorce:**
+
 - Constructor DI
 - *ngIf/*ngFor
 - [CSS approach from project]
@@ -124,40 +140,90 @@ Structure the plan as follows:
 
 ### Podzadania
 
-| ID | Tytul | Priorytet | Krok |
-|----|-------|-----------|------|
-| - | [Subtask 1] | High | 1 |
-| - | [Subtask 2] | Medium | 2 |
+| ID  | Tytul       | Priorytet | Krok |
+| --- | ----------- | --------- | ---- |
+| -   | [Subtask 1] | High      | 1    |
+| -   | [Subtask 2] | Medium    | 2    |
 ```
 
 ### Step 5: Create Subtasks (if needed)
 
 For complex tasks, create subtasks in Linear:
-- Use `mcp__linear-server__create_issue` with parent task ID
+
+- Use `mcp__linear__save_issue` with parent task ID
 - Each subtask should map to a plan step
 
-### Step 6: Post Plan as Comment
+### Step 6: Save Plan as Native Linear Attachment
+
+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
+
+If a `plan.md` attachment is being replaced, ask the user via `AskUserQuestion`:
+
+- "Tak, usuń stary plan i zapisz nowy" (Recommended)
+- "Anuluj"
+
+If confirmed, delete the Linear attachment via `mcp__linear__delete_attachment({ id: oldAttachmentId })`.
+
+#### 6.2 — Write `plan.md` locally
+
+```bash
+mkdir -p /tmp/claude-plans
+```
+
+Use `Write` to save the plan content to `/tmp/claude-plans/<taskId>-plan.md`.
+
+#### 6.3 — Base64-encode
+
+```bash
+b64=$(base64 -i /tmp/claude-plans/<taskId>-plan.md)
+```
+
+#### 6.4 — Create Linear attachment
+
+Call `mcp__linear__create_attachment` with:
+
+- `issue`: the task ID
+- `filename`: `plan.md`
+- `contentType`: `text/markdown`
+- `title`: `plan.md` (exact — required for detection)
+- `subtitle`: `Plan wygenerowany przez Claude Code (external)`
+- `base64Content`: the base64 string from 6.3
+
+#### 6.5 — Clean up local file
+
+Delete `/tmp/claude-plans/<taskId>-plan.md` after the attachment is created. `/push` leaves the Linear attachment in place.
+
+### Step 7: Add "AI Plan" Label
+
+**`AI Plan` is a workspace-level (organization-wide) label that already exists** — do NOT create it.
 
-Post the plan as a comment on the Linear task using `mcp__linear-server__create_comment`.
+1. Look up the `AI Plan` label via `mcp__linear__list_issue_labels` (workspace-wide). If not found, surface the error — do NOT create a team-scoped duplicate.
+2. Apply via `mcp__linear__save_issue({ id: taskId, labelIds: [...existingLabelIds, aiPlanLabelId] })`. Preserve existing labels; skip if already present.
+3. If label operations fail, surface the error but do not roll back the plan attachment.
 
-### Step 7: Ask for Approval
+### Step 8: Confirm to User
 
 ```markdown
 ## Plan zapisany
 
-Plan implementacji zostal dodany jako komentarz do zadania [linearTaskId].
+Plan implementacji został dodany jako załącznik `plan.md` do zadania [linearTaskId].
+Etykieta `AI Plan` została dodana.
 
-Czy plan jest zaakceptowany? Po akceptacji uruchom `/impl [linearTaskId]` aby rozpoczac implementacje.
+Czy plan jest zaakceptowany? Po akceptacji uruchom `/impl [linearTaskId]` aby rozpocząć implementację.
 ```
 
 ## Guidelines
 
 1. **Always analyze existing code first** before planning
 2. **Follow existing project patterns** - don't introduce new patterns
-3. **Write plan in Polish** for Linear comments
+3. **Write plan in Polish** (content inside the `plan.md` attachment)
 4. **Keep steps small and focused** - one logical change per step
 5. **Don't plan tests** unless explicitly requested in the task
 6. **Don't plan deployment** steps
 7. **Identify the CSS approach** before planning UI changes
 8. **Include build verification** as the final step (`ng build --prod`)
 9. **Use Angular CLI commands** not Nx commands
+10. **Mtime rule is authoritative**: only regenerate `plan.md` when the attachment is missing or a comment is newer than `plan.md.updatedAt`. Keyword detection triggers an explicit user confirmation only.
+11. **Always add "AI Plan" label** after saving the `plan.md` attachment. The label is workspace-level and pre-configured organization-wide — do NOT create a team-scoped duplicate.

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

@@ -7,12 +7,12 @@ allowed-tools:
   - Glob
   - Grep
   - AskUserQuestion
-  - mcp__linear-server__get_issue
-  - mcp__linear-server__list_issues
-  - mcp__linear-server__list_comments
-  - mcp__linear-server__create_comment
-  - mcp__linear-server__update_issue
-  - mcp__linear-server__list_issue_statuses
+  - mcp__linear__get_issue
+  - mcp__linear__list_issues
+  - mcp__linear__list_comments
+  - mcp__linear__save_comment
+  - mcp__linear__save_issue
+  - mcp__linear__list_issue_statuses
 ---
 
 # Push Skill
@@ -39,6 +39,7 @@ git log origin/$(git branch --show-current)..HEAD --oneline
 ```
 
 Check for:
+
 - Uncommitted changes (warn user)
 - Commits ahead of remote (list them)
 - Current branch name
@@ -46,12 +47,14 @@ Check for:
 ### Step 2: Detect Linear Task
 
 If `linearTaskId` not provided, try to extract from branch name:
+
 - Branch `MOB-123` → task `MOB-123`
 - Branch `feature/MOB-123-description` → task `MOB-123`
 
 ### Step 3: Fetch Task Details
 
 If Linear task ID is available:
+
 1. Fetch parent task details
 2. Fetch subtasks if any
 3. Analyze completion status
@@ -66,14 +69,15 @@ If Linear task ID is available:
 
 ### Commits
 
-| Hash | Message |
-|------|---------|
-| abc1234 | feat(gallery): add lightbox |
+| Hash    | Message                        |
+| ------- | ------------------------------ |
+| abc1234 | feat(gallery): add lightbox    |
 | def5678 | fix(gallery): fix image sizing |
 
 ### Linear Task: [ID] - [Title]
 
 **Subtasks**:
+
 - [x] MOB-549: Completed subtask
 - [x] MOB-550: Another completed
 - [ ] MOB-551: Incomplete (reason)
@@ -86,12 +90,14 @@ Do you want to push and update Linear status to "In Review"?
 ```
 
 Use `AskUserQuestion` with options:
+
 - "Tak, push i zaktualizuj status"
 - "Nie, anuluj"
 
 ### Step 6: Update Linear Status
 
 If confirmed:
+
 1. Update parent task status to "In Review"
 2. Update completed subtasks to "In Review"
 3. Create summary comment on parent task (in Polish):
@@ -101,21 +107,21 @@ If confirmed:
 
 ### Zrealizowane Podzadania
 
-| Podzadanie | Tytul | Status |
-|-----------|-------|--------|
-| MOB-549 | [title] | Zrealizowane |
-| MOB-550 | [title] | Zrealizowane |
+| Podzadanie | Tytul   | Status       |
+| ---------- | ------- | ------------ |
+| MOB-549    | [title] | Zrealizowane |
+| MOB-550    | [title] | Zrealizowane |
 
 ### Niezrealizowane Podzadania
 
-| Podzadanie | Tytul | Powod |
-|-----------|-------|-------|
-| MOB-551 | [title] | [reason] |
+| Podzadanie | Tytul   | Powod    |
+| ---------- | ------- | -------- |
+| MOB-551    | [title] | [reason] |
 
 ### Commity
 
-| Commit | Opis |
-|--------|------|
+| Commit  | Opis                        |
+| ------- | --------------------------- |
 | abc1234 | feat(gallery): add lightbox |
 
 ### Status
@@ -140,11 +146,13 @@ git push
 If on a feature branch (not `development` or `main`):
 
 1. Check if PR exists:
+
    ```bash
    gh pr list --head <branch-name> --base development --json number,title,state,url
    ```
 
 2. If no PR, ask user:
+
    ```markdown
    ## Create Pull Request?
 
@@ -178,6 +186,7 @@ Zmiany wyslane do `origin/<branch-name>`
 ## Push Failed
 
 Updates were rejected. Options:
+
 1. `git pull --rebase` then push again
 2. `git pull` and merge
 ```

package/plugins/flow-legacy/.claude-plugin/README.md

@@ -57,7 +57,7 @@ Or manually copy permissions from `settings.template.json` to your project's `.c
 
 Configure these in your `.mcp.json`:
 
-- `linear-server` - Linear API integration
+- `linear` - Linear API integration (MCP prefix `mcp__linear__`)
 - `playwright` - Browser automation for screenshots
 
 ## Permission Strategy

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.79.0"
+  "version": "2.81.0"
 }

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

@@ -34,14 +34,17 @@
       "Bash(for:*)",
       "Bash(node:*)",
       "Bash(mkdir:*)",
-      "mcp__linear-server__get_issue",
-      "mcp__linear-server__list_issues",
-      "mcp__linear-server__list_comments",
-      "mcp__linear-server__create_comment",
-      "mcp__linear-server__delete_comment",
-      "mcp__linear-server__update_issue",
-      "mcp__linear-server__list_issue_statuses",
-      "mcp__linear-server__create_issue",
+      "mcp__linear__get_issue",
+      "mcp__linear__list_issues",
+      "mcp__linear__list_comments",
+      "mcp__linear__save_comment",
+      "mcp__linear__delete_comment",
+      "mcp__linear__save_issue",
+      "mcp__linear__list_issue_statuses",
+      "mcp__linear__create_attachment",
+      "mcp__linear__get_attachment",
+      "mcp__linear__delete_attachment",
+      "mcp__linear__list_issue_labels",
       "mcp__playwright__browser_snapshot",
       "mcp__playwright__browser_take_screenshot",
       "mcp__playwright__browser_navigate",

package/plugins/flow-legacy/agents/shared-impl-orchestrator.md

@@ -158,11 +158,13 @@ _Orchestration plan generated by flow-legacy_
 
 ## Output
 
-Return the orchestration plan in the format above. The plan will be:
+Return the orchestration plan as a complete, standalone markdown document. The plan will be:
 
-1. Posted as a comment on the Linear task
+1. Saved as an `orchestration.md` attachment on the Linear task (not posted as a comment)
 2. Used to guide implementation
 
+Avoid comment-thread framing (greetings, replies); the document must read as a standalone file.
+
 ## Checklist
 
 - [ ] All Angular agents are legacy-compatible

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

@@ -11,8 +11,8 @@ allowed-tools:
   - TaskUpdate
   - TaskList
   - TaskGet
-  - mcp__linear-server__get_issue
-  - mcp__linear-server__list_comments
+  - mcp__linear__get_issue
+  - mcp__linear__list_comments
 ---
 
 # Commit Skill