@smartsoft001/pro-claude-plugins 0.2.0 → 0.4.0

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@smartsoft001/pro-claude-plugins",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "publishConfig": {
-    "access": "restricted"
+    "access": "public"
   },
   "scripts": {
     "postinstall": "claude plugin update smart-pro@smart-pro flow@smart-pro flow-legacy@smart-pro flow-external@smart-pro --scope project || true"

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

@@ -383,8 +383,8 @@ The agent will:
 
 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.
-2. **Write locally**: use `Write` to save the orchestration markdown to `/tmp/claude-plans/<taskId>-orchestration.md`.
-3. **Base64-encode**: `b64=$(base64 -i /tmp/claude-plans/<taskId>-orchestration.md)`.
+2. **Write locally**: ensure `.ai/tasks/` is gitignored (idempotent — `.ai/tasks` must NOT be synced to git): `grep -qxF '.ai/tasks/' .gitignore 2>/dev/null || echo '.ai/tasks/' >> .gitignore`. Then `mkdir -p .ai/tasks/<taskId>` and use `Write` to save the orchestration markdown to `.ai/tasks/<taskId>/orchestration.md` (sibling of `plan.md`).
+3. **Base64-encode**: `b64=$(base64 -i .ai/tasks/<taskId>/orchestration.md)`.
 4. **Create Linear attachment** via `mcp__linear__create_attachment`:
    - `issue`: the task/subtask ID
    - `filename`: `orchestration.md`
@@ -392,7 +392,7 @@ The agent will:
    - `title`: `orchestration.md` (exact — used for detection/replacement on the next `/impl` run)
    - `subtitle`: `Plan orkiestracji wygenerowany przez Claude Code`
    - `base64Content`: the base64 string from step 3
-5. **Clean up** the local `/tmp/claude-plans/<taskId>-orchestration.md` file after a successful attachment.
+5. **Keep the local file**: do NOT delete `.ai/tasks/<taskId>/orchestration.md` — it persists as a gitignored local artifact.
 6. **Follow the plan** — execute agents in the defined order.
 7. **Use TDD strictly** — `shared-tdd-developer` is MANDATORY for ALL code implementation.
 

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

@@ -679,7 +679,18 @@ When using `--deep` flag and the Planning Team has completed its analysis, appen
 
 **MANDATORY.** Before any Linear write (deletion of old `plan.md`, creation of new `plan.md`, label apply), the user MUST approve the generated plan content. This is the gate FRA-126 added.
 
-**`--auto` mode**: Skip this entire step. The plan is auto-approved. Record the auto-approval in the final Linear audit comment (e.g. `Plan zaakceptowany automatycznie (--auto)`). Proceed to Step 9.
+**Persist the plan locally first (both modes).** For each task/subtask that needs planning:
+
+- Ensure `.ai/tasks/` is gitignored (idempotent — `.ai/tasks` must NOT be synced to git):
+  ```bash
+  grep -qxF '.ai/tasks/' .gitignore 2>/dev/null || echo '.ai/tasks/' >> .gitignore
+  ```
+- `mkdir -p .ai/tasks/<taskId>`
+- Use the `Write` tool to save the Step 8 plan markdown to `.ai/tasks/<taskId>/plan.md`.
+
+This file is the source for the Linear attachment in Step 9a and is NOT deleted — it persists as a gitignored local artifact. On regeneration (below) the `Write` overwrites it with the new plan.
+
+**`--auto` mode**: Skip the approval prompt below — the plan is auto-approved and already persisted above. Record the auto-approval in the final Linear audit comment (e.g. `Plan zaakceptowany automatycznie (--auto)`). Proceed to Step 9.
 
 **Default mode** (interactive):
 
@@ -749,20 +760,14 @@ Use `AskUserQuestion` tool with options:
 
 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
-
-The plan content is exactly the markdown produced in Step 8 (the same block that would previously have been posted as a comment). Write it to the temp file:
-
-```bash
-mkdir -p /tmp/claude-plans
-```
+#### 9a.1 — Locate plan content
 
-Use the `Write` tool to save the plan markdown to `/tmp/claude-plans/<taskId>-plan.md`.
+The plan content was already written to `.ai/tasks/<taskId>/plan.md` in Step 8a (before acceptance). No temp file is needed — that persistent, gitignored file is the source for the attachment below.
 
 #### 9a.2 — Base64-encode the content
 
 ```bash
-b64=$(base64 -i /tmp/claude-plans/<taskId>-plan.md)
+b64=$(base64 -i .ai/tasks/<taskId>/plan.md)
 ```
 
 On macOS `base64 -i <file>` outputs without line-wrapping (which is what the Linear MCP expects). If you ever switch to GNU coreutils, pipe through `tr -d '\n'` to strip wraps.
@@ -780,9 +785,9 @@ Call `mcp__linear__create_attachment` with:
 
 Linear stores the file on its own infrastructure and surfaces it in the issue's Attachments pane.
 
-#### 9a.4 — Clean up local file
+#### 9a.4 — Keep the local file
 
-Delete `/tmp/claude-plans/<taskId>-plan.md` after the attachment is created successfully. `/push` leaves Linear attachments in place — they stay on the issue as permanent artifacts.
+Do NOT delete `.ai/tasks/<taskId>/plan.md` — it is intentionally kept as a gitignored local artifact. `/push` leaves Linear attachments in place — they stay on the issue as permanent artifacts.
 
 #### Scope rule
 
@@ -1030,4 +1035,4 @@ _Plan generated by Claude Code_
 - **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.
+The plan content is written to `.ai/tasks/<taskId>/plan.md` (before acceptance, gitignored), 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/skills/impl/SKILL.md

@@ -133,8 +133,8 @@ Use `shared-impl-orchestrator` agent to generate a `🎭 Agent Orchestration Pla
 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)`.
+2. **Write locally**: ensure `.ai/tasks/` is gitignored (idempotent — `.ai/tasks` must NOT be synced to git): `grep -qxF '.ai/tasks/' .gitignore 2>/dev/null || echo '.ai/tasks/' >> .gitignore`. Then `mkdir -p .ai/tasks/<taskId>` and `Write` the orchestration markdown to `.ai/tasks/<taskId>/orchestration.md` (sibling of `plan.md`).
+3. **Base64-encode**: `b64=$(base64 -i .ai/tasks/<taskId>/orchestration.md)`.
 4. **Create Linear attachment** via `mcp__linear__create_attachment`:
    - `issue`: the task ID
    - `filename`: `orchestration.md`
@@ -142,7 +142,7 @@ Then save it as an `orchestration.md` attachment on the task (not as a comment):
    - `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.
+5. **Keep the local file**: do NOT delete `.ai/tasks/<taskId>/orchestration.md` — it persists as a gitignored local artifact.
 
 ### Step 4: Implement Each Step
 

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

@@ -177,7 +177,18 @@ Structure the plan as follows:
 
 **MANDATORY.** Before any Linear write (subtask creation, attachment delete, attachment create, label apply), the user MUST approve the generated plan content. This is the gate FRA-126 added.
 
-**`--auto` mode**: Skip this entire step. The plan is auto-approved. Record the auto-approval in the final Linear audit comment (e.g. `Plan zaakceptowany automatycznie (--auto)`). Proceed to Step 5.
+**Persist the plan locally first (both modes — this is the "przed akceptacją" save).**
+
+- Ensure `.ai/tasks/` is gitignored (idempotent — `.ai/tasks` must NOT be synced to git):
+  ```bash
+  grep -qxF '.ai/tasks/' .gitignore 2>/dev/null || echo '.ai/tasks/' >> .gitignore
+  ```
+- `mkdir -p .ai/tasks/<taskId>`
+- Use the `Write` tool to save the Step 4 plan markdown to `.ai/tasks/<taskId>/plan.md`.
+
+This file is the source for the Linear attachment in Step 6 and is NOT deleted — it persists as a gitignored local artifact. On regeneration (below) the `Write` overwrites it with the new plan.
+
+**`--auto` mode**: Skip the approval prompt below — the plan is auto-approved and already persisted above. Record the auto-approval in the final Linear audit comment (e.g. `Plan zaakceptowany automatycznie (--auto)`). Proceed to Step 5.
 
 **Default mode** (interactive):
 
@@ -233,20 +244,14 @@ If a `plan.md` attachment is being replaced:
 
 - **`--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
-
-The plan content is exactly the markdown produced in Step 4. Write it to the temp file:
-
-```bash
-mkdir -p /tmp/claude-plans
-```
+#### 6.2 — Locate plan content
 
-Use `Write` to save the plan content to `/tmp/claude-plans/<taskId>-plan.md`.
+The plan content was already written to `.ai/tasks/<taskId>/plan.md` in Step 4a (before acceptance). No temp file is needed — that persistent, gitignored file is the source for the attachment below.
 
 #### 6.3 — Base64-encode
 
 ```bash
-b64=$(base64 -i /tmp/claude-plans/<taskId>-plan.md)
+b64=$(base64 -i .ai/tasks/<taskId>/plan.md)
 ```
 
 #### 6.4 — Create Linear attachment
@@ -260,9 +265,9 @@ Call `mcp__linear__create_attachment` with:
 - `subtitle`: `Plan wygenerowany przez Claude Code (external)`
 - `base64Content`: the base64 string from 6.3
 
-#### 6.5 — Clean up local file
+#### 6.5 — Keep the local file
 
-Delete `/tmp/claude-plans/<taskId>-plan.md` after the attachment is created. `/push` leaves the Linear attachment in place.
+Do NOT delete `.ai/tasks/<taskId>/plan.md` — it is intentionally kept as a gitignored local artifact. `/push` leaves the Linear attachment in place.
 
 ### Step 7: Add "AI Plan" Label
 

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

@@ -352,8 +352,8 @@ The agent will:
 
 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.
-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)`.
+2. **Write locally**: ensure `.ai/tasks/` is gitignored (idempotent — `.ai/tasks` must NOT be synced to git): `grep -qxF '.ai/tasks/' .gitignore 2>/dev/null || echo '.ai/tasks/' >> .gitignore`. Then `mkdir -p .ai/tasks/<taskId>` and `Write` the orchestration markdown to `.ai/tasks/<taskId>/orchestration.md` (sibling of `plan.md`).
+3. **Base64-encode**: `b64=$(base64 -i .ai/tasks/<taskId>/orchestration.md)`.
 4. **Create Linear attachment** via `mcp__linear__create_attachment`:
    - `issue`: the task/subtask ID
    - `filename`: `orchestration.md`
@@ -361,7 +361,7 @@ The agent will:
    - `title`: `orchestration.md` (exact — used for detection/replacement on the next `/impl` run)
    - `subtitle`: `Plan orkiestracji wygenerowany przez Claude Code (legacy)`
    - `base64Content`: the base64 string from step 3
-5. **Clean up** local `/tmp/claude-plans/<taskId>-orchestration.md`.
+5. **Keep the local file**: do NOT delete `.ai/tasks/<taskId>/orchestration.md` — it persists as a gitignored local artifact.
 6. **Follow the plan** — execute agents in the defined order.
 7. **Use TDD strictly** — `shared-tdd-developer` is MANDATORY for ALL code implementation.
 

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

@@ -550,7 +550,18 @@ _Plan generated by Claude Code (flow-legacy)_
 
 **MANDATORY.** Before any Linear write (deletion of old `plan.md`, creation of new `plan.md`, label apply), the user MUST approve the generated plan content. This is the gate FRA-126 added.
 
-**`--auto` mode**: Skip this entire step. The plan is auto-approved. Record the auto-approval in the final Linear audit comment (e.g. `Plan zaakceptowany automatycznie (--auto)`). Proceed to Step 9.
+**Persist the plan locally first (both modes — this is the "przed akceptacją" save).** For each task/subtask that needs planning:
+
+- Ensure `.ai/tasks/` is gitignored (idempotent — `.ai/tasks` must NOT be synced to git):
+  ```bash
+  grep -qxF '.ai/tasks/' .gitignore 2>/dev/null || echo '.ai/tasks/' >> .gitignore
+  ```
+- `mkdir -p .ai/tasks/<taskId>`
+- Use the `Write` tool to save the Step 8 plan markdown to `.ai/tasks/<taskId>/plan.md`.
+
+This file is the source for the Linear attachment in Step 9a and is NOT deleted — it persists as a gitignored local artifact. On regeneration (below) the `Write` overwrites it with the new plan.
+
+**`--auto` mode**: Skip the approval prompt below — the plan is auto-approved and already persisted above. Record the auto-approval in the final Linear audit comment (e.g. `Plan zaakceptowany automatycznie (--auto)`). Proceed to Step 9.
 
 **Default mode** (interactive):
 
@@ -618,20 +629,14 @@ Use `AskUserQuestion` with options:
 
 For each task that needs planning, upload the plan content directly to Linear (no external storage).
 
-#### 9a.1 — Write `plan.md` locally
-
-The plan content is exactly the markdown produced in Step 8. Write it to the temp file:
-
-```bash
-mkdir -p /tmp/claude-plans
-```
+#### 9a.1 — Locate plan content
 
-Use `Write` to save the plan content to `/tmp/claude-plans/<taskId>-plan.md`.
+The plan content was already written to `.ai/tasks/<taskId>/plan.md` in Step 8a (before acceptance). No temp file is needed — that persistent, gitignored file is the source for the attachment below.
 
 #### 9a.2 — Base64-encode
 
 ```bash
-b64=$(base64 -i /tmp/claude-plans/<taskId>-plan.md)
+b64=$(base64 -i .ai/tasks/<taskId>/plan.md)
 ```
 
 On macOS `base64 -i <file>` outputs without line-wrapping. On Linux, pipe through `tr -d '\n'` if needed.
@@ -649,9 +654,9 @@ Call `mcp__linear__create_attachment` with:
 
 Linear hosts the file on its own infrastructure.
 
-#### 9a.4 — Clean up local file
+#### 9a.4 — Keep the local file
 
-Delete `/tmp/claude-plans/<taskId>-plan.md` after the attachment is created. `/push` does NOT delete Linear attachments — they stay on the issue.
+Do NOT delete `.ai/tasks/<taskId>/plan.md` — it is intentionally kept as a gitignored local artifact. `/push` does NOT delete Linear attachments — they stay on the issue.
 
 #### Scope rule
 
@@ -739,4 +744,4 @@ After saving:
 - **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.
+The plan content is written to `.ai/tasks/<taskId>/plan.md` (before acceptance, gitignored), 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.