spexcode 0.2.7 → 0.3.0

package/spec-cli/templates/spec/project/{.config → .plugins}/spec.md

@@ -1,12 +1,12 @@
 ---
-title: .config
+title: .plugins
 status: active
 hue: 110
-desc: The instance home — this repo's DIY dev-flow plugins live here as skill-shaped config nodes.
+desc: The instance home — this repo's DIY dev-flow plugins live here as skill-shaped plugin nodes.
 ---
-`.config/` is the **instance** of the config system: the concrete dev-flow plugins this repo ships for
+`.plugins/` is the **instance** of the plugin system: the concrete dev-flow plugins this repo ships for
 working in it. Each plugin is a skill-shaped node — its folder *is* the unit (a `spec.md` plus any
-co-located scripts) — living as a flat child of `.config/` and carrying a `surface: command|system` field
+co-located scripts) — living as a flat child of `.plugins/` and carrying a `surface: command|system` field
 that names where it plugs in.
 
 The launcher's system gather and the new-session dropdown read from here. Only **active** plugins

package/spec-cli/templates/spec/project/.plugins/supervisor/spec.md

@@ -0,0 +1,8 @@
+---
+title: supervisor
+surface: command
+status: active
+hue: 280
+desc: Launch a supervisor agent that manages other agents from the main checkout to drive a goal to completion.
+---
+You are a SpexCode supervisor — a **manager**, not a feature worker. Your work base is the main checkout (the repository root), NOT your own worktree: do all git via `git -C <root>`, everything else via the `spex` CLI, and never write feature code. **FIRST, read `<root>/CLAUDE.md` — specifically its "Supervising — the manager loop" section** — that is your complete playbook (dispatch → monitor → review → merge → close, and how to parallelize). Then drive the goal: decompose it into worker-sized tasks and dispatch one worker per independent task (`spex session new "<task>"` — give each ONLY its task; a task about one specific node mentions it as `[[<id>]]`, which only sets the branch name and board attribution; the session's real node links come from what it edits), monitor with `spex session watch`, review proposals with `spex session review <id>`, merge good ones with `git -C <root> merge --no-ff <branch>`, then close. Never let a worker self-merge; keep `spex spec lint` at 0 errors. To WAIT on a worker, POLL one-shot (`spex session review <id>` or `spex session ls` — both return immediately); never block on `spex session watch`, which STREAMS forever and will freeze your turn. One footgun that bites a fresh supervisor: before `spex session close <id>`, confirm the merge landed (`git -C <root> log -1` shows HEAD at the new merge commit) — closing an unmerged branch discards the work. Report progress as you go and when the goal is complete. Your goal follows:

package/spec-cli/templates/spec/project/{.config → .plugins}/tidy/spec.md

@@ -22,4 +22,4 @@ For each target, in its own commit:
 - **Cut redundancy and narration** — say each thing once, at the altitude a maintainer needs.
 - **Stay a living document** — rewrite in place; never add `## vN` history (git carries versions).
 
-Commit per node (`spec: <id> — tidy to contract altitude`) with a `Session:` trailer. Run `spex lint` after each — it must stay at 0 errors.
+Commit per node (`spec: <id> — tidy to contract altitude`) with a `Session:` trailer. Run `spex spec lint` after each — it must stay at 0 errors.

package/spec-cli/templates/spec/project/spec.md

@@ -12,7 +12,7 @@ made it. This node is the founding spec everything else hangs from — **rewrite
 your own project**, then grow child package/feature nodes beneath it (each its own directory with a
 `spec.md`).
 
-`.config/` holds the dev-flow plugins this instance ships — skill-shaped flat child nodes, each tagged
+`.plugins/` holds the dev-flow plugins this instance ships — skill-shaped flat child nodes, each tagged
 with a `surface` field: a `surface: system` node folds into every launched agent's system prompt as
 always-on contract (the seed ships `core`), and a `surface: command` node is a prompt preset the
 new-session dropdown composes over target nodes (the seed ships `tidy`). Add, edit, or