@smartsoft001-mobilems/claude-plugins 2.81.0 → 2.83.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smartsoft001-mobilems/claude-plugins",
-  "version": "2.81.0",
+  "version": "2.83.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.83.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,12 +54,12 @@ 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)
+- [ ] **8. MANDATORY: Implement with 3x3 rule** — pause every 3 changes (skip pause in `--auto`, log checkpoint as Linear comment instead), use `shared-tdd-developer` for ALL code (RED → GREEN → REFACTOR)
 - [ ] **9. Verify implementation** — run tests, lint, build check
 - [ ] **9.5. E2E tests (conditional)** — if `E2E_TESTS_RECOMMENDED: YES`, delegate to `test-e2e` skill
 - [ ] **10. Capture "after" screenshots** — if `UI_CHANGE_REQUIRED: YES`, capture + post comparison to Linear + cleanup
@@ -54,13 +68,13 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **13. MANDATORY: Write reports in Polish** — all Linear comments must be in Polish language
 - [ ] **14. Update status** — delegate to `shared-linear-subtask-iterator` for status determination
 - [ ] **15. Agent evolution** — if user confirmed feedback, delegate to `shared-agent-evolver`
-- [ ] **16. Pause for user confirmation** — ALWAYS wait before proceeding to next subtask
+- [ ] **16. Pause for user confirmation** — wait before proceeding to next subtask (skipped in `--auto`; post completion comment and continue)
 
 ### Finalization
 
 - [ ] **17. Final summary** — present summary of all subtasks with statuses
 - [ ] **18. Session-wide evolution** — analyze all feedback across session
-- [ ] **19. ALWAYS pause** — wait for user confirmation at end
+- [ ] **19. ALWAYS pause** — wait for user confirmation at end (skipped in `--auto`; post final summary comment and exit)
 
 ### Task Progress Tracking
 
@@ -137,12 +151,31 @@ You implement code that is:
 ```
 /impl [linearTaskId]
 /impl [linearTaskId] --team    # Agent Team mode (experimental)
+/impl [linearTaskId] --auto    # Non-interactive mode for CI / GitHub Actions
 ```
 
 ## Parameters
 
 - `linearTaskId` - Linear task ID (e.g., ENG-123)
 - `--team` - Enable parallel Implementation Squad mode (experimental, requires `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`)
+- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts, 3x3 checkpoint pauses, per-subtask pauses, and the final end pause. If `plan.md` attachment is missing, auto-invoke `/plan` flow to generate it instead of posting a "run /plan first" comment and skipping. Designed for CI / GitHub Actions runs where no human is at the keyboard.
+
+## Auto Mode (`--auto`)
+
+**When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts.** Apply these overrides:
+
+| Default behavior                                         | `--auto` override                                                                                         |
+| -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
+| Post comment "no plan.md found, run /plan first" + skip  | Inline-invoke `/plan` flow for the task to generate `plan.md` attachment + `AI Plan` label, then continue |
+| 3x3 rule pauses every 3 changes asking "Continue?"       | Log the checkpoint summary as a status comment, then continue automatically                               |
+| Pause after each subtask waiting for user confirmation   | Post subtask completion comment, then proceed to next subtask                                             |
+| Final end pause "wait for user confirmation"             | Post final summary comment and exit cleanly                                                               |
+| `AskUserQuestion` for any decision                       | Use the option marked **(Recommended)**; if none, fail fast with a Linear comment explaining why          |
+| Confirmation before destructive ops (delete attachments) | Proceed without confirmation — replace old `orchestration.md` automatically                               |
+
+**Hard requirement in `--auto`**: every checkpoint, decision, or skip MUST be logged as a Linear comment in Polish so the run remains auditable after the fact. Comments replace the interactive prompts — they are the audit trail.
+
+**Detection**: The flag `--auto` is provided as a positional/named arg. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent. Combinable with `--team` (parallel squad mode runs without per-subtask approval).
 
 ## Instructions
 
@@ -275,9 +308,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:
+
+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).
 
-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:
+Parse the markdown for:
 
 - Implementation Steps
 - Files to Modify
@@ -285,7 +323,12 @@ If found, fetch its content via `mcp__linear__get_attachment({ id: <attachmentId
 - Testing Strategy
 - External Library Changes (if any — these are blockers, not to be implemented)
 
-**If no `plan.md` attachment found**: Create a comment noting that no plan was found, suggest running `/plan <taskId>` first, and skip this task. Set status back to "To Do". Do NOT fall back to reading plan content from comments — the attachment is the source of truth.
+**If no `plan.md` attachment found**:
+
+- **Default mode**: Create a comment noting that no plan was found, suggest running `/plan <taskId>` first, and skip this task. Set status back to "To Do".
+- **`--auto` mode**: Inline-invoke the `/plan` skill flow for this task to generate `plan.md` attachment + `AI Plan` label, then proceed with implementation. Post a comment in Polish noting the plan was auto-generated. Do NOT skip the task.
+
+Do NOT fall back to reading plan content from comments — the attachment is the source of truth.
 
 #### Step 3b-classify: MANDATORY UI Change Classification
 
@@ -334,7 +377,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.
@@ -696,7 +741,10 @@ The agent will provide:
 - Next subtask details (if any)
 - Pause point for user confirmation
 
-**IMPORTANT**: ALWAYS wait for user confirmation before proceeding to next subtask.
+**IMPORTANT**:
+
+- **Default mode**: ALWAYS wait for user confirmation before proceeding to next subtask.
+- **`--auto` mode**: Skip the wait. The completion comment from Step 3f is the audit trail; proceed directly to Step 3i.
 
 #### Step 3i: Move to Next Subtask
 
@@ -718,7 +766,10 @@ When all subtasks are processed, the agent will return `🏁 Iteration Complete`
 - Statistics (completed, partial, blocked)
 - Recommendations for follow-up
 
-**IMPORTANT**: ALWAYS pause and present the final summary to the user.
+**IMPORTANT**:
+
+- **Default mode**: ALWAYS pause and present the final summary to the user.
+- **`--auto` mode**: Post the final summary as a Linear comment in Polish on the parent task (or invoked task) and exit cleanly without pausing.
 
 ### Step 4a: Session-Wide Agent Evolution
 
@@ -767,18 +818,18 @@ To Do → In Progress → In Review (if completed)
 
 ## Pause Points (3x3 Rule)
 
-**ALWAYS stop and wait for user confirmation at these points:**
+**ALWAYS stop and wait for user confirmation at these points** (skipped in `--auto` — see overrides):
 
-| Pause Point          | When                                | What to Show                              |
-| -------------------- | ----------------------------------- | ----------------------------------------- |
-| **3x3 Checkpoint**   | After every 3 changes               | Summary of 3 changes + next 3 steps       |
-| **Subtask Complete** | After finishing each subtask        | Subtask summary + next subtask info       |
-| **Task Complete**    | After finishing all subtasks        | Final summary with all results            |
-| **Blocker Found**    | When external dependency found      | Blocker details + options                 |
-| **Error/Issue**      | When unexpected problem occurs      | Error details + proposed solution         |
-| **Agent Evolution**  | After subtask / after final summary | Evolution report with filed Linear issues |
+| Pause Point          | When                                | What to Show                              | `--auto` behavior                                             |
+| -------------------- | ----------------------------------- | ----------------------------------------- | ------------------------------------------------------------- |
+| **3x3 Checkpoint**   | After every 3 changes               | Summary of 3 changes + next 3 steps       | Post checkpoint as Linear comment, continue                   |
+| **Subtask Complete** | After finishing each subtask        | Subtask summary + next subtask info       | Post completion comment, continue to next subtask             |
+| **Task Complete**    | After finishing all subtasks        | Final summary with all results            | Post final summary comment, exit                              |
+| **Blocker Found**    | When external dependency found      | Blocker details + options                 | Set status to Blocked, post blocker comment, skip subtask     |
+| **Error/Issue**      | When unexpected problem occurs      | Error details + proposed solution         | Post error comment to Linear, fail the run with non-zero exit |
+| **Agent Evolution**  | After subtask / after final summary | Evolution report with filed Linear issues | Skip evolution prompt, file issues silently if any            |
 
-**Never proceed automatically** - always wait for explicit user confirmation before:
+**In default mode, never proceed automatically** - always wait for explicit user confirmation before:
 
 - Continuing after 3x3 checkpoint
 - Moving to next subtask

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.
@@ -41,9 +55,9 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **8. Analyze external library deps** — check if `@smartsoft001` or `@smartsoft001-mobilems` changes are needed (mark as separate process)
 - [ ] **9. Create implementation plans** — generate structured plans per task/subtask with all required sections
 - [ ] **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)
+- [ ] **11. Show plans to user** — present plans for review and approval before saving (skipped in `--auto`; proceed directly to save)
+- [ ] **12. MANDATORY: Confirm old plan deletion** — if replacing existing `plan.md`, ask user to confirm deletion of old attachment before proceeding (skipped in `--auto`; delete old attachment automatically)
+- [ ] **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
 
@@ -103,12 +117,30 @@ You create plans that are:
 ```
 /plan [linearTaskId]
 /plan [linearTaskId] --deep    # Deep planning with Agent Team (experimental)
+/plan [linearTaskId] --auto    # Non-interactive mode for CI / GitHub Actions
 ```
 
 ## Parameters
 
 - `linearTaskId` - Linear task ID (e.g., ENG-123)
 - `--deep` - Enable deep planning with Agent Team (experimental, requires `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`)
+- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts. Auto-approve plans before saving (no review step), auto-delete stale `plan.md` attachments without confirmation, and silently skip when all plans are up to date (no "regenerate anyway?" prompt). Designed for CI / GitHub Actions runs where no human is at the keyboard.
+
+## Auto Mode (`--auto`)
+
+**When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts.** Apply these overrides:
+
+| Default behavior                                                  | `--auto` override                                                                                |
+| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
+| Show plans to user for review/approval before saving              | Skip the review step; proceed directly to attachment save                                        |
+| Ask user to confirm deletion of old `plan.md` attachments         | Delete old attachments automatically before saving new ones                                      |
+| Ask "regenerate anyway?" when all plans are up-to-date            | Exit cleanly with a Linear comment noting all plans are current; no regeneration                 |
+| Secondary signal prompt (keyword-triggered confirmation to regen) | Ignore the secondary signal; only the mtime rule decides regeneration                            |
+| `AskUserQuestion` for any decision                                | Use the option marked **(Recommended)**; if none, fail fast with a Linear comment explaining why |
+
+**Hard requirement in `--auto`**: every decision (save, replace, skip) MUST be logged as a Linear comment in Polish so the run remains auditable after the fact. The mtime rule remains authoritative — `--auto` does not change *what* gets regenerated, only that no human is asked.
+
+**Detection**: The flag `--auto` is provided as a positional/named arg. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent. Combinable with `--deep` (deep team mode runs without the final approval prompt).
 
 ## Instructions
 
@@ -181,7 +213,10 @@ Create a list of tasks/subtasks that need planning:
 - `tasksWithExistingPlan`: Array of task IDs with valid, up-to-date plans (skip these)
 - `oldPlanAttachments`: Map of task ID → `attachmentId` for plans that will be replaced (needed for deletion in Step 9)
 
-**Important**: If ALL tasks already have up-to-date plans, inform the user and ask if they want to regenerate anyway.
+**Important**: If ALL tasks already have up-to-date plans:
+
+- **Default mode**: Inform the user and ask if they want to regenerate anyway.
+- **`--auto` mode**: Exit cleanly with a Linear comment in Polish noting all plans are current; do NOT regenerate.
 
 ### Step 4: Analyze Previous Commits
 
@@ -644,7 +679,9 @@ When using `--deep` flag and the Planning Team has completed its analysis, appen
 
 **This step applies only when replacing existing plans** (i.e., `oldPlanAttachments` from Step 3a is not empty).
 
-Before saving new plans, ask the user to confirm deletion of old `plan.md` attachments:
+**`--auto` mode**: Skip the confirmation prompt. For each task in `oldPlanAttachments`, delete the Linear attachment via `mcp__linear__delete_attachment({ id: attachmentId })` and proceed directly to Step 9a. Log the deletions in the final summary comment.
+
+**Default mode** (interactive): Before saving new plans, ask the user to confirm deletion of old `plan.md` attachments:
 
 ```markdown
 ## Zastąpienie istniejących planów
@@ -674,6 +711,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
@@ -922,4 +961,9 @@ _Plan generated by Claude Code_
 
 ---
 
-**Important**: Before saving the plans as attachments, show them to the user for review and approval. The plan content is written to `/tmp/claude-plans/<taskId>-plan.md`, base64-encoded, and uploaded as a native Linear attachment via `mcp__linear__create_attachment`. After that, the `AI Plan` label is applied to the invoked issue.
+**Important**:
+
+- **Default mode**: Before saving the plans as attachments, show them to the user for review and approval.
+- **`--auto` mode**: Skip the review step; proceed directly to saving the attachments.
+
+The plan content is written to `/tmp/claude-plans/<taskId>-plan.md`, base64-encoded, and uploaded as a native Linear attachment via `mcp__linear__create_attachment`. After that, the `AI Plan` label is applied to the invoked issue.

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.83.0"
 }

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

@@ -33,11 +33,39 @@ Implement changes based on approved plans from Linear `plan.md` attachments.
 
 ```
 /impl <linearTaskId>
+/impl <linearTaskId> --auto    # Non-interactive mode for CI / GitHub Actions
 ```
 
 ## Parameters
 
 - `linearTaskId` - Linear task ID (e.g., MOB-123)
+- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts and any per-step pauses. If `plan.md` attachment is missing, auto-invoke `/plan` flow to generate it instead of stopping. Designed for CI / GitHub Actions runs where no human is at the keyboard.
+
+## Auto Mode (`--auto`)
+
+When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts:
+
+| Default behavior                                                  | `--auto` override                                                                                         |
+| ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
+| Stop with "no plan.md found, run /plan first" suggestion          | Inline-invoke `/plan` flow for the task to generate `plan.md` attachment + `AI Plan` label, then continue |
+| Pause after each step / subtask waiting for user confirmation     | Post completion comment, then proceed automatically                                                       |
+| Confirmation before destructive ops (delete `orchestration.md`)   | Proceed without confirmation — replace old attachment automatically                                       |
+| Any `AskUserQuestion`                                             | Use the **(Recommended)** option; if none, fail fast with a Linear comment                                |
+
+Every checkpoint, decision, or skip MUST be logged as a Linear comment in Polish (audit trail).
+
+**Detection**: The flag `--auto` is provided as a positional/named arg. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent.
+
+## 🚨 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
 
@@ -55,11 +83,17 @@ 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:
+   - **Default mode**: inform the user and suggest running `/plan <taskId>` first. Stop the skill.
+   - **`--auto` mode**: inline-invoke the `/plan` skill flow for this task to generate `plan.md` attachment + `AI Plan` label, then proceed with implementation. Post a Linear comment in Polish noting the plan was auto-generated.
+
+   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 +125,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

@@ -27,11 +27,38 @@ Create a structured implementation plan for a Linear task and save it as a `plan
 
 ```
 /plan <linearTaskId>
+/plan <linearTaskId> --auto    # Non-interactive mode for CI / GitHub Actions
 ```
 
 ## Parameters
 
 - `linearTaskId` - Linear task ID (e.g., MOB-123)
+- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts. Auto-approve plan before saving, auto-delete stale `plan.md` attachment without confirmation, and silently skip when the existing plan is up to date. Designed for CI / GitHub Actions runs where no human is at the keyboard.
+
+## Auto Mode (`--auto`)
+
+When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts:
+
+| Default behavior                                              | `--auto` override                                                                  |
+| ------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
+| Ask user to confirm deletion of old `plan.md` attachment      | Delete old attachment automatically before saving the new one                      |
+| Ask "regenerate?" when plan is up-to-date but keywords detect | Ignore the secondary signal; only the mtime rule decides regeneration              |
+| Final approval prompt before user runs `/impl`                | Skip the prompt; finish with a Linear comment confirming plan saved                |
+| Any `AskUserQuestion`                                         | Use the **(Recommended)** option; if none, fail fast with a Linear comment         |
+
+Every decision MUST be logged as a Linear comment in Polish (audit trail). The mtime rule remains authoritative.
+
+**Detection**: The flag `--auto` is provided as a positional/named arg. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent.
+
+## 🚨 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
 
@@ -155,16 +182,20 @@ 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
 
-If a `plan.md` attachment is being replaced, ask the user via `AskUserQuestion`:
+If a `plan.md` attachment is being replaced:
 
-- "Tak, usuń stary plan i zapisz nowy" (Recommended)
-- "Anuluj"
+- **Default mode**: 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 })`.
+  If confirmed, delete the Linear attachment via `mcp__linear__delete_attachment({ id: oldAttachmentId })`.
+- **`--auto` mode**: skip the prompt; delete the old Linear attachment via `mcp__linear__delete_attachment({ id: oldAttachmentId })` automatically and proceed.
 
 #### 6.2 — Write `plan.md` locally
 
@@ -205,6 +236,8 @@ Delete `/tmp/claude-plans/<taskId>-plan.md` after the attachment is created. `/p
 
 ### Step 8: Confirm to User
 
+**Default mode**:
+
 ```markdown
 ## Plan zapisany
 
@@ -214,6 +247,8 @@ Etykieta `AI Plan` została dodana.
 Czy plan jest zaakceptowany? Po akceptacji uruchom `/impl [linearTaskId]` aby rozpocząć implementację.
 ```
 
+**`--auto` mode**: post a Linear comment confirming the plan was saved (no question asked) and exit. The comment is the audit trail for the CI run.
+
 ## Guidelines
 
 1. **Always analyze existing code first** before planning

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.83.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,12 +51,12 @@ 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)
+- [ ] **8. MANDATORY: Implement with 3x3 rule** — pause every 3 changes (skip pause in `--auto`, log checkpoint as Linear comment instead), use `shared-tdd-developer` for ALL code (RED → GREEN → REFACTOR)
 - [ ] **9. MANDATORY: Use Angular 14 patterns** — `*ngIf`/`*ngFor`, constructor DI, `@Input()`/`@Output()`, BehaviorSubject — NEVER signals, `@if`/`@for`, `inject()`
 - [ ] **10. Verify implementation** — run tests, lint, build check
 - [ ] **11. Capture "after" screenshots** — if `UI_CHANGE_REQUIRED: YES`, capture + post comparison to Linear + cleanup
@@ -54,12 +65,12 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **14. MANDATORY: Write reports in Polish** — all Linear comments must be in Polish language
 - [ ] **15. Update status** — delegate to `shared-linear-subtask-iterator` for status determination
 - [ ] **16. Agent evolution** — if user confirmed feedback, delegate to `shared-agent-evolver`
-- [ ] **17. Pause for user confirmation** — ALWAYS wait before proceeding to next subtask
+- [ ] **17. Pause for user confirmation** — wait before proceeding to next subtask (skipped in `--auto`; post completion comment and continue)
 
 ### Finalization
 
 - [ ] **18. Final summary** — present summary of all subtasks with statuses
-- [ ] **19. ALWAYS pause** — wait for user confirmation at end
+- [ ] **19. ALWAYS pause** — wait for user confirmation at end (skipped in `--auto`; post final summary comment and exit)
 
 ### Task Progress Tracking
 
@@ -207,11 +218,30 @@ export class DataService {
 
 ```
 /impl [linearTaskId]
+/impl [linearTaskId] --auto    # Non-interactive mode for CI / GitHub Actions
 ```
 
 ## Parameters
 
 - `linearTaskId` - Linear task ID (e.g., ENG-123)
+- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts, 3x3 checkpoint pauses, per-subtask pauses, and the final end pause. If `plan.md` attachment is missing, auto-invoke `/plan` flow to generate it instead of posting a "run /plan first" comment and skipping. Designed for CI / GitHub Actions runs where no human is at the keyboard.
+
+## Auto Mode (`--auto`)
+
+**When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts.** Apply these overrides:
+
+| Default behavior                                         | `--auto` override                                                                                         |
+| -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
+| Post comment "no plan.md found, run /plan first" + skip  | Inline-invoke `/plan` flow for the task to generate `plan.md` attachment + `AI Plan` label, then continue |
+| 3x3 rule pauses every 3 changes asking "Continue?"       | Log the checkpoint summary as a status comment, then continue automatically                               |
+| Pause after each subtask waiting for user confirmation   | Post subtask completion comment, then proceed to next subtask                                             |
+| Final end pause "wait for user confirmation"             | Post final summary comment and exit cleanly                                                               |
+| `AskUserQuestion` for any decision                       | Use the option marked **(Recommended)**; if none, fail fast with a Linear comment explaining why          |
+| Confirmation before destructive ops (delete attachments) | Proceed without confirmation — replace old `orchestration.md` automatically                               |
+
+**Hard requirement in `--auto`**: every checkpoint, decision, or skip MUST be logged as a Linear comment in Polish so the run remains auditable after the fact. Comments replace the interactive prompts — they are the audit trail.
+
+**Detection**: The flag `--auto` is provided as a positional/named arg. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent.
 
 ## Instructions
 
@@ -246,9 +276,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
@@ -256,7 +291,12 @@ If found, fetch its content via `mcp__linear__get_attachment({ id: <attachmentId
 - Testing Strategy
 - External Library Changes (blockers — not to be implemented)
 
-**If no `plan.md` attachment found**: Create a comment noting that no plan was found, suggest running `/plan <taskId>` first, and skip this task. Set status back to "To Do". Do NOT fall back to parsing plan content from comments — the attachment is the source of truth.
+**If no `plan.md` attachment found**:
+
+- **Default mode**: Create a comment noting that no plan was found, suggest running `/plan <taskId>` first, and skip this task. Set status back to "To Do".
+- **`--auto` mode**: Inline-invoke the `/plan` skill flow for this task to generate `plan.md` attachment + `AI Plan` label, then proceed with implementation. Post a comment in Polish noting the plan was auto-generated. Do NOT skip the task.
+
+Do NOT fall back to parsing plan content from comments — the attachment is the source of truth.
 
 #### Step 3b-classify: MANDATORY UI Change Classification
 
@@ -306,7 +346,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.
@@ -589,7 +631,10 @@ The agent will provide:
 - Next subtask details (if any)
 - Pause point for user confirmation
 
-**IMPORTANT**: ALWAYS wait for user confirmation before proceeding to next subtask.
+**IMPORTANT**:
+
+- **Default mode**: ALWAYS wait for user confirmation before proceeding to next subtask.
+- **`--auto` mode**: Skip the wait. The completion comment from Step 3f is the audit trail; proceed directly to Step 3i.
 
 #### Step 3i: Move to Next Subtask
 
@@ -611,7 +656,10 @@ When all subtasks are processed, the agent will return `🏁 Iteration Complete`
 - Statistics (completed, partial, blocked)
 - Recommendations for follow-up
 
-**IMPORTANT**: ALWAYS pause and present the final summary to the user.
+**IMPORTANT**:
+
+- **Default mode**: ALWAYS pause and present the final summary to the user.
+- **`--auto` mode**: Post the final summary as a Linear comment in Polish on the parent task (or invoked task) and exit cleanly without pausing.
 
 ## Status Flow
 
@@ -623,18 +671,18 @@ To Do → In Progress → In Review (if completed)
 
 ## Pause Points (3x3 Rule)
 
-**ALWAYS stop and wait for user confirmation at these points:**
+**ALWAYS stop and wait for user confirmation at these points** (skipped in `--auto` — see overrides):
 
-| Pause Point          | When                                | What to Show                              |
-| -------------------- | ----------------------------------- | ----------------------------------------- |
-| **3x3 Checkpoint**   | After every 3 changes               | Summary of 3 changes + next 3 steps       |
-| **Subtask Complete** | After finishing each subtask        | Subtask summary + next subtask info       |
-| **Task Complete**    | After finishing all subtasks        | Final summary with all results            |
-| **Blocker Found**    | When external dependency found      | Blocker details + options                 |
-| **Error/Issue**      | When unexpected problem occurs      | Error details + proposed solution         |
-| **Agent Evolution**  | After subtask / after final summary | Evolution report with filed Linear issues |
+| Pause Point          | When                                | What to Show                              | `--auto` behavior                                             |
+| -------------------- | ----------------------------------- | ----------------------------------------- | ------------------------------------------------------------- |
+| **3x3 Checkpoint**   | After every 3 changes               | Summary of 3 changes + next 3 steps       | Post checkpoint as Linear comment, continue                   |
+| **Subtask Complete** | After finishing each subtask        | Subtask summary + next subtask info       | Post completion comment, continue to next subtask             |
+| **Task Complete**    | After finishing all subtasks        | Final summary with all results            | Post final summary comment, exit                              |
+| **Blocker Found**    | When external dependency found      | Blocker details + options                 | Set status to Blocked, post blocker comment, skip subtask     |
+| **Error/Issue**      | When unexpected problem occurs      | Error details + proposed solution         | Post error comment to Linear, fail the run with non-zero exit |
+| **Agent Evolution**  | After subtask / after final summary | Evolution report with filed Linear issues | Skip evolution prompt, file issues silently if any            |
 
-**Never proceed automatically** - always wait for explicit user confirmation before:
+**In default mode, never proceed automatically** - always wait for explicit user confirmation before:
 
 - Continuing after 3x3 checkpoint
 - Moving to next subtask

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.
@@ -41,9 +52,9 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
 - [ ] **9. Analyze external library deps** — check if `@smartsoft001` or `@smartsoft001-mobilems` changes are needed (mark as separate process)
 - [ ] **10. Create implementation plans** — generate structured plans per task/subtask with all required sections, using Angular 14 patterns
 - [ ] **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)
+- [ ] **12. Show plans to user** — present plans for review and approval before saving (skipped in `--auto`; proceed directly to save)
+- [ ] **13. MANDATORY: Confirm old plan deletion** — if replacing existing `plan.md`, ask user to confirm deletion of old attachment before proceeding (skipped in `--auto`; delete old attachment automatically)
+- [ ] **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
 
@@ -104,11 +115,29 @@ You create plans that are:
 
 ```
 /plan [linearTaskId]
+/plan [linearTaskId] --auto    # Non-interactive mode for CI / GitHub Actions
 ```
 
 ## Parameters
 
 - `linearTaskId` - Linear task ID (e.g., ENG-123)
+- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts. Auto-approve plans before saving (no review step), auto-delete stale `plan.md` attachments without confirmation, and silently skip when all plans are up to date (no "regenerate anyway?" prompt). Designed for CI / GitHub Actions runs where no human is at the keyboard.
+
+## Auto Mode (`--auto`)
+
+**When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts.** Apply these overrides:
+
+| Default behavior                                                  | `--auto` override                                                                                |
+| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
+| Show plans to user for review/approval before saving              | Skip the review step; proceed directly to attachment save                                        |
+| Ask user to confirm deletion of old `plan.md` attachments         | Delete old attachments automatically before saving new ones                                      |
+| Ask "regenerate anyway?" when all plans are up-to-date            | Exit cleanly with a Linear comment noting all plans are current; no regeneration                 |
+| Secondary signal prompt (keyword-triggered confirmation to regen) | Ignore the secondary signal; only the mtime rule decides regeneration                            |
+| `AskUserQuestion` for any decision                                | Use the option marked **(Recommended)**; if none, fail fast with a Linear comment explaining why |
+
+**Hard requirement in `--auto`**: every decision (save, replace, skip) MUST be logged as a Linear comment in Polish so the run remains auditable after the fact. The mtime rule remains authoritative — `--auto` does not change *what* gets regenerated, only that no human is asked.
+
+**Detection**: The flag `--auto` is provided as a positional/named arg. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent.
 
 ## Angular 14 Legacy Patterns
 
@@ -195,7 +224,10 @@ If `planAttachment` exists and no comment is newer than it, but the user's lates
 - `tasksWithExistingPlan`: Array of task IDs with up-to-date plans
 - `oldPlanAttachments`: Map of task ID → `attachmentId` for plans being replaced
 
-**Important**: If ALL tasks already have up-to-date plans, inform the user and ask if they want to regenerate anyway.
+**Important**: If ALL tasks already have up-to-date plans:
+
+- **Default mode**: Inform the user and ask if they want to regenerate anyway.
+- **`--auto` mode**: Exit cleanly with a Linear comment in Polish noting all plans are current; do NOT regenerate.
 
 ### Step 4: Analyze Previous Commits
 
@@ -518,7 +550,9 @@ _Plan generated by Claude Code (flow-legacy)_
 
 **This step applies only when replacing existing plans** (`oldPlanAttachments` from Step 3a is not empty).
 
-Before saving new plans, ask the user to confirm deletion of old `plan.md` attachments:
+**`--auto` mode**: Skip the confirmation prompt. For each task in `oldPlanAttachments`, delete the Linear attachment via `mcp__linear__delete_attachment({ id: attachmentId })` and proceed directly to Step 9a. Log the deletions in the final summary comment.
+
+**Default mode** (interactive): Before saving new plans, ask the user to confirm deletion of old `plan.md` attachments:
 
 ```markdown
 ## Zastąpienie istniejących planów
@@ -546,6 +580,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
@@ -630,4 +666,9 @@ After saving:
 
 ---
 
-**Important**: Before saving the plans as attachments, show them to the user for review and approval. The plan content is written to `/tmp/claude-plans/<taskId>-plan.md`, base64-encoded, and uploaded as a native Linear attachment via `mcp__linear__create_attachment`. After that, the `AI Plan` label is applied to the invoked issue.
+**Important**:
+
+- **Default mode**: Before saving the plans as attachments, show them to the user for review and approval.
+- **`--auto` mode**: Skip the review step; proceed directly to saving the attachments.
+
+The plan content is written to `/tmp/claude-plans/<taskId>-plan.md`, base64-encoded, and uploaded as a native Linear attachment via `mcp__linear__create_attachment`. After that, the `AI Plan` label is applied to the invoked issue.