1	# Changelog
2
3	All notable changes to the SPT (Spacetime / Sentience Pocket Transacter) plugin are documented in this file.
4
5	The format is based on [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Entries authored retroactively from `git log --grep='chore: bump'` at Phase 34 (v1.7.1 milestone).
6
7	## [1.11.25] - 2026-06-02
8
9	- TODO: changelog entry
10
11	## [1.11.24] - 2026-06-02
12
13	### Fixed
14	- **A busy Psyche no longer disappears from `$OWL list` — or gets killed by checking on it.** While your Psyche was ingesting a commune (its wrapper running a background summary), the perch could read as offline and drop out of `$OWL list`; worse, running `$LIVE list-psyches` during that window could clear the perch's `ready` marker and make the wrapper shut down on its next cycle, taking the Psyche down for good. Psyche liveness now keys on whether the wrapper itself is alive, so a busy Psyche stays visible and is never torn down by a read-only listing command.
15	- **Clearer after-`/clear` guidance for live agents.** The session re-orientation text wrongly described a `pid:"BUSY"` listener as "dead" and implied you should rebuild your poll after `/clear`. It now states the truth: a `BUSY` listener is online and mid-delivery; your poll survives `/clear` intact, so do nothing (a `DUPLICATE` on a re-arm attempt is proof it is still alive); never use `$LIVE stop` to clear a "stale" listener (that tears down your Psyche); and live agents re-arm with `listen --live` when a re-arm is genuinely needed.
16
17	### BTS
18	- debug/post-clear-poll-psyche-misread: `src/common/list_filter.rs::collect` and `src/live/list_psyches.rs` gain a `wrapper_backed_alive` check (`owlery::is_wrapper_alive` on the `-psyche`-stripped id) that forces a wrapper-owned psyche perch ONLINE and skips the destructive `ready` soft-clean — closing the gap where the existing Gate-A wrapper protection covered only the info-missing branch, not the info-present stale path. Wrapper-owned psyche perches carry the inner-poll pid and no `parent_pid` (types.rs:182-186), so the inner poll exiting during ingest otherwise read as dead. SessionStart reorientation string in `src/owl/resume.rs` corrected (BUSY=online, post-/clear do-nothing, no `$LIVE stop`, live-aware `{poll_cmd}` re-arm). 1 new regression test (`live_wrapper_keeps_busy_psyche_online_and_ready_intact`).
19
20	## [1.11.23] - 2026-06-02
21
22	### Fixed
23	- **A manual commune or signoff no longer triggers a redundant automatic context summary right afterward.** Sending a `/spt:commune` (or signing off) already flushes your latest context to the Psyche; previously a pending background cadence trigger could still fire a duplicate echo-commune moments later. Delivering a commune/signoff now also clears that pending trigger, so the next automatic summary waits for the normal cadence.
24
25	### BTS
26	- quick-260602-2ar: `process_file_drop` (`src/live/wrapper/mod.rs`) now clears the `.more-done` cadence sentinel at its two FILE-DROP consume exits (empty-body signoff skip + the shared `exit_code == 0` block covering commune / init-stale signoff / normal signoff), gated on consume success so a failed consume keeps the sentinel. The previously-inlined delete-both logic in `echo_fire.rs` was extracted into a shared free fn `remove_both_more_done(nested, flat)` + `WrapperState::delete_more_done_sentinel()` (derives both paths via `owlery::nested_perch_dir` + `perch_dir`, honoring the reader/writer path-asymmetry KNOWN-HAZARD); `fire_echo_commune_if_due` rewired onto it so fire-path and consume-path share one delete code path. 2 new echo_fire unit tests.
27
28	## [1.11.22] - 2026-05-30
29
30	### Fixed
31	- **Attaching a second machine no longer overwrites the other machine's agent context.** `psyche-sync-setup` used force-push semantics for agent branches, so attaching a second machine could clobber remote branch heads holding the first machine's most recent writes (a data-loss risk). Setup now reconciles before pushing — fetches the remote, rebases any diverged branches onto the remote head, and pushes per-ref with observable outcomes — so concurrent machines converge instead of overwriting each other.
32	- **Second-machine setup no longer fails with a non-fast-forward rejection.** Each machine used to generate its own empty-seed commit, creating a `main` divergence that setup then refused to push past. The seed bootstrap is now deterministic (every machine produces a byte-identical `main`), and pre-existing wall-clock-seeded installs are absorbed automatically through the new reconciliation path — no migration command needed.
33	- **`psyche-sync-setup` failures now show a readable error.** The skill's failure path printed raw Rust debug output (`GitFailed(Nonzero { stderr: "..." })`); it now prints the curated, human-readable error line so you can actually act on it.
34	- **Live agents in non-git host projects now back up their project context.** Starting a live agent in a directory that is not a git repository previously skipped syncing that project's tracked context (`psyches/tracked/projects/<name>/`) — the project-name resolver returned nothing outside a git repo. It now falls back to the directory's own name (guarded against ref-unsafe characters), so non-git projects get their context worktree, commit, and push like any other.
35

# Changelog

All notable changes to the SPT (Spacetime / Sentience Pocket Transacter) plugin are documented in this file.

The format is based on [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Entries authored retroactively from `git log --grep='chore: bump'` at Phase 34 (v1.7.1 milestone).

## [1.11.25] - 2026-06-02

- TODO: changelog entry

## [1.11.24] - 2026-06-02

### Fixed
- **A busy Psyche no longer disappears from `$OWL list` — or gets killed by checking on it.** While your Psyche was ingesting a commune (its wrapper running a background summary), the perch could read as offline and drop out of `$OWL list`; worse, running `$LIVE list-psyches` during that window could clear the perch's `ready` marker and make the wrapper shut down on its next cycle, taking the Psyche down for good. Psyche liveness now keys on whether the wrapper itself is alive, so a busy Psyche stays visible and is never torn down by a read-only listing command.
- **Clearer after-`/clear` guidance for live agents.** The session re-orientation text wrongly described a `pid:"BUSY"` listener as "dead" and implied you should rebuild your poll after `/clear`. It now states the truth: a `BUSY` listener is online and mid-delivery; your poll survives `/clear` intact, so do nothing (a `DUPLICATE` on a re-arm attempt is proof it is still alive); never use `$LIVE stop` to clear a "stale" listener (that tears down your Psyche); and live agents re-arm with `listen --live` when a re-arm is genuinely needed.

### BTS
- debug/post-clear-poll-psyche-misread: `src/common/list_filter.rs::collect` and `src/live/list_psyches.rs` gain a `wrapper_backed_alive` check (`owlery::is_wrapper_alive` on the `-psyche`-stripped id) that forces a wrapper-owned psyche perch ONLINE and skips the destructive `ready` soft-clean — closing the gap where the existing Gate-A wrapper protection covered only the info-missing branch, not the info-present stale path. Wrapper-owned psyche perches carry the inner-poll pid and no `parent_pid` (types.rs:182-186), so the inner poll exiting during ingest otherwise read as dead. SessionStart reorientation string in `src/owl/resume.rs` corrected (BUSY=online, post-/clear do-nothing, no `$LIVE stop`, live-aware `{poll_cmd}` re-arm). 1 new regression test (`live_wrapper_keeps_busy_psyche_online_and_ready_intact`).

## [1.11.23] - 2026-06-02

### Fixed
- **A manual commune or signoff no longer triggers a redundant automatic context summary right afterward.** Sending a `/spt:commune` (or signing off) already flushes your latest context to the Psyche; previously a pending background cadence trigger could still fire a duplicate echo-commune moments later. Delivering a commune/signoff now also clears that pending trigger, so the next automatic summary waits for the normal cadence.

### BTS
- quick-260602-2ar: `process_file_drop` (`src/live/wrapper/mod.rs`) now clears the `.more-done` cadence sentinel at its two FILE-DROP consume exits (empty-body signoff skip + the shared `exit_code == 0` block covering commune / init-stale signoff / normal signoff), gated on consume success so a failed consume keeps the sentinel. The previously-inlined delete-both logic in `echo_fire.rs` was extracted into a shared free fn `remove_both_more_done(nested, flat)` + `WrapperState::delete_more_done_sentinel()` (derives both paths via `owlery::nested_perch_dir` + `perch_dir`, honoring the reader/writer path-asymmetry KNOWN-HAZARD); `fire_echo_commune_if_due` rewired onto it so fire-path and consume-path share one delete code path. 2 new echo_fire unit tests.

## [1.11.22] - 2026-05-30

### Fixed
- **Attaching a second machine no longer overwrites the other machine's agent context.** `psyche-sync-setup` used force-push semantics for agent branches, so attaching a second machine could clobber remote branch heads holding the first machine's most recent writes (a data-loss risk). Setup now reconciles before pushing — fetches the remote, rebases any diverged branches onto the remote head, and pushes per-ref with observable outcomes — so concurrent machines converge instead of overwriting each other.
- **Second-machine setup no longer fails with a non-fast-forward rejection.** Each machine used to generate its own empty-seed commit, creating a `main` divergence that setup then refused to push past. The seed bootstrap is now deterministic (every machine produces a byte-identical `main`), and pre-existing wall-clock-seeded installs are absorbed automatically through the new reconciliation path — no migration command needed.
- **`psyche-sync-setup` failures now show a readable error.** The skill's failure path printed raw Rust debug output (`GitFailed(Nonzero { stderr: "..." })`); it now prints the curated, human-readable error line so you can actually act on it.
- **Live agents in non-git host projects now back up their project context.** Starting a live agent in a directory that is not a git repository previously skipped syncing that project's tracked context (`psyches/tracked/projects/<name>/`) — the project-name resolver returned nothing outside a git repo. It now falls back to the directory's own name (guarded against ref-unsafe characters), so non-git projects get their context worktree, commit, and push like any other.


Edit

## [1.11.25] - 2026-06-02

### Fixed
- **A live agent re-orienting after `/clear` now gets its full context back instead of an empty one.** When a live agent cleared its context, the automatic re-hydration that re-sends your saved live-context and project-context to Self could arrive empty (`<live-context></live-context>`), leaving the freshly-cleared agent with nothing to resume from. The re-hydration was being summarized as a "delta" — and right after a `/clear` there is no new work versus the saved snapshot, so the summary was correctly empty. The clear-path now re-emits your saved context verbatim instead of computing a delta, so a post-`/clear` agent wakes up with its real state.

### BTS
- debug/fire-ec-empty-slices: root cause was a prompt/intent mismatch, not a slice-threading or persistence bug. The FIRE-EC `source=clear` re-emission reused the cadence echo-commune DELTA prompt; post-`/clear` the delta is genuinely empty so the haiku emitted empty slice bodies by design and the envelope faithfully forwarded them. Fix threads `source` end-to-end (`cli.rs` `--source` flag → `owl/mod.rs` → `echo_fire.rs` `build_inner_argv`/`fire_echo_commune_inner` → `wrapper/mod.rs` `fire_echo_commune_force`; cadence/orphan paths pass `None`/carry no flag). `run_echo_commune` extracts `build_echo_commune_prompt`: `source=="clear"` selects a re-emit prompt (echo `CURRENT_LIVE_CONTEXT`/`CURRENT_PROJECT_CONTEXT` verbatim), all other values keep the delta prompt. Belt-and-suspenders: the Self-leg dispatch (`forward_to_self`) now falls back to the on-disk snapshot via `two_slice_effectively_empty` + `snapshot_two_slice_body` + a `self_body_override` closure when the haiku emits empty slices (`Some("")` from `extract_tag` treated as empty). 13 new tests (10 `fire_ec_empty_slices_tests` + 3 `--source` clap parse). Commit `c965c4a`.


The file C:\Users\decid\Documents\projects\claude_skill_owl\CHANGELOG.md has been updated successfully. (file state is current in your context — no need to Read it back)

## [1.11.25] - 2026-06-02

### Fixed
- **A live agent re-orienting after `/clear` now gets its full context back instead of an empty one.** When a live agent cleared its context, the automatic re-hydration that re-sends your saved live-context and project-context to Self could arrive empty (`<live-context></live-context>`), leaving the freshly-cleared agent with nothing to resume from. The re-hydration was being summarized as a "delta" — and right after a `/clear` there is no new work versus the saved snapshot, so the summary was correctly empty. The clear-path now re-emits your saved context verbatim instead of computing a delta, so a post-`/clear` agent wakes up with its real state.

### BTS
- debug/fire-ec-empty-slices: root cause was a prompt/intent mismatch, not a slice-threading or persistence bug. The FIRE-EC `source=clear` re-emission reused the cadence echo-commune DELTA prompt; post-`/clear` the delta is genuinely empty so the haiku emitted empty slice bodies by design and the envelope faithfully forwarded them. Fix threads `source` end-to-end (`cli.rs` `--source` flag → `owl/mod.rs` → `echo_fire.rs` `build_inner_argv`/`fire_echo_commune_inner` → `wrapper/mod.rs` `fire_echo_commune_force`; cadence/orphan paths pass `None`/carry no flag). `run_echo_commune` extracts `build_echo_commune_prompt`: `source=="clear"` selects a re-emit prompt (echo `CURRENT_LIVE_CONTEXT`/`CURRENT_PROJECT_CONTEXT` verbatim), all other values keep the delta prompt. Belt-and-suspenders: the Self-leg dispatch (`forward_to_self`) now falls back to the on-disk snapshot via `two_slice_effectively_empty` + `snapshot_two_slice_body` + a `self_body_override` closure when the haiku emits empty slices (`Some("")` from `extract_tag` treated as empty). 13 new tests (10 `fire_ec_empty_slices_tests` + 3 `--source` clap parse). Commit `c965c4a`.

+- **A live agent re-orienting after `/clear` now gets its full context back instead of an empty one.** When a live agent cleared its context, the automatic re-hydration that re-sends your saved live-context and project-context to Self could arrive empty (`<live-context></live-context>`), leaving the freshly-cleared agent with nothing to resume from. The re-hydration was being summarized as a "delta" — and right after a `/clear` there is no new work versus the saved snapshot, so the summary was correctly empty. The clear-path now re-emits your saved context verbatim instead of computing a delta, so a post-`/clear` agent wakes up with its real state.

+- debug/fire-ec-empty-slices: root cause was a prompt/intent mismatch, not a slice-threading or persistence bug. The FIRE-EC `source=clear` re-emission reused the cadence echo-commune DELTA prompt; post-`/clear` the delta is genuinely empty so the haiku emitted empty slice bodies by design and the envelope faithfully forwarded them. Fix threads `source` end-to-end (`cli.rs` `--source` flag → `owl/mod.rs` → `echo_fire.rs` `build_inner_argv`/`fire_echo_commune_inner` → `wrapper/mod.rs` `fire_echo_commune_force`; cadence/orphan paths pass `None`/carry no flag). `run_echo_commune` extracts `build_echo_commune_prompt`: `source=="clear"` selects a re-emit prompt (echo `CURRENT_LIVE_CONTEXT`/`CURRENT_PROJECT_CONTEXT` verbatim), all other values keep the delta prompt. Belt-and-suspenders: the Self-leg dispatch (`forward_to_self`) now falls back to the on-disk snapshot via `two_slice_effectively_empty` + `snapshot_two_slice_body` + a `self_body_override` closure when the haiku emits empty slices (`Some("")` from `extract_tag` treated as empty). 13 new tests (10 `fire_ec_empty_slices_tests` + 3 `--source` clap parse). Commit `c965c4a`.


Bash

cd "C:/Users/decid/Documents/projects/claude_skill_owl" && git add CHANGELOG.md && git commit -F - <<'EOF'
docs(34): fill v1.11.25 CHANGELOG entry

FIRE-EC source=clear re-hydration emitted empty slices post-/clear.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
EOF

Commit CHANGELOG entry for 1.11.25


[main b1eb8b2] docs(34): fill v1.11.25 CHANGELOG entry
 1 file changed, 8 insertions(+)


CHANGELOG committed (`b1eb8b2`). Re-running deploy.


PowerShell

powershell -ExecutionPolicy Bypass -File docs/DEPLOY.ps1 -Bump patch

Build, bump patch, sync to marketplace, install plugin


Command running in background with ID: bjzuzkb51. Output is being written to: C:\Users\decid\AppData\Local\Temp\claude\C--Users-decid-Documents-projects-claude-skill-owl\4fe4b176-7015-42ee-8d73-661e05b6dc30\tasks\bjzuzkb51.output. You will be notified when it completes. To check interim output, use Read on that file path.


Deploy re-running (bg `bjzuzkb51`) with CHANGELOG gate cleared. Notify on finish.


<task-notification>
<task-id>bjzuzkb51</task-id>
<tool-use-id>toolu_01SCidi1DyZkCsERxfyuUvPH</tool-use-id>
<output-file>C:\Users\decid\AppData\Local\Temp\claude\C--Users-decid-Documents-projects-claude-skill-owl\4fe4b176-7015-42ee-8d73-661e05b6dc30\tasks\bjzuzkb51.output</output-file>
<status>completed</status>
<summary>Background command "Build, bump patch, sync to marketplace, install plugin" completed (exit code 0)</summary>
</task-notification>


CAVEMAN MODE ACTIVE (full). Drop articles/filler/pleasantries/hedging. Fragments OK. Code/commits/security: write normal.


<owl_reachability_notice>
You have an active owl perch. When spawning subagents or doing work, use run_in_background: true so you stay reachable for incoming messages.
</owl_reachability_notice>


Deploy succeeded exit 0. Verifying tail.


HANDOFF: trampoline -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25\owl.exe


1	==> Step 1: Resolve version from plugin.json
2	    Current version: 1.11.24
3	    Bumping (patch): 1.11.24 -> 1.11.25
4	[main be5f2e7] chore: bump spt plugin to v1.11.25
5	 2 files changed, 2 insertions(+), 2 deletions(-)
6	    Committed bump: be5f2e7 (not pushed; plugin.json + Cargo.toml only -- CHANGELOG entry was pre-committed)
7	    Version: 1.11.25
8	    RepoRoot: C:\Users\decid\Documents\projects\claude_skill_owl
9	    Marketplace: C:\Users\decid\.claude\plugins\marketplaces\cplugs
10	    PluginDir: C:\Users\decid\.claude\plugins\spt
11	==> Step 3: cargo build --release
12	   Compiling owl v1.11.25 (C:\Users\decid\Documents\projects\claude_skill_owl)
13	warning: unused import: `perch_path`
14	 --> src\owl\cleanup.rs:4:50
15	  |
16	4 | use crate::common::{hook_output, output, owlery, perch_path, process, types};
17	  |                                                  ^^^^^^^^^^
18	  |
19	  = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
20
21	warning: unused import: `crate::common::perch_path::ParentHint`
22	 --> src\owl\cleanup.rs:5:5
23	  |
24	5 | use crate::common::perch_path::ParentHint;
25	  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
26
27	warning: function `open_spool` is never used
28	  --> src\common\spool.rs:65:4
29	   |
30	65 | fn open_spool(id: &str, _owlery: &Path) -> rusqlite::Result<Connection> {
31	   |    ^^^^^^^^^^
32	   |
33	   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
34
35	warning: function `check_alive` is never used
36	  --> src\owl\send.rs:37:8
37	   |
38	37 | pub fn check_alive(id: &str) {
39	   |        ^^^^^^^^^^^
40
41	warning: field `source` is never read
42	  --> src\owl\resume.rs:13:5
43	   |
44	11 | struct HookInput {
45	   |        --------- field in this struct
46	12 |     #[serde(default)]
47	13 |     source: Option<String>,
48	   |     ^^^^^^
49
50	warning: function `route_two_slice_outcome` is never used
51	   --> src\owl\echo_commune.rs:481:15
52	    |
53	481 | pub(crate) fn route_two_slice_outcome(
54	    |               ^^^^^^^^^^^^^^^^^^^^^^^
55
56	warning: function `route_two_slice` is never used
57	   --> src\owl\echo_commune.rs:745:15
58	    |
59	745 | pub(crate) fn route_two_slice(
60	    |               ^^^^^^^^^^^^^^^
61
62	warning: function `route_project_slot` is never used
63	   --> src\owl\echo_commune.rs:813:4
64	    |
65	813 | fn route_project_slot(
66	    |    ^^^^^^^^^^^^^^^^^^
67
68	warning: function `should_fire` is never used
69	   --> src\live\wrapper\echo_fire.rs:140:15
70	    |
71	140 | pub(crate) fn should_fire(sentinel: &Path, window: Duration) -> bool {
72	    |               ^^^^^^^^^^^
73
74	warning: `owl` (lib) generated 9 warnings (run `cargo fix --lib -p owl` to apply 2 suggestions)
75	    Finished `release` profile [optimized] target(s) in 11.68s
76	==> Step 4: Sync files to marketplace
77	    Ensure C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\skills exists
78	    Ensure C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\hooks exists
79	    Ensure C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\.claude-plugin exists
80	    Copy owl.exe -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt
81	    Copy skills/* -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\skills
82	    Copy hooks/* -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\hooks
83	    Copy CHANGELOG.md -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt
84	    Copy plugin.json -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\.claude-plugin
85	==> Step 5: Commit + push marketplace
86	    Committing marketplace changes
87	[main 33927ca] spt: deploy v1.11.25
88	 3 files changed, 9 insertions(+), 1 deletion(-)
89	    Pushing marketplace
90	To https://github.com/SaberMage/cplugs.git
91	   eb03327..33927ca  main -> main
92	    Marketplace HEAD: 33927caa109e1ed97aab964d6ea87e5473869074
93	==> Step 6-7: Sync new version + prune old cache
94	    Prior version: 1.11.24 (installPath leaf: 1.11.24)
95	    Create C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/.claude-plugin
96	    Create C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/skills
97	    Create C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/hooks
98	    Copy owl.exe -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25
99	    Copy skills/* -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/skills
100	    Copy hooks/* -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/hooks
101	    Copy CHANGELOG.md -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25
102	    Copy plugin.json -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/.claude-plugin
103	    Carry-over .pending-prune-* dirs from prior deploys: .pending-prune-1.11.22-1780371400
104	    ! Carry-over .pending-prune-1.11.22-1780371400 still not removable (sharing violation persists; will retry next deploy)
105	    Keep-set: 1.11.25, 1.11.24
106	    Prune candidates: 1.11.23
107	    Renamed 1.11.23 -> .pending-prune-1.11.23-1780410798
108	    ! Deferred deletion of .pending-prune-1.11.23-1780410798 (owl.exe inside still in use; carry-over cleanup will retry next deploy -- no resolver-visible stale skills because the dir name is no longer semver-shaped)
109	==> Step 8: Clean up rogue manual-install dir
110	    No manual-install dir at C:\Users\decid\.claude\plugins\spt -- nothing to clean up.
111	==> Step 9: Refresh plugin state via Claude Code CLI
112	    Running: claude plugin install spt@cplugs
113	Installing plugin "spt@cplugs"...✔ Plugin "spt@cplugs" is already installed (scope: user)
114	==> Step 9b: Patch installed_plugins.json (canonical pointer)
115	    Updated spt@cplugs[0]: version=1.11.25, installPath=C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25
116	    installed_plugins.json patched (atomic write via temp + Move-Item -Force).
117	==> Step 10: Verify installed_plugins.json reflects v1.11.25
118	    Pointer verified: spt@cplugs version=1.11.25 installPath=C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25
119
120	Deploy complete for v1.11.25.
121	Marketplace HEAD: 33927caa109e1ed97aab964d6ea87e5473869074
122	>>> Now run /reload-plugins inside Claude Code to pick up the changes. <<<
123

==> Step 1: Resolve version from plugin.json
    Current version: 1.11.24
    Bumping (patch): 1.11.24 -> 1.11.25
[main be5f2e7] chore: bump spt plugin to v1.11.25
 2 files changed, 2 insertions(+), 2 deletions(-)
    Committed bump: be5f2e7 (not pushed; plugin.json + Cargo.toml only -- CHANGELOG entry was pre-committed)
    Version: 1.11.25
    RepoRoot: C:\Users\decid\Documents\projects\claude_skill_owl
    Marketplace: C:\Users\decid\.claude\plugins\marketplaces\cplugs
    PluginDir: C:\Users\decid\.claude\plugins\spt
==> Step 3: cargo build --release
   Compiling owl v1.11.25 (C:\Users\decid\Documents\projects\claude_skill_owl)
warning: unused import: `perch_path`
 --> src\owl\cleanup.rs:4:50
  |
4 | use crate::common::{hook_output, output, owlery, perch_path, process, types};
  |                                                  ^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default

warning: unused import: `crate::common::perch_path::ParentHint`
 --> src\owl\cleanup.rs:5:5
  |
5 | use crate::common::perch_path::ParentHint;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

warning: function `open_spool` is never used
  --> src\common\spool.rs:65:4
   |
65 | fn open_spool(id: &str, _owlery: &Path) -> rusqlite::Result<Connection> {
   |    ^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default

warning: function `check_alive` is never used
  --> src\owl\send.rs:37:8
   |
37 | pub fn check_alive(id: &str) {
   |        ^^^^^^^^^^^

warning: field `source` is never read
  --> src\owl\resume.rs:13:5
   |
11 | struct HookInput {
   |        --------- field in this struct
12 |     #[serde(default)]
13 |     source: Option<String>,
   |     ^^^^^^

warning: function `route_two_slice_outcome` is never used
   --> src\owl\echo_commune.rs:481:15
    |
481 | pub(crate) fn route_two_slice_outcome(
    |               ^^^^^^^^^^^^^^^^^^^^^^^

warning: function `route_two_slice` is never used
   --> src\owl\echo_commune.rs:745:15
    |
745 | pub(crate) fn route_two_slice(
    |               ^^^^^^^^^^^^^^^

warning: function `route_project_slot` is never used
   --> src\owl\echo_commune.rs:813:4
    |
813 | fn route_project_slot(
    |    ^^^^^^^^^^^^^^^^^^

warning: function `should_fire` is never used
   --> src\live\wrapper\echo_fire.rs:140:15
    |
140 | pub(crate) fn should_fire(sentinel: &Path, window: Duration) -> bool {
    |               ^^^^^^^^^^^

warning: `owl` (lib) generated 9 warnings (run `cargo fix --lib -p owl` to apply 2 suggestions)
    Finished `release` profile [optimized] target(s) in 11.68s
==> Step 4: Sync files to marketplace
    Ensure C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\skills exists
    Ensure C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\hooks exists
    Ensure C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\.claude-plugin exists
    Copy owl.exe -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt
    Copy skills/* -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\skills
    Copy hooks/* -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\hooks
    Copy CHANGELOG.md -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt
    Copy plugin.json -> C:\Users\decid\.claude\plugins\marketplaces\cplugs\plugins\spt\.claude-plugin
==> Step 5: Commit + push marketplace
    Committing marketplace changes
[main 33927ca] spt: deploy v1.11.25
 3 files changed, 9 insertions(+), 1 deletion(-)
    Pushing marketplace
To https://github.com/SaberMage/cplugs.git
   eb03327..33927ca  main -> main
    Marketplace HEAD: 33927caa109e1ed97aab964d6ea87e5473869074
==> Step 6-7: Sync new version + prune old cache
    Prior version: 1.11.24 (installPath leaf: 1.11.24)
    Create C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/.claude-plugin
    Create C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/skills
    Create C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/hooks
    Copy owl.exe -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25
    Copy skills/* -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/skills
    Copy hooks/* -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/hooks
    Copy CHANGELOG.md -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25
    Copy plugin.json -> C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25/.claude-plugin
    Carry-over .pending-prune-* dirs from prior deploys: .pending-prune-1.11.22-1780371400
    ! Carry-over .pending-prune-1.11.22-1780371400 still not removable (sharing violation persists; will retry next deploy)
    Keep-set: 1.11.25, 1.11.24
    Prune candidates: 1.11.23
    Renamed 1.11.23 -> .pending-prune-1.11.23-1780410798
    ! Deferred deletion of .pending-prune-1.11.23-1780410798 (owl.exe inside still in use; carry-over cleanup will retry next deploy -- no resolver-visible stale skills because the dir name is no longer semver-shaped)
==> Step 8: Clean up rogue manual-install dir
    No manual-install dir at C:\Users\decid\.claude\plugins\spt -- nothing to clean up.
==> Step 9: Refresh plugin state via Claude Code CLI
    Running: claude plugin install spt@cplugs
Installing plugin "spt@cplugs"...✔ Plugin "spt@cplugs" is already installed (scope: user)
==> Step 9b: Patch installed_plugins.json (canonical pointer)
    Updated spt@cplugs[0]: version=1.11.25, installPath=C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25
    installed_plugins.json patched (atomic write via temp + Move-Item -Force).
==> Step 10: Verify installed_plugins.json reflects v1.11.25
    Pointer verified: spt@cplugs version=1.11.25 installPath=C:\Users\decid\.claude\plugins\cache\cplugs\spt\1.11.25

Deploy complete for v1.11.25.
Marketplace HEAD: 33927caa109e1ed97aab964d6ea87e5473869074
>>> Now run /reload-plugins inside Claude Code to pick up the changes. <<<


## DEPLOYED v1.11.25 ✓

- Bump commit `be5f2e7` (plugin.json + Cargo.toml).
- Marketplace pushed `33927ca` → cplugs main.
- Cache synced, `installed_plugins.json` pointer verified → 1.11.25.
- Binary handoff: prior 1.11.24 kept; old 1.11.23 deferred-pruned (owl.exe in use — retries next deploy, harmless).
- Warnings = pre-existing dead-code (route_two_slice_*, should_fire, etc.) — not from this fix.

**You run:** `/reload-plugins` to pick up changes.

Full chain done: root cause → fix `c965c4a` → CHANGELOG `b1eb8b2` → deploy `33927ca`. Debug session resolved.


<task-notification>
<task-id>b72c369kn</task-id>
Monitor event: "« spt event »"
<event><EVENT-PART seq="1/9" id="46eb81a0" type="msg" from="version-change">&lt;spt-version-changelog&gt;
  &lt;old&gt;1.11.24&lt;/old&gt;
  &lt;new&gt;1.11.25&lt;/new&gt;
  &lt;old_date&gt;2026-06-02&lt;/old_date&gt;
  &lt;new_date&gt;&lt;/new_date&gt;
  &lt;step_count&gt;1&lt;/step_count&gt;
  &lt;changelog_path&gt;$CLAUDE_PLUGIN_ROOT/CHANGELOG.md&lt;/changelog_path</EVENT-PART>
<EVENT-PART seq="2/9" id="46eb81a0">&gt;
  &lt;instructions&gt;
Render an AskUserQuestion to confirm whether the user wants to see the changelog for this SPT plugin update.

Before invoking AskUserQuestion, write one short pre-question line that names the version transition (and dates if both &lt;old_date&gt; and &lt;new_date&gt; are non-empty), e.g. &quot;SPT plugin</EVENT-PART>
<EVENT-PART seq="3/9" id="46eb81a0"> updated v1.11.24 → v1.11.25. Print changelog?&quot;.

Then invoke AskUserQuestion with EXACTLY these three options (labels verbatim, do not paraphrase):

  1. &quot;Yes, full changelog&quot; — On selection: read $CLAUDE_PLUGIN_ROOT/CHANGELOG.md and print every H2 section where 1.11.24 &lt; version &lt;= 1.11.25, verbatim markd</EVENT-PART>
<EVENT-PART seq="4/9" id="46eb81a0">own. Preserve the original H2 lines, bullet structure, and the user-facing H3 subsections (Added / Changed / Fixed / Removed / Deprecated / Security / Reverted). OMIT any &quot;### BTS&quot; subsection entirely — those are behind-the-scenes notes the user does not want to see. If a version has only a &quot;### BTS&quot; subsection with no us</EVENT-PART>
<EVENT-PART seq="5/9" id="46eb81a0">er-facing content, render the H2 header and date alone with a single line &quot;(no user-facing changes this release)&quot;. Render in the order they appear in the file (newest first). Do not summarize, do not paraphrase the bullets you do show.

  2. &quot;Yes, highlights only&quot; — On selection: read $CLAUDE_PLUGIN_ROOT/CHANGELOG.m</EVENT-PART>
<EVENT-PART seq="6/9" id="46eb81a0">d and synthesize 2-5 highlight bullets across the H2 sections where 1.11.24 &lt; version &lt;= 1.11.25. Draw ONLY from the &quot;### Added&quot;, &quot;### Changed&quot;, &quot;### Fixed&quot;, &quot;### Removed&quot;, &quot;### Deprecated&quot;, &quot;### Security&quot;, and &quot;### Reverted&quot; subsections. Do NOT draw from &quot;### BTS</EVENT-PART>
<EVENT-PART seq="7/9" id="46eb81a0">&quot; subsections — those are behind-the-scenes notes and must never appear in highlights. Pick the most impactful user-facing items across the range. Append exactly this pointer at the end: &quot;See $CLAUDE_PLUGIN_ROOT/CHANGELOG.md for full detail.&quot;

  3. &quot;Skip&quot; — On selection: take no action. Acknowledge briefly (&</EVENT-PART>
<EVENT-PART seq="8/9" id="46eb81a0">quot;OK, skipping.&quot;) and continue with the user's prior intent.

If the user provides freeform input via AskUserQuestion's &quot;Other&quot; option, treat all continuation phrases (later / not now / i
...(truncated)</event>
</task-notification>


Version-change event: SPT plugin reloaded v1.11.24 → v1.11.25.

SPT plugin updated v1.11.24 → v1.11.25. Print changelog?


AskUserQuestion

Question: SPT plugin updated v1.11.24 -> v1.11.25. Print changelog?

Choices:
Print every user-facing changelog section for this update verbatim.
Synthesize 2-5 highlight bullets of the most impactful user-facing changes.
Take no action and continue.


Your questions have been answered: "SPT plugin updated v1.11.24 -> v1.11.25. Print changelog?"="Skip". You can now continue with these answers in mind.

Question: SPT plugin updated v1.11.24 -> v1.11.25. Print changelog?

Choices:
Print every user-facing changelog section for this update verbatim.
Synthesize 2-5 highlight bullets of the most impactful user-facing changes.
Take no action and continue.


OK, skipping.

v1.11.25 live. FIRE-EC empty-slices fix shipped end-to-end. Done.


<local-command-caveat>Caveat: The messages below were generated by the user while running local commands. DO NOT respond to these messages or otherwise consider them in your response unless the user explicitly asks you to.</local-command-caveat>


<command-name>/reload-plugins</command-name>
            <command-message>reload-plugins</command-message>
            <command-args></command-args>


<local-command-stdout>Reloaded: 6 plugins · 0 skills · 39 agents · 9 hooks · 1 plugin MCP server · 1 plugin LSP server</local-command-stdout>


<bash-input>powershell -Command "Start-Process powershell -Verb RunAs -ArgumentList '-Command','Set-NetFirewallProfile -All -NotifyOnListen False'"</bash-input>


<bash-stdout>(Bash completed with no output)</bash-stdout><bash-stderr></bash-stderr>


please fix the `/self-clear` skill: -it isn't bringing the correct window into focus. it seems to focus the first window of whichever program it targets, instead of actually focusing the appropriate parent PID of the claude session that invokes it -10s delay can be shortened to 200ms. -change 2nd sendkeys to simply `Proceed with next steps[enter]`


- autoplan: Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk
and runs them sequentially with auto-decisions using 6 decision principles. Surfaces
taste decisions (close approaches, borderline scope, codex disagreements) at a final
approval gate. One command, fully reviewed plan out.
Use when asked to "auto review", "autoplan", "run all reviews", "review this plan
automatically", or "make the decisions for me".
Proactively suggest when the user has a plan file and wants to run the full review
gauntlet without answering 15-30 intermediate questions. (gstack)
- benchmark: Performance regression detection using the browse daemon. Establishes
baselines for page load times, Core Web Vitals, and resource sizes.
Compares before/after on every PR. Tracks performance trends over time.
Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals",
"bundle size", "load time". (gstack)
- browse: Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with
elements, verify page state, diff before/after actions, take annotated screenshots, check
responsive layouts, test forms and uploads, handle dialogs, and assert element states.
~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a
user flow, or file a bug with evidence. Use when asked to "open in browser", "test the
site", "take a screenshot", or "dogfood this". (gstack)
- canary: Post-deploy canary monitoring. Watches the live app for console errors,
performance regressions, and page failures using the browse daemon. Takes
periodic screenshots, compares against pre-deploy baselines, and alerts
on anomalies. Use when: "monitor deploy", "canary", "post-deploy check",
"watch production", "verify deploy". (gstack)
- careful: Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE,
force-push, git reset --hard, kubectl delete, and similar destructive operations.
User can override each warning. Use when touching prod, debugging live systems,
or working in a shared environment. Use when asked to "be careful", "safety mode",
"prod mode", or "careful mode". (gstack)
- caveman: Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
- ccs-delegation: Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
- checkpoint: Save and resume working state checkpoints. Captures git state, decisions made,
and remaining work so you can pick up exactly where you left off — even across
Conductor workspace handoffs between branches.
Use when asked to "checkpoint", "save progress", "where was I", "resume",
"what was I working on", or "pick up where I left off".
Proactively suggest when a session is ending, the user is switching context,
or before a long break. (gstack)
- codex: OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via
codex review with pass/fail gate. Challenge: adversarial mode that tries to break
your code. Consult: ask codex anything with session continuity for follow-ups.
The "200 IQ autistic developer" second opinion. Use when asked to "codex review",
"codex challenge", "ask codex", "second opinion", or "consult codex". (gstack)
- connect-chrome: Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in.
Opens a visible browser window where you can watch every action in real time.
The sidebar shows a live activity feed and chat. Anti-bot stealth built in.
Use when asked to "open gstack browser", "launch browser", "connect chrome",
"open chrome", "real browser", "launch chrome", "side panel", or "control my browser".
- cso: Chief Security Officer mode. Infrastructure-first security audit: secrets archaeology,
dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain
scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification.
Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep
scan, 2/10 bar). Trend tracking across audit runs.
Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review". (gstack)
- design-consultation: Design consultation: understands your product, researches the landscape, proposes a
complete design system (aesthetic, typography, color, layout, spacing, motion), and
generates font+color preview pages. Creates DESIGN.md as your project's design source
of truth. For existing sites, use /plan-design-review to infer the system instead.
Use when asked to "design system", "brand guidelines", or "create DESIGN.md".
Proactively suggest when starting a new project's UI with no existing
design system or DESIGN.md. (gstack)
- design-html: Design finalization: generates production-quality Pretext-native HTML/CSS.
Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review,
design review context from /plan-design-review, or from scratch with a user
description. Text actually reflows, heights are computed, layouts are dynamic.
30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns
for each design type. Use when: "finalize this design", "turn this into HTML",
"build me a page", "implement this design", or after any planning skill.
Proactively suggest when user has approved a design or has a plan ready. (gstack)
- design-review: Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems,
AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues
in source code, committing each fix atomically and re-verifying with before/after
screenshots. For plan-mode design review (before implementation), use /plan-design-review.
Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish".
Proactively suggest when the user mentions visual inconsistencies or
wants to polish the look of a live site. (gstack)
- design-shotgun: Design shotgun: generate multiple AI design variants, open a comparison board,
collect structured feedback, and iterate. Standalone design exploration you can
run anytime. Use when: "explore designs", "show me options", "design variants",
"visual brainstorm", or "I don't like how this looks".
Proactively suggest when the user describes a UI feature but hasn't seen
what it could look like. (gstack)
- devex-review: Live developer experience audit. Uses the browse tool to actually TEST the
developer experience: navigates docs, tries the getting started flow, times
TTHW, screenshots error messages, evaluates CLI help text. Produces a DX
scorecard with evidence. Compares against /plan-devex-review scores if they
exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to
"test the DX", "DX audit", "developer experience test", or "try the
onboarding". Proactively suggest after shipping a developer-facing feature. (gstack)
- diagnose: Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
- document-release: Post-ship documentation update. Reads all project docs, cross-references the
diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped,
polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when
asked to "update the docs", "sync documentation", or "post-ship docs".
Proactively suggest after a PR is merged or code is shipped. (gstack)
- find-skills: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
- freeze: Restrict file edits to a specific directory for the session. Blocks Edit and
Write outside the allowed path. Use when debugging to prevent accidentally
"fixing" unrelated code, or when you want to scope changes to one module.
Use when asked to "freeze", "restrict edits", "only edit this folder",
or "lock down edits". (gstack)
- grill-me: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- grill-with-docs: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- gsd-add-tests: Generate tests for a completed phase based on UAT criteria and implementation
- gsd-ai-integration-phase: Generate an AI-SPEC.md design contract for phases that involve building AI systems.
- gsd-audit-fix: Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
- gsd-audit-milestone: Audit milestone completion against original intent before archiving
- gsd-audit-uat: Cross-phase audit of all outstanding UAT and verification items
- gsd-autonomous: Run all remaining phases autonomously — discuss→plan→execute per phase
- gsd-capture: Capture ideas, tasks, notes, and seeds to their destination
- gsd-cleanup: Archive accumulated phase directories from completed milestones
- gsd-code-review: Review source files changed during a phase for bugs, security issues, and code quality problems
- gsd-complete-milestone: Archive completed milestone and prepare for next version
- gsd-config: Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile
- gsd-debug: Systematic debugging with persistent state across context resets
- gsd-discuss-phase: Gather phase context through adaptive questioning before planning.
- gsd-docs-update: Generate or update project documentation verified against the codebase
- gsd-eval-review: Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
- gsd-execute-phase: Execute all plans in a phase with wave-based parallelization
- gsd-explore: Socratic ideation and idea routing — think through ideas before committing to plans
- gsd-extract-learnings: Extract decisions, lessons, patterns, and surprises from completed phase artifacts
- gsd-fast: Execute a trivial task inline — no subagents, no planning overhead
- gsd-forensics: Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
- gsd-graphify: Build, query, and inspect the project knowledge graph in .planning/graphs/
- gsd-health: Diagnose planning directory health and optionally repair issues
- gsd-help: Show available GSD commands and usage guide
- gsd-import: Ingest external plans with conflict detection against project decisions before writing anything.
- gsd-inbox: Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
- gsd-ingest-docs: Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo.
- gsd-manager: Interactive command center for managing multiple phases from one terminal
- gsd-map-codebase: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
- gsd-milestone-summary: Generate a comprehensive project summary from milestone artifacts for team onboarding and review
- gsd-mvp-phase: Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase
- gsd-new-milestone: Start a new milestone cycle — update PROJECT.md and route to requirements
- gsd-new-project: Initialize a new project with deep context gathering and PROJECT.md
- gsd-ns-context: codebase intelligence | map graphify docs learnings
- gsd-ns-ideate: exploration capture | explore sketch spike spec capture
- gsd-ns-manage: config workspace | workstreams thread update ship inbox
- gsd-ns-project: project lifecycle | milestones audits summary
- gsd-ns-review: quality gates | code review debug audit security eval ui
- gsd-ns-workflow: workflow | discuss plan execute verify phase progress
- gsd-pause-work: Create context handoff when pausing work mid-phase
- gsd-phase: CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases
- gsd-plan-phase: Create detailed phase plan (PLAN.md) with verification loop
- gsd-plan-review-convergence: Cross-AI plan convergence loop — replan with review feedback until no HIGH concerns remain.
- gsd-pr-branch: Create a clean PR branch by filtering out .planning/ commits — ready for code review
- gsd-profile-user: Generate developer behavioral profile and create Claude-discoverable artifacts
- gsd-progress: Check progress, advance workflow, or dispatch freeform intent — the unified GSD situational command
- gsd-quick: Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
- gsd-resume-work: Resume work from previous session with full context restoration
- gsd-review: Request cross-AI peer review of phase plans from external AI CLIs
- gsd-review-backlog: Review and promote backlog items to active milestone
- gsd-secure-phase: Retroactively verify threat mitigations for a completed phase
- gsd-settings: Configure GSD workflow toggles and model profile
- gsd-ship: Create PR, run review, and prepare for merge after verification passes
- gsd-sketch: Sketch UI/design ideas with throwaway HTML mockups, or propose what to sketch next (frontier mode)
- gsd-spec-phase: Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.
- gsd-spike: Spike an idea through experiential exploration, or propose what to spike next (frontier mode)
- gsd-stats: Display project statistics — phases, plans, requirements, git metrics, and timeline
- gsd-surface: Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall
- gsd-thread: Manage persistent context threads for cross-session work
- gsd-ui-phase: Generate UI design contract (UI-SPEC.md) for frontend phases
- gsd-ui-review: Retroactive 6-pillar visual audit of implemented frontend code
- gsd-ultraplan-phase: [BETA] Offload plan phase to Claude Code's ultraplan cloud; review in browser and import back.
- gsd-undo: Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
- gsd-update: Update GSD to latest version with changelog display
- gsd-validate-phase: Retroactively audit and fill Nyquist validation gaps for a completed phase
- gsd-verify-work: Validate built features through conversational UAT
- gsd-workspace: Manage GSD workspaces — create, list, or remove isolated workspace environments
- gsd-workstreams: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
- gstack: Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with
elements, verify state, diff before/after, take annotated screenshots, test responsive
layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or
test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
- gstack-upgrade: Upgrade gstack to the latest version. Detects global vs vendored install,
runs the upgrade, and shows what's new. Use when asked to "upgrade gstack",
"update gstack", or "get latest version".
- guard: Full safety mode: destructive command warnings + directory-scoped edits.
Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with
/freeze (blocks edits outside a specified directory). Use for maximum safety
when touching prod or debugging live systems. Use when asked to "guard mode",
"full safety", "lock it down", or "maximum safety". (gstack)
- handoff: Compact the current conversation into a handoff document for another agent to pick up.
- health: Code quality dashboard. Wraps existing project tools (type checker, linter,
test runner, dead code detector, shell linter), computes a weighted composite
0-10 score, and tracks trends over time. Use when: "health check",
"code quality", "how healthy is the codebase", "run all checks",
"quality score". (gstack)
- improve-codebase-architecture: Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
- investigate: Systematic debugging with root cause investigation. Four phases: investigate,
analyze, hypothesize, implement. Iron Law: no fixes without root cause.
Use when asked to "debug this", "fix this bug", "why is this broken",
"investigate this error", or "root cause analysis".
Proactively invoke this skill (do NOT debug directly) when the user reports
errors, 500 errors, stack traces, unexpected behavior, "it was working
yesterday", or is troubleshooting why something stopped working. (gstack)
- land-and-deploy: Land and deploy workflow. Merges the PR, waits for CI and deploy,
verifies production health via canary checks. Takes over after /ship
creates the PR. Use when: "merge", "land", "deploy", "merge and verify",
"land it", "ship it to production". (gstack)
- learn: Manage project learnings. Review, search, prune, and export what gstack
has learned across sessions. Use when asked to "what have we learned",
"show learnings", "prune stale learnings", or "export learnings".
Proactively suggest when the user asks about past patterns or wonders
"didn't we fix this before?"
- mux-send: Send keystrokes to a psmux terminal session. Use when the user says "send to",
"type in", "send keys to", "mux send", or wants to send input to another terminal
session by name.
- office-hours: YC Office Hours — two modes. Startup mode: six forcing questions that expose
demand reality, status quo, desperate specificity, narrowest wedge, observation,
and future-fit. Builder mode: design thinking brainstorming for side projects,
hackathons, learning, and open source. Saves a design doc.
Use when asked to "brainstorm this", "I have an idea", "help me think through
this", "office hours", or "is this worth building".
Proactively invoke this skill (do NOT answer directly) when the user describes
a new product idea, asks whether something is worth building, wants to think
through design decisions for something that doesn't exist yet, or is exploring
a concept before any code is written.
Use before /plan-ceo-review or /plan-eng-review. (gstack)
- open-gstack-browser: Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in.
Opens a visible browser window where you can watch every action in real time.
The sidebar shows a live activity feed and chat. Anti-bot stealth built in.
Use when asked to "open gstack browser", "launch browser", "connect chrome",
"open chrome", "real browser", "launch chrome", "side panel", or "control my browser".
- pair-agent: Pair a remote AI agent with your browser. One command generates a setup key and
prints instructions the other agent can follow to connect. Works with OpenClaw,
Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent
gets its own tab with scoped access (read+write by default, admin on request).
Use when asked to "pair agent", "connect agent", "share browser", "remote browser",
"let another agent use my browser", or "give browser access". (gstack)
- plan-ceo-review: CEO/founder-mode plan review. Rethink the problem, find the 10-star product,
challenge premises, expand scope when it creates a better product. Four modes:
SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick
expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
Use when asked to "think bigger", "expand scope", "strategy review", "rethink this",
or "is this ambitious enough".
Proactively suggest when the user is questioning scope or ambition of a plan,
or when the plan feels like it could be thinking bigger. (gstack)
- plan-design-review: Designer's eye plan review — interactive, like CEO and Eng review.
Rates each design dimension 0-10, explains what would make it a 10,
then fixes the plan to get there. Works in plan mode. For live site
visual audits, use /design-review. Use when asked to "review the design plan"
or "design critique".
Proactively suggest when the user has a plan with UI/UX components that
should be reviewed before implementation. (gstack)
- plan-devex-review: Interactive developer experience plan review. Explores developer personas,
benchmarks against competitors, designs magical moments, and traces friction
points before scoring. Three modes: DX EXPANSION (competitive advantage),
DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only).
Use when asked to "DX review", "developer experience audit", "devex review",
or "API design review".
Proactively suggest when the user has a plan for developer-facing products
(APIs, CLIs, SDKs, libraries, platforms, docs). (gstack)
- plan-eng-review: Eng manager-mode plan review. Lock in the execution plan — architecture,
data flow, diagrams, edge cases, test coverage, performance. Walks through
issues interactively with opinionated recommendations. Use when asked to
"review the architecture", "engineering review", or "lock in the plan".
Proactively suggest when the user has a plan or design doc and is about to
start coding — to catch architecture issues before implementation. (gstack)
- propose-issue: Challenge an issue statement before fixing it. Probes scope, root cause, and assumptions
through interactive questioning grounded in the codebase. Use when the user says "propose issue",
"challenge this bug", "question this fix", "is this the right problem", or wants to pressure-test
a problem statement before jumping to implementation.
- qa: Systematically QA test a web application and fix bugs found. Runs QA testing,
then iteratively fixes bugs in source code, committing each fix atomically and
re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs",
"test and fix", or "fix what's broken".
Proactively suggest when the user says a feature is ready for testing
or asks "does this work?". Three tiers: Quick (critical/high only),
Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores,
fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack)
- qa-only: Report-only QA testing. Systematically tests a web application and produces a
structured report with health score, screenshots, and repro steps — but never
fixes anything. Use when asked to "just report bugs", "qa report only", or
"test but don't fix". For the full test-fix-verify loop, use /qa instead.
Proactively suggest when the user wants a bug report without any code changes. (gstack)
- retro: Weekly engineering retrospective. Analyzes commit history, work patterns,
and code quality metrics with persistent history and trend tracking.
Team-aware: breaks down per-person contributions with praise and growth areas.
Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".
Proactively suggest at the end of a work week or sprint. (gstack)
- review: Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust
boundary violations, conditional side effects, and other structural issues. Use when
asked to "review this PR", "code review", "pre-landing review", or "check my diff".
Proactively suggest when the user is about to merge or land code changes. (gstack)
- screenshot-capture: Capture, process, and analyze screenshots of any running application on Windows 10/11. Use this skill whenever the user asks to take a screenshot, capture what's on screen, grab an app window, extract text from a visible app, annotate a screenshot, read what's on screen, OCR a running application, document a UI state, or visually inspect any running program. Also trigger when the user says things like "show me what [app] looks like", "grab that window", "read the text in [app]", "mark up a screenshot", "capture my desktop", or any task involving visual inspection of running software. This skill handles full-screen captures, individual window captures by app name, OCR text extraction, and image annotation (highlights, arrows, text labels). Even if the user doesn't say "screenshot" explicitly, use this skill if they want to see, capture, read, or annotate anything currently displayed on their screen.
- self-clear: Clear the calling agent's own Claude Code context with /clear, then re-seed it with a user note so it wakes and resumes work after the wipe. Use when the user says "self-clear", "/self-clear", "clear myself", "clear and continue", or "reset my context and keep going".
- setup-browser-cookies: Import cookies from your real Chromium browser into the headless browse session.
Opens an interactive picker UI where you select which cookie domains to import.
Use before QA testing authenticated pages. Use when asked to "import cookies",
"login to the site", or "authenticate the browser". (gstack)
- setup-deploy: Configure deployment settings for /land-and-deploy. Detects your deploy
platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom),
production URL, health check endpoints, and deploy status commands. Writes
the configuration to CLAUDE.md so all future deploys are automatic.
Use when: "setup deploy", "configure deployment", "set up land-and-deploy",
"how do I deploy with gstack", "add deploy config".
- ship: Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION,
update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy",
"push to main", "create a PR", "merge and push", or "get it deployed".
Proactively invoke this skill (do NOT push/PR directly) when the user says code
is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)
- to-prd: Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
- trace: Find old conversations in Claude Code session history. Use when the user says
"find the conversation where", "when did we discuss", "trace back to", or wants
to locate a past session by topic, command, commit, or keyword.
- traceable-reqs: traceable-reqs
- unfreeze: Clear the freeze boundary set by /freeze, allowing edits to all directories
again. Use when you want to widen edit scope without ending the session.
Use when asked to "unfreeze", "unlock edits", "remove freeze", or
"allow all edits". (gstack)
- win-marketplace-add: Add a plugin marketplace on Windows, bypassing the EBUSY rename bug. Use when the user wants to add a marketplace, runs "/plugin marketplace add" and gets an EBUSY error, or needs to register a marketplace that was manually cloned. Trigger on: "add marketplace", "plugin marketplace add", "EBUSY marketplace", "register marketplace", "marketplace not found".
- write-a-skill: Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
- ccs: Delegate task with intelligent profile selection [AUTO ENHANCE]
- ccs:continue: Continue last CCS delegation session [AUTO ENHANCE]
- deep-research: Deep research harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report. - When the user wants a deep, multi-source, fact-checked research report on any topic. BEFORE invoking, check if the question is specific enough to research directly — if underspecified (e.g., "what car to buy" without budget/use-case/region), ask 2-3 clarifying questions to narrow scope. Then pass the refined question as args, weaving the answers in.
- frontend-design:frontend-design: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
- spt:clear-psyche: Clear stored Psyche context. Use when the user says "clear psyche",
"reset psyche context", or wants to wipe a Psyche's saved state.
- spt:commune: Send a communal update to your Psyche. Use when the user says "commune",
"update psyche", or wants to sync context with their Psyche companion.
- spt:force-stop: Force-stop an SPT agent -- ready agent or live agent (with its
Psyche). Use when the user says "stop listening", "stop owl", "kill live
agent", "force stop", "tear down perch", or "immediately terminate".
Session-aware: a live session (or a target with `live:true` in info.json)
routes through `$LIVE stop` (3-step kill including Psyche teardown); a
ready agent routes through `$OWL stop`.
- spt:list-agents: Unified listing for SPT agents -- ready agents, live agents, and Psyche
processes. Use when the user says "list agents", "who's live", "who's
listening", "show psyches", "show active listeners", or wants a roster of
active perches. Session-aware: defaults to live agents in a live session,
ready agents otherwise. Pass `--psyches` to list Psyche processes
instead.
- spt:live: Run a live agent session. For past sessions, restores a summarized context.

EXPLICIT START phrases (route to /spt:live <id>):
- "live as"
- "start live"
- "go live"
- "start a live agent"

AUTO-RESUME phrases (route to /spt:live --auto, resumes most-recently-active live agent):
- continue live work
- resume live work
- continue live agent
- resume live agent
- live agent continue
- live agent resume
- live work continue
- live work resume

Does NOT route here (too ambiguous — require BOTH "live" AND ("agent" or "work")):
- "keep going"
- "resume work"
- "continue" (bare)
- spt:new-alarm: Schedule a one-shot timed alarm delivered as TIMED PULSE. Use when the user
says "remind me", "check back in", "set an alarm", "wake me when", or wants a
delayed notification.
- spt:psyche-sync-setup: Enable cross-machine Psyche context sync via a private GitHub repo
(spt-agent-storage). Drives install + auth checks for the `gh` CLI,
creates the repo via `gh repo create --private`, wires it as the
`origin` remote for every existing agent/project worktree, and
seeds the remote with `git push --all`. Idempotent — running again
when already enabled reports current status.

Use when the user says "enable cross-machine sync", "set up psyche
sync", "back up my agent context to GitHub", or runs the skill
directly via /spt:psyche-sync-setup.
- spt:ready: Enable inter-agent messaging for the current session.
Use when the user says "listen as", "ready as", or wants to receive inter-agent messages.
- spt:revive: Restart a live agent with new generation. Use when the user says "revive",
"restart live agent", or wants to refresh a live agent's session.
- spt:send: Send a message to another SPT agent. Use when the user says "send to",
"message", "tell <agent>", or wants to communicate with another agent.
- spt:signoff: Graceful live agent shutdown with final context summary. Use when the user
says "sign off", "graceful stop", or wants to cleanly end a live session.
- spt:whoami: Check which owl agent belongs to the current session. Use when the user asks
"which agent am I?", "what's my owl name?", or when you need to discover your
own perch identity.
- caveman:caveman: Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
- caveman:caveman-commit: Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
- caveman:caveman-help: Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
- caveman:caveman-review: Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
- caveman:compress: Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"
- everything:search: Instantly search files and folders on Windows via voidtools Everything 1.5a HTTP JSON API. Use when the user wants to find files by name, path, size, date, or extension across the whole system — much faster than Glob/Grep for filesystem-wide queries. Triggers on "find file", "where is", "locate", "search my drive", "find all .ext files", "everything search".
- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- verify: Verify that a code change actually does what it's supposed to by running the app and observing behavior. Use when asked to verify a PR, confirm a fix works, test a change manually, check that a feature works, or validate local changes before pushing.
- code-review: Review the current diff for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud). Pass --comment to post findings as inline PR comments, or --fix to apply the findings to the working tree after the review.
- simplify: Review the changed code for reuse, simplification, efficiency, and altitude cleanups, then apply the fixes. Quality only — it does not hunt for bugs; use /code-review for that.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo). Omit the interval to let the model self-pace. - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled remote agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring remote agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements).
TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project.
SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML.
- run: Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a pull request
- security-review: Complete a security review of the pending changes on the current branch

autoplan benchmark browse canary careful caveman ccs-delegation checkpoint codex connect-chrome cso design-consultation design-html design-review design-shotgun devex-review diagnose document-release find-skills freeze grill-me grill-with-docs gsd-add-tests gsd-ai-integration-phase gsd-audit-fix gsd-audit-milestone gsd-audit-uat gsd-autonomous gsd-capture gsd-cleanup gsd-code-review gsd-complete-milestone gsd-config gsd-debug gsd-discuss-phase gsd-docs-update gsd-eval-review gsd-execute-phase gsd-explore gsd-extract-learnings gsd-fast gsd-forensics gsd-graphify gsd-health gsd-help gsd-import gsd-inbox gsd-ingest-docs gsd-manager gsd-map-codebase gsd-milestone-summary gsd-mvp-phase gsd-new-milestone gsd-new-project gsd-ns-context gsd-ns-ideate gsd-ns-manage gsd-ns-project gsd-ns-review gsd-ns-workflow gsd-pause-work gsd-phase gsd-plan-phase gsd-plan-review-convergence gsd-pr-branch gsd-profile-user gsd-progress gsd-quick gsd-resume-work gsd-review gsd-review-backlog gsd-secure-phase gsd-settings gsd-ship gsd-sketch gsd-spec-phase gsd-spike gsd-stats gsd-surface gsd-thread gsd-ui-phase gsd-ui-review gsd-ultraplan-phase gsd-undo gsd-update gsd-validate-phase gsd-verify-work gsd-workspace gsd-workstreams gstack gstack-upgrade guard handoff health improve-codebase-architecture investigate land-and-deploy learn mux-send office-hours open-gstack-browser pair-agent plan-ceo-review plan-design-review plan-devex-review plan-eng-review propose-issue qa qa-only retro review screenshot-capture self-clear setup-browser-cookies setup-deploy ship to-prd trace traceable-reqs unfreeze win-marketplace-add write-a-skill ccs ccs:continue deep-research frontend-design:frontend-design spt:clear-psyche spt:commune spt:force-stop spt:list-agents spt:live spt:new-alarm spt:psyche-sync-setup spt:ready spt:revive spt:send spt:signoff spt:whoami caveman:caveman caveman:caveman-commit caveman:caveman-help caveman:caveman-review caveman:compress everything:search update-config keybindings-help verify code-review simplify fewer-permission-prompts loop schedule claude-api run init review security-review


please fix the `/self-clear` skill: -it isn't bringing the correct window into focus. it seems to focus the first window of whichever program it targets, instead of actually focusing the appropriate p…


Fix /self-clear: window focus (target parent-PID window, not first window of program), 10s→200ms, 2nd sendkeys → `Proceed with next steps[enter]`.

Locating skill files first.


Bash

ls "C:/Users/decid/.claude/skills/self-clear/" 2>/dev/null; echo "---repo---"; ls "C:/Users/decid/Documents/projects/claude_skill_owl/plugin/spt/skills/self-clear/" 2>/dev/null; echo "---glob---"; find "C:/Users/decid/.claude/skills/self-clear" "C:/Users/decid/Documents/projects/claude_skill_owl/plugin/spt/skills/self-clear" -type f 2>/dev/null

Locate self-clear skill files


SKILL.md
scripts
---repo---
---glob---
C:/Users/decid/.claude/skills/self-clear/scripts/self-clear.ps1
C:/Users/decid/.claude/skills/self-clear/SKILL.md


Standalone skill (not in this repo) — GSD repo-enforcement N/A. Reading both files.


1	# self-clear.ps1 — one-shot self-clear + delayed self-wake.
2	#
3	# Order (per design):
4	#   1. Resolve this session's agent_id via `owl whoami` (context-independent; survives /clear).
5	#   2. Focus the calling agent's terminal window (walk parents until one owns a window).
6	#   3. Type "/clear" + Enter  — QUEUED; fires only when this agent's turn ends.
7	#   4. Spawn a DETACHED waker that waits 10s, re-foregrounds the terminal, THEN
8	#      TYPES the self-note as a fresh user prompt + Enter.
9	#
10	# Why detached + delayed: a blocking sleep here would hold the turn open, so /clear
11	# could never fire. The waker must outlive the turn. The 10s gap lets the turn end
12	# and /clear wipe the context first.
13	#
14	# Why TYPE the note (not `owl send`): after /clear the session sits IDLE awaiting user
15	# input. A spooled owl message cannot self-start a turn — it surfaces only during an
16	# already-active turn (PreToolUse hook) or in a live Monitor stream (whose buffer /clear
17	# wipes). So the prior "arrives as a waking poll message" design never woke the agent.
18	# A typed prompt + Enter deterministically starts a fresh turn AND is the re-seed.
19	$ErrorActionPreference = 'Stop'
20
21	# --- 1. Resolve agent_id ---
22	$owl = $env:OWL
23	if (-not $owl) { Write-Error 'OWL env not set — restart the session so the SessionStart hook runs.'; exit 1 }
24	$who = & $owl whoami 2>&1 | Out-String
25	if ($who -notmatch 'WHOAMI:([^\s]+)') {
26	  Write-Error "No perch for this session (whoami: $($who.Trim())). Run /spt:ready or /spt:live first — NOT clearing."
27	  exit 2
28	}
29	$id = $matches[1]
30
31	# --- 2. Focus the terminal window ---
32	Add-Type @'
33	using System;
34	using System.Runtime.InteropServices;
35	public class SC {
36	  [DllImport("user32.dll")] public static extern bool SetForegroundWindow(IntPtr h);
37	  [DllImport("user32.dll")] public static extern bool ShowWindow(IntPtr h, int n);
38	  [DllImport("user32.dll")] public static extern bool IsIconic(IntPtr h);
39	}
40	'@
41	$cur = $PID; $hwnd = [IntPtr]::Zero; $winpid = 0
42	for ($i = 0; $i -lt 8; $i++) {
43	  $ci = Get-CimInstance Win32_Process -Filter "ProcessId=$cur" -ErrorAction SilentlyContinue
44	  if (-not $ci) { break }
45	  $proc = Get-Process -Id $cur -ErrorAction SilentlyContinue
46	  if ($proc -and $proc.MainWindowHandle -ne [IntPtr]::Zero) { $hwnd = $proc.MainWindowHandle; $winpid = $cur; break }
47	  $cur = $ci.ParentProcessId
48	}
49	if ($hwnd -eq [IntPtr]::Zero) { Write-Error 'No ancestor window found in 8 hops.'; exit 3 }
50	if ([SC]::IsIconic($hwnd)) { [SC]::ShowWindow($hwnd, 9) | Out-Null }  # 9 = SW_RESTORE
51	[SC]::SetForegroundWindow($hwnd) | Out-Null
52	$ws = New-Object -ComObject WScript.Shell
53	try { $ws.AppActivate($winpid) | Out-Null } catch {}
54
55	# --- 3. Type /clear + Enter (queued; processes at turn-end) ---
56	Start-Sleep -Milliseconds 400
57	$ws.SendKeys('/clear')
58	Start-Sleep -Milliseconds 150
59	$ws.SendKeys('{ENTER}')
60
61	# --- 4. Detached delayed waker (10s) — re-foregrounds + TYPES the note as a fresh prompt ---
62	$hptr = $hwnd.ToInt64()
63	$note = 'NOTE FROM THE USER: proceed with next steps.'
64	$inner = @"
65	Start-Sleep -Seconds 10
66	Add-Type @'
67	using System;
68	using System.Runtime.InteropServices;
69	public class SCW {
70	  [DllImport("user32.dll")] public static extern bool SetForegroundWindow(IntPtr h);
71	  [DllImport("user32.dll")] public static extern bool ShowWindow(IntPtr h, int n);
72	  [DllImport("user32.dll")] public static extern bool IsIconic(IntPtr h);
73	}
74	'@
75	`$h = [IntPtr]$hptr
76	if ([SCW]::IsIconic(`$h)) { [SCW]::ShowWindow(`$h, 9) | Out-Null }
77	[SCW]::SetForegroundWindow(`$h) | Out-Null
78	`$ws = New-Object -ComObject WScript.Shell
79	try { `$ws.AppActivate($winpid) | Out-Null } catch {}
80	Start-Sleep -Milliseconds 400
81	`$ws.SendKeys('$note')
82	Start-Sleep -Milliseconds 150
83	`$ws.SendKeys('{ENTER}')
84	"@
85	$enc = [Convert]::ToBase64String([Text.Encoding]::Unicode.GetBytes($inner))
86	Start-Process -FilePath 'pwsh' -ArgumentList '-NoProfile','-NonInteractive','-EncodedCommand',$enc -WindowStyle Hidden | Out-Null
87
88	"SELF-CLEAR armed: id=$id winpid=$winpid hwnd=$hwnd — /clear queued; self-note typed in ~10s"
89

# self-clear.ps1 — one-shot self-clear + delayed self-wake.
#
# Order (per design):
#   1. Resolve this session's agent_id via `owl whoami` (context-independent; survives /clear).
#   2. Focus the calling agent's terminal window (walk parents until one owns a window).
#   3. Type "/clear" + Enter  — QUEUED; fires only when this agent's turn ends.
#   4. Spawn a DETACHED waker that waits 10s, re-foregrounds the terminal, THEN
#      TYPES the self-note as a fresh user prompt + Enter.
#
# Why detached + delayed: a blocking sleep here would hold the turn open, so /clear
# could never fire. The waker must outlive the turn. The 10s gap lets the turn end
# and /clear wipe the context first.
#
# Why TYPE the note (not `owl send`): after /clear the session sits IDLE awaiting user
# input. A spooled owl message cannot self-start a turn — it surfaces only during an
# already-active turn (PreToolUse hook) or in a live Monitor stream (whose buffer /clear
# wipes). So the prior "arrives as a waking poll message" design never woke the agent.
# A typed prompt + Enter deterministically starts a fresh turn AND is the re-seed.
$ErrorActionPreference = 'Stop'

# --- 1. Resolve agent_id ---
$owl = $env:OWL
if (-not $owl) { Write-Error 'OWL env not set — restart the session so the SessionStart hook runs.'; exit 1 }
$who = & $owl whoami 2>&1 | Out-String
if ($who -notmatch 'WHOAMI:([^\s]+)') {
  Write-Error "No perch for this session (whoami: $($who.Trim())). Run /spt:ready or /spt:live first — NOT clearing."
  exit 2
}
$id = $matches[1]

# --- 2. Focus the terminal window ---
Add-Type @'
using System;
using System.Runtime.InteropServices;
public class SC {
  [DllImport("user32.dll")] public static extern bool SetForegroundWindow(IntPtr h);
  [DllImport("user32.dll")] public static extern bool ShowWindow(IntPtr h, int n);
  [DllImport("user32.dll")] public static extern bool IsIconic(IntPtr h);
}
'@
$cur = $PID; $hwnd = [IntPtr]::Zero; $winpid = 0
for ($i = 0; $i -lt 8; $i++) {
  $ci = Get-CimInstance Win32_Process -Filter "ProcessId=$cur" -ErrorAction SilentlyContinue
  if (-not $ci) { break }
  $proc = Get-Process -Id $cur -ErrorAction SilentlyContinue
  if ($proc -and $proc.MainWindowHandle -ne [IntPtr]::Zero) { $hwnd = $proc.MainWindowHandle; $winpid = $cur; break }
  $cur = $ci.ParentProcessId
}
if ($hwnd -eq [IntPtr]::Zero) { Write-Error 'No ancestor window found in 8 hops.'; exit 3 }
if ([SC]::IsIconic($hwnd)) { [SC]::ShowWindow($hwnd, 9) | Out-Null }  # 9 = SW_RESTORE
[SC]::SetForegroundWindow($hwnd) | Out-Null
$ws = New-Object -ComObject WScript.Shell
try { $ws.AppActivate($winpid) | Out-Null } catch {}

# --- 3. Type /clear + Enter (queued; processes at turn-end) ---
Start-Sleep -Milliseconds 400
$ws.SendKeys('/clear')
Start-Sleep -Milliseconds 150
$ws.SendKeys('{ENTER}')

# --- 4. Detached delayed waker (10s) — re-foregrounds + TYPES the note as a fresh prompt ---
$hptr = $hwnd.ToInt64()
$note = 'NOTE FROM THE USER: proceed with next steps.'
$inner = @"
Start-Sleep -Seconds 10
Add-Type @'
using System;
using System.Runtime.InteropServices;
public class SCW {
  [DllImport("user32.dll")] public static extern bool SetForegroundWindow(IntPtr h);
  [DllImport("user32.dll")] public static extern bool ShowWindow(IntPtr h, int n);
  [DllImport("user32.dll")] public static extern bool IsIconic(IntPtr h);
}
'@
`$h = [IntPtr]$hptr
if ([SCW]::IsIconic(`$h)) { [SCW]::ShowWindow(`$h, 9) | Out-Null }
[SCW]::SetForegroundWindow(`$h) | Out-Null
`$ws = New-Object -ComObject WScript.Shell
try { `$ws.AppActivate($winpid) | Out-Null } catch {}
Start-Sleep -Milliseconds 400
`$ws.SendKeys('$note')
Start-Sleep -Milliseconds 150
`$ws.SendKeys('{ENTER}')
"@
$enc = [Convert]::ToBase64String([Text.Encoding]::Unicode.GetBytes($inner))
Start-Process -FilePath 'pwsh' -ArgumentList '-NoProfile','-NonInteractive','-EncodedCommand',$enc -WindowStyle Hidden | Out-Null

"SELF-CLEAR armed: id=$id winpid=$winpid hwnd=$hwnd — /clear queued; self-note typed in ~10s"


Skill in `~/.claude/skills/self-clear/`. Reading SKILL.md too.


1	---
2	name: self-clear
3	description: Clear the calling agent's own Claude Code context with /clear, then re-seed it with a user note so it wakes and resumes work after the wipe. Use when the user says "self-clear", "/self-clear", "clear myself", "clear and continue", or "reset my context and keep going".
4	allowed-tools: [PowerShell]
5	---
6
7	# /self-clear
8
9	Wipes THIS agent's conversation (`/clear`), then ~10s later TYPES a self-note
10	as a fresh user prompt so the agent wakes on a clean context and proceeds.
11
12	## Run it
13
14	One script does everything. Just run:
15
16	```powershell
17	& "C:\Users\decid\.claude\skills\self-clear\scripts\self-clear.ps1"
18	```
19
20	Expect: `SELF-CLEAR armed: id=<agent_id> winpid=<n> hwnd=<n> — /clear queued; self-note typed in ~10s`
21
22	Then stop — end your turn promptly so the queued `/clear` fires.
23
24	## What the script does
25
26	1. `owl whoami` → resolves this session's `agent_id` (context-independent, survives the wipe). No perch → it aborts WITHOUT clearing and tells you to `/spt:ready` or `/spt:live` first.
27	2. Walks the parent chain (`pwsh → claude.exe → … → WindowsTerminal`) to the ancestor that owns the window, foregrounds it.
28	3. Types `/clear` + Enter — **queued**; only fires when this turn ends.
29	4. Spawns a **detached** waker: waits 10s (past turn-end + wipe), re-foregrounds the terminal via the arm-time `hwnd`/`winpid`, then **types** `NOTE FROM THE USER: proceed with next steps.` + Enter as a fresh user prompt.
30
31	The 10s delay + detachment are deliberate: the prompt must be typed **after**
32	`/clear` takes effect, so it lands on the clean context and starts a new turn.
33
34	Why typed, not `owl send`: after `/clear` the session sits idle awaiting user
35	input. A spooled owl message can't self-start a turn — it surfaces only during an
36	already-active turn (PreToolUse hook) or in a live Monitor stream (whose buffer
37	`/clear` wipes). So a self-addressed owl note never woke the agent. A typed prompt
38	deterministically starts a turn AND is the re-seed.
39
40	## Caveats
41
42	- Window focus brings the whole terminal forward; it can't target a specific tab. Clean when the agent's tab is active.
43	- The note is typed via SendKeys, so the terminal must stay the foreground-able window of `winpid`. Don't close/replace the terminal in the ~10s gap.
44	- SendKeys reserves `+ ^ % ~ ( ) { } [ ]`; the default note text uses none. If you customize the note, escape those chars.
45	- If your turn runs longer than ~10s after the script returns, the prompt could be typed before the wipe completes. Stop promptly after running.
46

---
name: self-clear
description: Clear the calling agent's own Claude Code context with /clear, then re-seed it with a user note so it wakes and resumes work after the wipe. Use when the user says "self-clear", "/self-clear", "clear myself", "clear and continue", or "reset my context and keep going".
allowed-tools: [PowerShell]
---

# /self-clear

Wipes THIS agent's conversation (`/clear`), then ~10s later TYPES a self-note
as a fresh user prompt so the agent wakes on a clean context and proceeds.

## Run it

One script does everything. Just run:

```powershell
& "C:\Users\decid\.claude\skills\self-clear\scripts\self-clear.ps1"
```

Expect: `SELF-CLEAR armed: id=<agent_id> winpid=<n> hwnd=<n> — /clear queued; self-note typed in ~10s`

Then stop — end your turn promptly so the queued `/clear` fires.

## What the script does

1. `owl whoami` → resolves this session's `agent_id` (context-independent, survives the wipe). No perch → it aborts WITHOUT clearing and tells you to `/spt:ready` or `/spt:live` first.
2. Walks the parent chain (`pwsh → claude.exe → … → WindowsTerminal`) to the ancestor that owns the window, foregrounds it.
3. Types `/clear` + Enter — **queued**; only fires when this turn ends.
4. Spawns a **detached** waker: waits 10s (past turn-end + wipe), re-foregrounds the terminal via the arm-time `hwnd`/`winpid`, then **types** `NOTE FROM THE USER: proceed with next steps.` + Enter as a fresh user prompt.

The 10s delay + detachment are deliberate: the prompt must be typed **after**
`/clear` takes effect, so it lands on the clean context and starts a new turn.

Why typed, not `owl send`: after `/clear` the session sits idle awaiting user
input. A spooled owl message can't self-start a turn — it surfaces only during an
already-active turn (PreToolUse hook) or in a live Monitor stream (whose buffer
`/clear` wipes). So a self-addressed owl note never woke the agent. A typed prompt
deterministically starts a turn AND is the re-seed.

## Caveats

- Window focus brings the whole terminal forward; it can't target a specific tab. Clean when the agent's tab is active.
- The note is typed via SendKeys, so the terminal must stay the foreground-able window of `winpid`. Don't close/replace the terminal in the ~10s gap.
- SendKeys reserves `+ ^ % ~ ( ) { } [ ]`; the default note text uses none. If you customize the note, escape those chars.
- If your turn runs longer than ~10s after the script returns, the prompt could be typed before the wipe completes. Stop promptly after running.


Applying fixes to `self-clear.ps1`.

Fix 1 — window focus: replace `MainWindowHandle` (returns process's first/main window) with `EnumWindows`-by-PID that finds the visible top-level window owned by the exact ancestor PID.


Edit

# --- 2. Focus the terminal window ---
Add-Type @'
using System;
using System.Runtime.InteropServices;
public class SC {
  [DllImport("user32.dll")] public static extern bool SetForegroundWindow(IntPtr h);
  [DllImport("user32.dll")] public static extern bool ShowWindow(IntPtr h, int n);
  [DllImport("user32.dll")] public static extern bool IsIconic(IntPtr h);
}
'@
$cur = $PID; $hwnd = [IntPtr]::Zero; $winpid = 0
for ($i = 0; $i -lt 8; $i++) {
  $ci = Get-CimInstance Win32_Process -Filter "ProcessId=$cur" -ErrorAction SilentlyContinue
  if (-not $ci) { break }
  $proc = Get-Process -Id $cur -ErrorAction SilentlyContinue
  if ($proc -and $proc.MainWindowHandle -ne [IntPtr]::Zero) { $hwnd = $proc.MainWindowHandle; $winpid = $cur; break }
  $cur = $ci.ParentProcessId
}

# --- 2. Focus the terminal window ---
# We must focus the window that belongs to THIS session's ancestor pid, NOT the
# program's "main window". Get-Process.MainWindowHandle returns whichever window
# the OS treats as a process's primary one — for a multi-window terminal host
# (e.g. one WindowsTerminal.exe serving several windows) that is the FIRST window,
# which is usually the wrong one. Instead, walk the parent chain and, for each
# ancestor pid, enumerate top-level windows and pick the visible, titled one OWNED
# by that exact pid (FindForPid). The deepest such ancestor is this session's window.
Add-Type @'
using System;
using System.Runtime.InteropServices;
public class SC {
  [DllImport("user32.dll")] public static extern bool SetForegroundWindow(IntPtr h);
  [DllImport("user32.dll")] public static extern bool ShowWindow(IntPtr h, int n);
  [DllImport("user32.dll")] public static extern bool IsIconic(IntPtr h);
  [DllImport("user32.dll")] static extern bool EnumWindows(EnumWindowsProc cb, IntPtr l);
  [DllImport("user32.dll")] static extern uint GetWindowThreadProcessId(IntPtr h, out uint pid);
  [DllImport("user32.dll")] static extern bool IsWindowVisible(IntPtr h);
  [DllImport("user32.dll")] static extern IntPtr GetWindow(IntPtr h, uint cmd);
  [DllImport("user32.dll")] static extern int GetWindowTextLength(IntPtr h);
  delegate bool EnumWindowsProc(IntPtr h, IntPtr l);
  const uint GW_OWNER = 4;
  // First visible, titled, un-owned (top-level) window belonging to `target` pid.
  public static IntPtr FindForPid(uint target) {
    IntPtr found = IntPtr.Zero;
    EnumWindows((h, l) => {
      uint pid; GetWindowThreadProcessId(h, out pid);
      if (pid == target && IsWindowVisible(h) && GetWindow(h, GW_OWNER) == IntPtr.Zero && GetWindowTextLength(h) > 0) {
        found = h; return false; // stop enumeration
      }
      return true;
    }, IntPtr.Zero);
    return found;
  }
}
'@
$cur = $PID; $hwnd = [IntPtr]::Zero; $winpid = 0
for ($i = 0; $i -lt 8; $i++) {
  $ci = Get-CimInstance Win32_Process -Filter "ProcessId=$cur" -ErrorAction SilentlyContinue
  if (-not $ci) { break }
  $cand = [SC]::FindForPid([uint32]$cur)
  if ($cand -ne [IntPtr]::Zero) { $hwnd = $cand; $winpid = $cur; break }
  $cur = $ci.ParentProcessId
}