docs(index): place experiment-spec in the relationships diagram

Missed in 83b069a. #15 asked for three things and the table row was only two of them: experiment-spec also belongs in the Skill Relationships tree, parallel to feature-spec and downstream of spec-driven-dev, since it is the research/ML substitute for feature-spec rather than a separate lifecycle. dream needs no edge, same as trainer and session-retrospective — the issue said so and that part was right. Refs #15 Bump-Type: patch
chore(release): plugin.json version 0.8.3
2026-08-29 09:54:23 +02:00 · 2026-08-29 07:53:48 +00:00 · 2026-08-29 09:53:33 +02:00 · 2026-08-29 07:52:16 +00:00
3 changed files with 25 additions and 13 deletions
@@ -1,7 +1,7 @@
 {
  "name": "skills",
  "description": "Mathias's engineering skills library, plus the hooks and MCP servers that make it enforceable: TDD, clean code, debugging, specs, discovery, CI, and secret hygiene.",
-  "version": "0.8.1",
+  "version": "0.8.3",
  "author": {
    "name": "Mathias",
    "url": "https://git.d-ma.be/mathias"
@@ -109,14 +109,16 @@ problem-analysis
            │
            ├── spec-driven-dev (PM-kickoff lifecycle)
            │       │
-            │       └── feature-spec (per-feature, mid-implementation)
-            │               │
-            │               └── planning
-            │                       │
-            │                       └── atdd ──→ tdd (foundation)
-            │                                ├──→ debug (when tests fail)
-            │                                ├──→ clean-code (REFACTOR phase)
-            │                                └──→ test-design (review)
+            │       ├── feature-spec (per-feature, mid-implementation)
+            │       │       │
+            │       │       └── planning
+            │       │               │
+            │       │               └── atdd ──→ tdd (foundation)
+            │       │                        ├──→ debug (when tests fail)
+            │       │                        ├──→ clean-code (REFACTOR phase)
+            │       │                        └──→ test-design (review)
+            │       │
+            │       └── experiment-spec (research/ML phase, instead of feature-spec)
            │
            └── planning

@@ -22,18 +22,28 @@ Screenshot a locally-running web UI without installing a browser on the agent's

 ## Usage

+`shot.sh` ships beside this SKILL.md, so resolve it from wherever the harness
+installed the skill rather than from a checkout path — an absolute `~/dev/...`
+went stale the first time the repo moved and cost a caller three hand-rolled
+Job attempts before they found the working script (#26).
+
 ```bash
+# Claude Code installs the plugin; Crush/Pi/OpenCode get ~/.agents/skills.
+SHOT=$(ls ~/.claude/plugins/marketplaces/*/skills/web-shot/shot.sh \
+          ~/.agents/skills/web-shot/shot.sh 2>/dev/null | head -1 || true)
+[ -n "$SHOT" ] || { echo "web-shot not installed on this host: run install.sh or the plugin install" >&2; exit 1; }
+
 # auto-detect Tailscale hostname, screenshot port 8099 root
-~/dev/.skills/web-shot/shot.sh --port 8099
+"$SHOT" --port 8099

 # explicit URL
-~/dev/.skills/web-shot/shot.sh --url http://flamingo:5173
+"$SHOT" --url http://flamingo:5173

 # capture a search state too (types into input[name=q])
-~/dev/.skills/web-shot/shot.sh --port 8181 --search agentsquad
+"$SHOT" --port 8181 --search agentsquad

 # different output dir
-~/dev/.skills/web-shot/shot.sh --port 3000 --out /tmp/shots
+"$SHOT" --port 3000 --out /tmp/shots
 ```

 ## Flags
Author	SHA1	Message	Date
mathias	b188965161	docs(index): place experiment-spec in the relationships diagram CI / Check / Test (push) Successful in 1s Details CI / Tag release (push) Successful in 1s Details Missed in `83b069a`. #15 asked for three things and the table row was only two of them: experiment-spec also belongs in the Skill Relationships tree, parallel to feature-spec and downstream of spec-driven-dev, since it is the research/ML substitute for feature-spec rather than a separate lifecycle. dream needs no edge, same as trainer and session-retrospective — the issue said so and that part was right. Refs #15 Bump-Type: patch	2026-08-29 09:54:23 +02:00
mathias	ae66840a03	chore(release): plugin.json version 0.8.3 Skip-Release: true	2026-08-29 07:53:48 +00:00
mathias	e7e514390b	docs(web-shot): resolve shot.sh from the install, not a checkout path CI / Check / Test (push) Successful in 1s Details CI / Tag release (push) Successful in 1s Details The usage block pointed at ~/dev/.skills/web-shot/shot.sh four times. That directory has not existed since the skills moved into this repo, and the failure mode is worse than a broken link: web-shot exists for agents with no local browser, so a 404 sends them to hand-roll the Job instead of looking harder. One caller burned three attempts on playwright module resolution before finding the script that documents that exact gotcha. Replaced with a resolution line covering both delivery paths — the Claude Code plugin and the ~/.agents/skills symlink — so no absolute checkout path is left to rot. Verified on koala: resolves to the .agents link, and degrades to an empty string plus a clear message where the skill is not installed. The brain entry headless-browser-via-k3s-playwright-job carried the same stale path in three places and referenced the retired wire-skills.sh wiring; updated to match. Closes #26 Bump-Type: patch	2026-08-29 09:53:33 +02:00
mathias	087685f2e3	chore(release): plugin.json version 0.8.2 Skip-Release: true	2026-08-29 07:52:16 +00:00