Merge pull request #27 from PyAutoLabs/claude/pyauto-skills-modernize-l29hxr

Re-home workflow skills out of Mind; retire handoff; record relocation

Author: Jammy2211

README.md

@@ -170,10 +170,13 @@ fine — write naturally, the AI fills in the rest.
   done
 ```
 
-Two slash commands operate over the prompt registry without starting work:
+The slash commands above are skills hosted across the organism (Brain, Heart) but
+all read/write Mind's registry via workspace-root-anchored paths. One operates
+over the registry without starting work:
 
 - `/pyauto-status` — dashboard of `active.md`, `planned.md`, `complete.md`
-- `/handoff` — park a task on this machine and resume on another (mobile, laptop, server)
+  (a PyAutoHeart status view). Continuity across execution environments needs no
+  special step — any environment reads `active.md` and resumes an in-flight task.
 
 ---
 
@@ -226,23 +229,20 @@ PyAutoMind/
 │   ├── status.sh            ← prompt inventory helper
 │   └── prompt_sync.sh       ← commit/push helpers sourced by skills
 │
-└── skills/                  ← Claude Code skills tightly coupled to the prompt registry
-    ├── start_dev/
-    ├── start_library/
-    ├── start_workspace/
-    ├── ship_library/
-    ├── ship_workspace/
-    ├── pyauto-status/
-    ├── register_and_iterate/
-    ├── handoff/
-    ├── worktree_status/
-    ├── create_issue/
-    └── plan_branches/
+└── skills/                  ← Mind-owned skills + the ownership audit
+    ├── OWNERSHIP.md          ← where every workflow skill lives, and why
+    └── create_issue/         ← convert a prompt into a tracked GitHub issue
 ```
 
-The `skills/` here hold **only the skills that read or write `active.md` / prompt
-files**. General PyAuto tooling (release prep, dependency audits, smoke tests,
-lint sweeps) lives in `admin_jammy/skills/`.
+`PyAutoMind/skills/` now holds **only** the Mind-owned `create_issue` skill (plus
+`OWNERSHIP.md`). The development-workflow skills were re-homed to the organs that
+own them — **PyAutoBrain** (`start_dev`, `start_dev_for_user`, `plan_branches`,
+`start_library`, `start_workspace`, `ship_library`, `ship_workspace`,
+`register_and_iterate`), **PyAutoHeart** (`pyauto-status`, `pyauto-status-full`,
+`worktree_status`), and **autolens_profiling** (`profile_likelihood`). The
+`handoff` skill was retired (PyAutoBrain runs uniformly across execution
+environments — see `OWNERSHIP.md`). General PyAuto tooling (release prep,
+dependency audits, smoke tests, lint sweeps) lives in `admin_jammy/skills/`.
 
 `scripts/prompt_sync.sh` is sourced by skills that mutate registry files
 (`active.md`, `complete.md`, etc.) to commit and push back to origin. It
@@ -439,10 +439,9 @@ flags anything in `z_vault/` that's been sitting for a while.
 
 ### From inside Claude Code
 
-- `/pyauto-status` — dashboard of registry state (active, planned, recent complete)
-- `/start_dev <category>/<name>.md` — read a prompt and route it
-- `/handoff park` / `/handoff resume` — cross-machine task transitions
-- `/worktree_status` — cross-references registry with task worktrees
+- `/pyauto-status` — dashboard of registry state (active, planned, recent complete; PyAutoHeart)
+- `/start_dev <work-type>/<target>/<name>.md` — read a prompt and route it (PyAutoBrain)
+- `/worktree_status` — cross-references registry with task worktrees (PyAutoHeart)
 
 ---
 
@@ -472,28 +471,20 @@ absolute path.
 
 ```bash
 cd ~/Code/PyAutoLabs
-# Until the GitHub-side rename (PyAutoPrompt -> PyAutoMind) lands, clone the old
-# URL into a PyAutoMind/ directory: the old URL works now and redirects after the
-# rename, and the documented commands all assume a `PyAutoMind/` checkout. Once
-# the rename lands, `git clone git@github.com:PyAutoLabs/PyAutoMind.git` works too.
-git clone git@github.com:PyAutoLabs/PyAutoPrompt.git PyAutoMind
-git clone git@github.com:Jammy2211/admin_jammy.git    # if not already present
+git clone git@github.com:PyAutoLabs/PyAutoMind.git    # the Mind (this repo)
+git clone git@github.com:PyAutoLabs/PyAutoBrain.git   # dev-workflow skills
+git clone git@github.com:PyAutoLabs/PyAutoHeart.git   # status / readiness skills
+git clone git@github.com:Jammy2211/admin_jammy.git    # installer + general tooling
 bash admin_jammy/skills/install.sh                     # symlinks skills + commands
 ```
 
-> **Note on the rename.** This repository is being renamed from **PyAutoPrompt**
-> to **PyAutoMind**. The GitHub-side rename is a separate admin action; once it
-> lands, GitHub redirects the old `PyAutoLabs/PyAutoPrompt` URL to the new one, so
-> existing clones keep working — update your remote with
-> `git remote set-url origin git@github.com:PyAutoLabs/PyAutoMind.git`.
->
-> **The local checkout directory must be named `PyAutoMind`** (or symlinked with
-> `ln -s PyAutoPrompt PyAutoMind`). The skill and script docs reference
-> `PyAutoMind/...` paths directly — e.g. `source PyAutoMind/scripts/prompt_sync.sh`
-> and `git -C PyAutoMind …` — so a directory still named `PyAutoPrompt` will break
-> those commands. (The `prompt_sync.sh` fallback only covers automatic
-> `PROMPT_REPO` resolution, not these literal documented paths.)
-
-`install.sh` auto-discovers skills from both `admin_jammy/skills/` and
-`PyAutoMind/skills/` and creates symlinks under `~/.claude/skills/` and
-`~/.claude/commands/`. Re-run any time after pulling new skills from either repo.
+> **The local checkout directory must be named `PyAutoMind`.** The skills and
+> scripts reference `PyAutoMind/...` paths directly — e.g.
+> `source PyAutoMind/scripts/prompt_sync.sh` and `git -C PyAutoMind …` — so a
+> differently-named directory breaks those commands.
+
+`install.sh` auto-discovers skills from every present discovery root
+(`admin_jammy/skills/`, `PyAutoMind/skills/`, `PyAutoBrain/skills/`,
+`PyAutoHeart/skills/`, `autolens_profiling/skills/`) and creates symlinks under
+`~/.claude/skills/` and `~/.claude/commands/`. Roots that aren't checked out are
+skipped. Re-run any time after pulling new skills from any of those repos.

scripts/pyauto_status.sh

@@ -35,7 +35,7 @@
 #                             Suppressed when no JSONs exist.
 #
 # Note: this shell function shares its name with the /pyauto-status slash
-# command (PyAutoMind/skills/pyauto-status/) but lives in a different
+# command (PyAutoHeart/skills/pyauto-status/) but lives in a different
 # namespace. The slash command shows workflow registry status (planned /
 # active / complete tasks); this function shows git sync state.
 

scripts/pyauto_status_full.sh

@@ -22,7 +22,7 @@
 #   pyauto-status-full ~/Code/PyAutoLabs/PyAutoBuild/test_results/runs/2026-04-29T14-48-47Z
 #
 # Note: this shell function shares its name with the /pyauto-status-full
-# slash command (PyAutoMind/skills/pyauto-status-full/) but lives in a
+# slash command (PyAutoHeart/skills/pyauto-status-full/) but lives in a
 # different namespace. The slash command is the conversational layer; this
 # function is the same data, printed straight to stdout, no Claude needed.
 

skills/OWNERSHIP.md

@@ -0,0 +1,104 @@
+# PyAuto workflow skill ownership — audit + relocation
+
+Originally an **ownership/location audit** (PR #26); this version records the
+**completed relocation** done by the skill-redesign task (`autoprompt/skill_redesign.md`).
+Each workflow skill now lives in the organ that owns its responsibility, command
+names preserved, discovery wired up via `admin_jammy/skills/install.sh`.
+
+## What moved (and why)
+
+Ownership reconciled with the **actual** organism boundary docs
+(`PyAutoBrain/AGENTS.md`, `PyAutoBuild/AGENTS.md`), not the aspirational mapping
+in `skill_redesign.md`:
+
+- **Mind** = intent + task-registry state.
+- **Memory** = accumulated knowledge (consulted for context).
+- **Brain** = reasoning + how-work-gets-done; **owns the development workflow**.
+- **Heart** = health / validation / readiness gates.
+- **Build (Hands)** = **release/packaging executor only** (tag / notebooks / PyPI
+  via `release.yml`). It owns **no** workflow skills; `ship_*` is feature-dev work
+  that only *calls* Build's release step at release time.
+
+| Skill | New home | Recommended owner | Action taken |
+|-------|----------|-------------------|--------------|
+| `create_issue` | `PyAutoMind/skills/` | **PyAutoMind** — the issue+registry **primitive** (Brain's `/start_dev` delegates the issue write to it; runnable standalone) | kept in Mind |
+| `start_dev` | `PyAutoBrain/skills/` | **PyAutoBrain** (classification/routing entry) | **moved → Brain** |
+| `start_dev_for_user` | `PyAutoBrain/skills/` | **PyAutoBrain** (routing variant) | **moved → Brain** |
+| `plan_branches` | `PyAutoBrain/skills/` | **PyAutoBrain** (planning) | **moved → Brain** |
+| `start_library` | `PyAutoBrain/skills/` | **PyAutoBrain** (dev-cycle setup) | **moved → Brain** |
+| `start_workspace` | `PyAutoBrain/skills/` | **PyAutoBrain** (dev-cycle setup) | **moved → Brain** |
+| `ship_library` | `PyAutoBrain/skills/` | **PyAutoBrain** dev-workflow → Heart gate (Build only at release) | **moved → Brain** |
+| `ship_workspace` | `PyAutoBrain/skills/` | **PyAutoBrain** dev-workflow → Heart gate (Build only at release) | **moved → Brain** |
+| `register_and_iterate` | `PyAutoBrain/skills/` | **PyAutoBrain** (dev-workflow orchestration loop) | **moved → Brain** |
+| `repo_cleanup` | `PyAutoBrain/skills/` | **PyAutoBrain** (between-tasks git hygiene; Heart observes, Brain decides + executes — natural home is a future Cleanup Agent) | **moved → Brain** (from admin_jammy) |
+| `pyauto-status` | `PyAutoHeart/skills/` | **PyAutoHeart** (status/readiness view) | **moved → Heart** |
+| `pyauto-status-full` | `PyAutoHeart/skills/` | **PyAutoHeart** (release-readiness dashboard) | **moved → Heart** |
+| `worktree_status` | `PyAutoHeart/skills/` | **PyAutoHeart** (diagnostic) | **moved → Heart** |
+| `profile_likelihood` | `autolens_profiling/skills/` | **`autolens_profiling`** (science profiling) | **moved → autolens_profiling** |
+| `handoff` | — (removed) | — | **deleted** — the phone↔laptop park/resume dance is obsolete now PyAutoBrain runs uniformly across execution environments; `active.md` is the shared task state, so any environment resumes a task directly |
+
+### Second wave — general admin_jammy skills
+
+A follow-up pass re-homed the remaining admin_jammy skills so `admin_jammy/`
+trends toward installer + tooling only:
+
+- **→ PyAutoHeart** (read-only validation/readiness checks): `dep_audit`,
+  `verify_install`, `review_release`, `audit_docs`, `cli_noise_clean`.
+- **→ PyAutoBrain** (dev-workflow): `update_issue`, `repo_cleanup`.
+- **→ PyAutoBuild** (release execution): `pre_build`. PyAutoBuild now has a
+  `skills/` root for its **release-execution** skills only — it still owns no
+  dev-workflow skills (`ship_*` live in Brain and only *call* its release step).
+- **Removed:** `start-new-project` was a duplicate of the canonical science-project
+  skill already owned by `autolens_assistant` (`skills/start-new-project.md`),
+  so the admin_jammy fork was deleted rather than moved.
+
+After this, `admin_jammy/skills/` hosts **no skills** — only the installer
+(`install.sh`) and the line-count guard (`check_skill_line_counts.sh`).
+
+(`*/agents/openai.yaml` and the `SKILL.md` ↔ `<name>.md` pairs are bundled Codex
+agent configs / dispatcher+body pairs, not separate skills. Long-form detail was
+factored into per-skill `reference.md` files and the shared
+`PyAutoBrain/skills/WORKFLOW.md`, keeping every primary skill file under 200
+lines.)
+
+## Discovery
+
+`admin_jammy/skills/install.sh` now scans these roots and symlinks skills into
+`~/.claude/skills/` and commands into `~/.claude/commands/`:
+
+- `admin_jammy/skills/` — general PyAuto tooling
+- `PyAutoMind/skills/` — registry-coupled (`create_issue`)
+- `PyAutoBrain/skills/` — development-workflow
+- `PyAutoHeart/skills/` — status / readiness
+- `autolens_profiling/skills/` — science profiling
+
+**PyAutoBuild's `skills/` root holds release-execution skills only** (`pre_build`)
+— it owns no *dev-workflow* skills; `ship_*` live in Brain and only call its
+release step. Registry
+references stay workspace-root-anchored (`PyAutoMind/active.md`,
+`PyAutoMind/complete.md`, `source PyAutoMind/scripts/prompt_sync.sh`), which
+resolve from any sibling repo, so the moved skills keep working unchanged.
+
+## Redesign summary
+
+The moves were paired with the redesign in `autoprompt/skill_redesign.md`:
+
+- Skills are **thin entry points** that delegate to the organism — Brain reasons
+  and routes (Feature/Build/Health agents), Heart gates ship via
+  `pyauto-heart readiness`, Build executes release only, Mind holds state, Memory
+  supplies context.
+- `start_dev` routes through the **Feature Agent** (+ Memory); `ship_*` gates
+  through the **Health Agent → Heart** before the dev workflow commits/pushes/PRs.
+- "Remote / mobile mode" is gone, replaced by the general execution-environment
+  model (`local-dev` / `web-github` / `ci-only` / `analysis-only`) in
+  `PyAutoBrain/skills/WORKFLOW.md`. No phone↔laptop handoff concept remains.
+- Command names and the start/ship lifecycle are preserved.
+
+## Validation
+
+- `bash admin_jammy/skills/install.sh` → every moved `/command` resolves.
+- `find <each skills dir> -type l` → no stray symlinks in source.
+- `bash admin_jammy/skills/check_skill_line_counts.sh` → all primary workflow
+  skill files within 200 lines.
+- Grep for stale `PyAutoMind/skills/` workflow paths and mobile/remote-mode terms
+  → clean across the moved skills.