Merge pull request #30 from AndreJorgeLopes/chore/post-mr29-skill-mirror-sync

chore(skills): sync mirrors + scrub stale /compact and natural-language refs post-MR#29

Author: AndreJorgeLopes

CLAUDE.md

@@ -90,9 +90,11 @@ brainstorming → spec-feature → writing-plans → lock-tests → executing-pl
 - `finish-feature` runs verification, creates the PR/MR, retains learnings.
 
 Each phase ends by invoking `devflow:phase-handoff`, which writes a frozen-state file
-at `.devflow/state/<branch>/<phase>.md` and prompts the user to run `/compact`. The next
-phase reads only the frozen-state file as source of truth — the brainstorming context
-does not bleed into implementation.
+at `.devflow/state/<branch>/<phase>.md` (with worktree-relative artefact paths), gates
+on a one-click `AskUserQuestion`, then emits a copy-pasteable resume prompt (with
+ABSOLUTE artefact paths) for the user to paste after `/clear`. The next phase reads
+only the frozen-state file and the artefact paths the resume block hands it as source
+of truth — the brainstorming context does not bleed into implementation.
 
 On feature branches, always complete work with `/devflow:finish-feature` before ending
 the session.

devflow-plugin/commands/finish-feature.md

@@ -11,10 +11,11 @@ You are finishing a feature. Run the full completion pipeline before handing off
 1. Detect ticket ID from `git branch --show-current` (regex `[A-Z]+-[0-9]+`); if none, use `none`.
 2. Call `mark_chapter` with `{title: "Finish — <TICKET>", summary: "Finishing the feature"}`.
    If `mark_chapter` is unavailable (e.g. running outside Claude Code), skip silently.
-3. Echo ANSI terminal-title escape:
+3. Set terminal window title (CLI Claude Code only — silent no-op in Claude Desktop):
    ```bash
-   printf '\e]2;%s — Finish\007' "<TICKET>"
+   [ -t 1 ] && printf '\e]2;%s — Finish\007' "<TICKET>" || true
    ```
+   In Claude Desktop there is no controlling terminal — the visible phase signal comes from `mark_chapter` (step 2).
 
 ## Steps
 

devflow-plugin/commands/lock-tests.md

@@ -22,10 +22,11 @@ You are at the test-locking phase of devflow's new-feature pipeline. Your job is
 
    If `mark_chapter` is unavailable (e.g. running outside Claude Code), skip silently.
 
-3. **ANSI terminal-title escape:**
+3. **Set terminal window title (CLI Claude Code only — silent no-op in Claude Desktop):**
    ```bash
-   printf '\e]2;%s — Lock Tests\007' "<TICKET>"
+   [ -t 1 ] && printf '\e]2;%s — Lock Tests\007' "<TICKET>" || true
    ```
+   In Claude Desktop there is no controlling terminal — the visible phase signal comes from `mark_chapter` (step 2).
 
 4. **Read the frozen-state file** from the previous phase:
    `.devflow/state/${branch_slug}/plan.md`
@@ -47,7 +48,7 @@ You are at the test-locking phase of devflow's new-feature pipeline. Your job is
    - If user skips: invoke `devflow:phase-handoff --phase lock-tests --next-phase impl --no-handoff`. Then print:
 
    ```
-   Trivial change — lock-tests gate skipped. Context is already small; you can proceed directly to the next phase without `/clear`. Trigger executing-plans by typing: `Use the superpowers:executing-plans skill to implement the plan task by task` (natural-language skill trigger — superpowers exposes skills via the `Skill` tool, not as `/`-prefixed commands).
+   Trivial change — lock-tests gate skipped. Context is already small; you can proceed directly to the next phase without `/clear`. Invoke `/executing-plans` (Claude Code auto-exposes the superpowers skill as a slash command; if the picker doesn't surface it on older installs, use the natural-language trigger `Use the superpowers:executing-plans skill to implement the plan task by task` instead).
    ```
 
    Then exit.
@@ -154,7 +155,7 @@ Use `AskUserQuestion` with:
 
 ## Phase 2 — GREEN (delegated)
 
-After approval, invoke `devflow:phase-handoff --phase lock-tests --next-phase impl`. The handoff skill writes the frozen-state file, gates on a one-click `AskUserQuestion`, then emits a copy-pasteable resume prompt for the user to paste after `/clear`. After `/clear` + paste, the new session reads the frozen-state file and invokes `superpowers:executing-plans` via natural-language skill trigger (no `/superpowers:*` slash command exists), which drives per-task red/green against the tests already locked in this phase.
+After approval, invoke `devflow:phase-handoff --phase lock-tests --next-phase impl`. The handoff skill writes the frozen-state file, gates on a one-click `AskUserQuestion`, then emits a copy-pasteable resume prompt for the user to paste after `/clear`. After `/clear` + paste, the new session invokes `/executing-plans` (the superpowers skill auto-exposed as a slash command by Claude Code's plugin runtime) which drives per-task red/green against the tests already locked in this phase.
 
 ## Phase 3 — REFACTOR (delegated)
 

devflow-plugin/commands/new-feature.md

@@ -11,10 +11,11 @@ You have been launched inside a feature worktree. Your job is to orient yourself
 1. Detect ticket ID from `git branch --show-current` (regex `[A-Z]+-[0-9]+`); if none, use `none`.
 2. Call `mark_chapter` with `{title: "Brainstorm — <TICKET>", summary: "Starting a new feature"}`.
    If `mark_chapter` is unavailable (e.g. running outside Claude Code), skip silently.
-3. Echo ANSI terminal-title escape:
+3. Set terminal window title (CLI Claude Code only — silent no-op in Claude Desktop):
    ```bash
-   printf '\e]2;%s — Brainstorm\007' "<TICKET>"
+   [ -t 1 ] && printf '\e]2;%s — Brainstorm\007' "<TICKET>" || true
    ```
+   In Claude Desktop there is no controlling terminal — the visible phase signal comes from `mark_chapter` (step 2).
 
 ## Steps
 

devflow-plugin/commands/phase-handoff.md

@@ -77,12 +77,14 @@ If `--no-handoff` is present, print "phase-handoff skipped" and exit.
 
    If `mark_chapter` is unavailable (e.g. running outside Claude Code), skip silently.
 
-6. **Echo ANSI terminal-title escape:**
+6. **Set terminal window title (CLI Claude Code only — silent no-op in Claude Desktop):**
 
    ```bash
-   printf '\e]2;%s — %s\007' "<TICKET>" "<mapped-title>"
+   [ -t 1 ] && printf '\e]2;%s — %s\007' "<TICKET>" "<mapped-title>" || true
    ```
 
+   In Claude Desktop there is no controlling terminal (stdout is captured by the harness, `/dev/tty` is unavailable), so the escape would never reach a window manager. The visible phase signal comes from `mark_chapter` (step 5).
+
 7. **Resolve the next-phase invocation text.** Map `<next-phase>` to what the user must paste after `/clear`:
 
    | `<next-phase>` | Text to paste |

devflow-plugin/commands/spec-feature.md

@@ -9,10 +9,11 @@ You are speccing a new feature. This command enforces a structured planning proc
 1. Detect ticket ID from `git branch --show-current` (regex `[A-Z]+-[0-9]+`); if none, use `none`.
 2. Call `mark_chapter` with `{title: "Spec — <TICKET>", summary: "Writing the spec document"}`.
    If `mark_chapter` is unavailable (e.g. running outside Claude Code), skip silently.
-3. Echo ANSI terminal-title escape:
+3. Set terminal window title (CLI Claude Code only — silent no-op in Claude Desktop):
    ```bash
-   printf '\e]2;%s — Spec\007' "<TICKET>"
+   [ -t 1 ] && printf '\e]2;%s — Spec\007' "<TICKET>" || true
    ```
+   In Claude Desktop there is no controlling terminal — the visible phase signal comes from `mark_chapter` (step 2).
 
 ## Steps
 

devflow-plugin/commands/writing-plans.md

@@ -10,10 +10,11 @@ When the following events occur, apply these additions:
 1. Detect ticket ID from current branch name (regex `[A-Z]+-[0-9]+`); if none, use `none`.
 2. Call `mark_chapter` with `{title: "Plan — <TICKET>", summary: "Writing implementation plan"}`.
    If `mark_chapter` is unavailable (e.g. running outside Claude Code), skip silently.
-3. Echo ANSI terminal-title escape:
+3. Set terminal window title (CLI Claude Code only — silent no-op in Claude Desktop):
    ```bash
-   printf '\e]2;%s — Plan\007' "<TICKET>"
+   [ -t 1 ] && printf '\e]2;%s — Plan\007' "<TICKET>" || true
    ```
+   In Claude Desktop there is no controlling terminal — the visible phase signal comes from `mark_chapter` (step 2).
 
 ## After: Plan saved to disk
 

skills/lock-tests/SKILL.md

@@ -49,12 +49,11 @@ You are at the test-locking phase of devflow's new-feature pipeline. Your job is
    - If user skips: invoke `devflow:phase-handoff --phase lock-tests --next-phase impl --no-handoff`. Then print:
 
    ```
-   Trivial change — lock-tests gate skipped. Context is already small; you can proceed directly to `/superpowers:executing-plans` without `/compact`.
+   Trivial change — lock-tests gate skipped. Context is already small; you can proceed directly to the next phase without `/clear`. Invoke `/executing-plans` (Claude Code auto-exposes the superpowers skill as a slash command; if the picker doesn't surface it on older installs, use the natural-language trigger `Use the superpowers:executing-plans skill to implement the plan task by task` instead).
    ```
 
    Then exit.
 
-
 7. **Check git status:**
    ```bash
    git status --porcelain
@@ -157,7 +156,7 @@ Use `AskUserQuestion` with:
 
 ## Phase 2 — GREEN (delegated)
 
-After approval, invoke `devflow:phase-handoff --phase lock-tests --next-phase impl`. The handoff skill writes the frozen-state file and prompts the user to `/compact`. After compact, the user re-invokes `superpowers:executing-plans` which drives per-task red/green where the tests already exist.
+After approval, invoke `devflow:phase-handoff --phase lock-tests --next-phase impl`. The handoff skill writes the frozen-state file, gates on a one-click `AskUserQuestion`, then emits a copy-pasteable resume prompt for the user to paste after `/clear`. After `/clear` + paste, the new session invokes `/executing-plans` (the superpowers skill auto-exposed as a slash command by Claude Code's plugin runtime) which drives per-task red/green against the tests already locked in this phase.
 
 ## Phase 3 — REFACTOR (delegated)
 

skills/new-feature/SKILL.md

@@ -72,7 +72,7 @@ You have been launched inside a feature worktree. Your job is to orient yourself
    ```
    brainstorming → spec-feature → writing-plans → lock-tests → executing-plans → finish-feature
    ```
-   Each phase ends with `devflow:phase-handoff` (writes a frozen-state file, prompts you to run `/compact`). The next phase reads only the frozen-state file as source of truth.
+   Each phase ends with `devflow:phase-handoff` (writes a frozen-state file, gates via one-click `AskUserQuestion`, then emits a copy-pasteable resume prompt for the user to paste after `/clear`). The next phase reads only the frozen-state file and the artefact paths it lists as source of truth.
 
 ## Important
 

skills/registry.json

@@ -108,7 +108,7 @@
     },
     {
       "name": "phase-handoff",
-      "description": "Hand off between phases of the devflow new-feature pipeline — writes a frozen-state file, marks a chapter, and prompts user to /compact.",
+      "description": "Hand off between phases of the devflow new-feature pipeline — writes a frozen-state file, marks a chapter, sets terminal title, gates on a one-click AskUserQuestion, then emits a copy-pasteable resume prompt for the user to paste after /clear.",
       "category": "workflow",
       "layer": 4
     },