multi-agent-prompt 0.1.0__tar.gz

multi_agent_prompt-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,47 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      # https://github.com/actions/checkout
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      # The autosave/keymap/fold-on-paste integration tests drive a real
+      # Neovim (headless, and over a pseudo-terminal for anything that needs
+      # actual UI attachment — TextChanged and startinsert! don't fire
+      # without one). They skip gracefully if nvim is missing, but that
+      # would silently stop covering the thing this project mostly is.
+      - name: Install Neovim
+        run: sudo apt-get update && sudo apt-get install -y neovim
+
+      # https://github.com/astral-sh/setup-uv
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        run: uv python install
+
+      - name: Run ruff
+        run: uv run ruff check .
+
+      - name: Run mypy
+        run: uv run mypy src
+
+      - name: Run pytest
+        run: uv run pytest

multi_agent_prompt-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,52 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "v*"
+
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+
+jobs:
+  publish:
+    name: Build and publish
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: write
+      attestations: write
+
+    steps:
+      # https://github.com/actions/checkout
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      # See ci.yml: the integration tests need a real Neovim to run at all
+      # rather than skip.
+      - name: Install Neovim
+        run: sudo apt-get update && sudo apt-get install -y neovim
+
+      # https://github.com/astral-sh/setup-uv
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        run: uv python install
+
+      - name: Install dependencies
+        run: uv sync
+
+      - name: Run test suite
+        run: uv run pytest
+
+      - name: Build package
+        run: uv build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          verbose: true

multi_agent_prompt-0.1.0/.gitignore

@@ -0,0 +1,17 @@
+.venv
+__pycache__/
+*.pyc
+dist/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.ma/prompt/
+
+# task-agent auto-registers any git repo it finds under ~/repos/ as one of
+# its own task stores — unrelated to this project, not ours to track.
+# docs/tasks is a symlink it manages, pointing at a machine-specific
+# absolute path — must never be committed as a real symlink.
+.env
+.ta-config.json
+docs/tasks

multi_agent_prompt-0.1.0/PKG-INFO

@@ -0,0 +1,231 @@
+Metadata-Version: 2.5
+Name: multi-agent-prompt
+Version: 0.1.0
+Summary: A crash-proof, autosaving prompt editor for AI coding agent CLIs — compose in your real editor, hand off with a slash command
+Author-email: Mark Stouffer <1802850+InTEGr8or@users.noreply.github.com>
+License: MIT
+Requires-Python: >=3.12
+Requires-Dist: rich>=13.9.4
+Requires-Dist: verkit>=0.1.4
+Description-Content-Type: text/markdown
+
+# Multi-Agent Prompt ✍️
+
+A crash-proof, autosaving prompt editor for AI coding agent CLIs.
+
+Chat text boxes lose long, carefully-composed prompts to a single wrong
+keystroke, and give you almost no editing power while you write. `multi-agent-prompt`
+moves composition out of the chat box entirely: write in a real Neovim, in a
+split pane next to your agent session, autosaved to disk every couple of
+seconds so a crash or a fat-fingered shortcut can never cost you more than a
+moment of typing. When you're ready, hand it to the agent with `/prompt` —
+which reads it, archives it, and clears the file in one step, so there's no
+separate "now go clear it" to remember.
+
+---
+
+## Install
+
+```bash
+pip install multi-agent-prompt
+# or
+uv tool install multi-agent-prompt
+```
+
+Requires [Neovim](https://neovim.io/) — the autosave hook is Lua, so plain
+Vim isn't supported.
+
+## Usage
+
+Open a split pane next to your agent CLI (Windows Terminal: `Alt+Shift+-`;
+tmux: `<prefix> "`) in the **same working directory**, then run:
+
+```bash
+map
+```
+
+This opens `.ma/prompt/current.md` — resolved to the current project's git
+root, so every pane in the same repo shares one scratch file — in your actual
+`nvim`, your actual `init.lua`, your actual keymaps and plugins. No config
+import step, no reimplemented Vim subset: it's just Neovim. You land in
+**insert mode already**, cursor at the end of the buffer, so there's no `i`
+to press before you start typing (`--no-insert` if you'd rather open in
+normal mode). A buffer-local autocmd (scoped only to this one buffer — it
+never touches how you edit anything else) autosaves ~2 seconds after you stop
+typing, and immediately when you switch away from the pane
+(`FocusLost`/`BufLeave`), so the save always beats you to the chat window.
+
+When you're done, switch back to the agent pane and either:
+
+- Type `/prompt` (if the agent's install includes the skill — see below) —
+  reads the draft, archives it, and clears the file, all in one step, or
+- Reference `@prompt.md` / `@.ma/prompt/current.md` directly, if your agent
+  supports file mentions and can see gitignored files — this is a plain
+  read, so unlike `/prompt` it doesn't archive or clear anything.
+
+Pasting a long CLI transcript or diff in? Anything **6 lines or more**
+(bracketed paste, `"+p`, `"*p` — any paste source) auto-folds, closed, so it
+doesn't bury the rest of what you're writing — `za`/`zo`/`zc` (standard Vim)
+toggle it open.
+
+Also want to browse past drafts without leaving the editor? A buffer-local
+keymap — `<leader>ph` by default — lists archived drafts (newest first) in a
+split; `<CR>` opens one, read-only. Forgot what any of this is bound to?
+Press `g?` — it shows exactly the keymaps active for *this* session
+(respecting any `--clear-key`/`--history-key` overrides, and omitting
+whichever ones you disabled):
+
+```
+map            # open the scratch file (same as `map edit`)
+map where      # print the resolved file path
+map show       # print its current content to stdout (does not clear it)
+map pop        # print it, archive it, and clear it — what /prompt uses
+map clear      # archive the current draft, then empty it, without printing it
+map --clean    # skip your init.lua entirely (-u NONE) for faster startup
+```
+
+```
+map edit --clear-key '<F5>'      # rebind the in-editor clear keymap
+map edit --no-clear-key          # don't register it at all
+map edit --history-key '<F6>'    # rebind the in-editor history-browse keymap
+map edit --no-history-key        # don't register it at all
+map edit --help-key '<F1>'       # rebind the in-editor g? cheatsheet keymap
+map edit --no-help-key           # don't register it at all
+map edit --fold-threshold 3      # auto-fold pastes of 3+ lines instead of 6
+map edit --no-fold-paste         # don't auto-fold pastes at all
+map edit --no-insert             # open in normal mode instead of insert mode
+map clear --keep 20              # override how many archived drafts to retain
+map clear --no-archive           # discard instead of archiving (e.g. it had a secret in it)
+```
+
+`map pop` accepts the same `--keep`/`--no-archive` as `map clear`.
+
+### The archive
+
+`map pop`/`map clear` — from the CLI or the in-editor keymap, which shells
+out to `map clear` — never actually discard a non-empty draft; they move it
+to `.ma/prompt/archive/<timestamp>-<seq>.md` first, then prune that archive
+down to the most recent entries. Pruning is by **count**, not age (`--keep` /
+`MAP_ARCHIVE_KEEP` env var, default **10**) — simpler to reason about than a
+retention window, and it doesn't depend on the clock. Use `--no-archive` for
+the one case that shouldn't be kept anywhere: you pasted a secret and want it
+actually gone.
+
+## Performance
+
+A `map` session opens your *entire* Neovim config, which is exactly the
+point — but if that config is large, startup isn't free. Two things worth
+knowing, from actually measuring it (not guessing):
+
+- **It's not a one-time thing.** Whatever makes your first `map` slow will
+  make every subsequent one about equally slow, unless something changes
+  (lazy.nvim itself finishes installing/compiling once; LSP servers and
+  large plugin trees generally don't get meaningfully faster after that).
+- **On WSL specifically, check for `vim.opt.clipboard = 'unnamedplus'` (or
+  similar) in your own init.lua.** Setting that option makes Neovim probe for
+  a clipboard provider immediately, and on WSL that probe walks every `PATH`
+  entry checking `executable()` — including everything under `/mnt/c/...`,
+  which is slow cross-filesystem interop. Measured on this project's own dev
+  machine: ~900ms startup with that line in play, ~160ms with the Windows
+  `PATH` entries stripped, ~4ms with `-u NONE`. That's not multi-agent-prompt
+  overhead; it's one line in a personal init.lua interacting badly with WSL,
+  and fixing it (or guarding it — see `MAP_SESSION` below) speeds up *every*
+  Neovim session, not just `map`.
+- **`map --clean` (`-u NONE`)** sidesteps all of it by skipping your config
+  entirely — the built-in fast path when you don't need your plugins for a
+  quick edit.
+- **`MAP_SESSION=1`** is set in the environment of every nvim `map` launches.
+  Nothing in this package reads it — it's there so you can guard an
+  expensive line in your *own* init.lua behind
+  `if not vim.env.MAP_SESSION then ... end`, if you want full-config speed
+  back without giving up faster `map` startup. That's your config to edit,
+  not something this tool does for you. This isn't just for the clipboard
+  line above — a scratch prompt buffer has no use for a file-tree sidebar or
+  git tooling either, and with [lazy.nvim](https://github.com/folke/lazy.nvim)
+  you can skip those specific plugins the same way, with `cond` on the spec:
+
+  ```lua
+  return {
+    'nvim-neo-tree/neo-tree.nvim',
+    cond = not vim.env.MAP_SESSION,
+    -- ...
+  }
+  ```
+
+  Confirmed on this project's own dev config: with `neo-tree.nvim` and
+  `gitsigns.nvim` guarded this way, `<leader>e` (NeoTree's toggle) becomes a
+  no-op in a `map` session, and their entire module trees (dozens of
+  individual `require()` calls each) simply don't load — real startup
+  savings, not just fewer keymaps to trip over. `cond` is evaluated on every
+  start, so this takes effect immediately; no `:Lazy sync`/restart needed.
+- **It's specifically a startup cost, not a per-save one.** The clipboard
+  probe runs once, while your init.lua is sourced, not again on autosave, on
+  `FocusLost`, or when you switch panes and type `/prompt` — that last step
+  never touches nvim at all (`map pop`/reading the file is a separate,
+  plain filesystem read and write). If a session still feels slow at the
+  hand-off moment specifically, that's terminal pane-switching or the
+  agent's own slash-command overhead, not this tool or Neovim.
+- **`/prompt`'s own overhead is small, and it isn't Neovim's.** Measured on
+  this project's own dev machine: `map pop` runs in ~60-85ms end to end —
+  bare `python3 -c pass` alone is ~30ms of that, this package's own imports
+  add maybe another ~20ms, and the rest is the file read/archive/write. If
+  `/prompt` still feels slow, that latency lives in the *agent host's* own
+  tool-call round trip (spawning/sandboxing the shell command), not in
+  anything this package does — there's no nvim process in this path at all.
+  The one thing the `prompt` skill itself controls: it runs `map pop`
+  directly rather than checking `which map` first, since that check is a
+  second subprocess spawn that's a wasted round trip almost every time.
+
+## Agent integration
+
+`skills/prompt/` is a portable [Agent Skill](https://code.claude.com/docs/en/skills)
+that teaches a host to read `.ma/prompt/current.md` and treat its content as
+the user's message when they type `/prompt`. See
+[`skills/README.md`](./skills/README.md) for install paths.
+
+## Why not tmux `send-keys` / auto-injection?
+
+That's the obvious next step — save, close the pane, and have the tool type
+`/prompt` into the neighboring agent pane for you — but it needs a reliable
+way to identify *which* pane is running the agent, which varies by terminal
+(tmux panes, Windows Terminal panes, and OS-level input injection like
+`xdotool`/`wtype` all solve a different half of that problem). The manual
+handoff above works everywhere today; auto-injection is being explored as a
+follow-up, potentially building on [`multi-agent-registry`](https://github.com/InTEGr8or/multi-agent-registry)'s
+chat discovery to identify a live agent session (not just a recent one) in
+the same directory.
+
+If/when that lands: prefer sending a widely-supported "submit" keystroke —
+`Ctrl+Enter` is the closest thing to a universal convention across chat
+input boxes — into the target pane after typing `/prompt`, over anything
+input-method-specific, so the same injection code has a chance of working
+across agents rather than being re-tuned per host.
+
+## Design notes
+
+- **The prompt file is per-project, not global.** `.ma/prompt/current.md`
+  resolves against the nearest `.git` root, so working on two projects in two
+  terminal tabs never mixes up their scratch files.
+- **`.ma/` is a shared root, not this tool's alone.** It's the umbrella
+  directory for the whole multi-agent-* line (`map`'s CLI alias is the shared
+  `ma` prefix of `map`/`mar`/`maa`) — one dotfolder instead of one per
+  product. Only `.ma/prompt/` is this tool's; a sibling product could use
+  `.ma/registry/`, etc., without colliding. Note that `task-agent`'s existing
+  `.task-agent/` convention predates this and stays as-is — migrating an
+  already-shipped tool's config layout is a separate, larger decision.
+- **`.gitignore` is managed for you.** The first time `map edit` runs in a
+  git repo, it appends `.ma/prompt/` to `.gitignore` if it isn't already
+  covered — including by a broader pre-existing `.ma/` entry.
+- **Reading is non-destructive; handing off isn't, but it never discards
+  either.** `map show` and `@prompt.md` (file mention) just print/read — the
+  file is untouched either way. `/prompt` (`map pop`) clears it, because the
+  whole point is not needing a separate "now go clear it" step — but it
+  archives first, so "cleared" never means "gone". `--no-archive` is the
+  explicit opt-out for content that shouldn't be kept anywhere at all.
+- **The editor notices when the file changes out from under it.** `/prompt`
+  runs `map pop` from the *agent's* process, not from inside the running
+  nvim session — so if you're still looking at that buffer when you hand a
+  draft off, it auto-reloads (`autoread` + `checktime` on
+  `FocusGained`/`BufEnter`) the next time you focus it, rather than keep
+  showing the text you already submitted. It won't discard anything you've
+  since typed there unsaved.

multi_agent_prompt-0.1.0/README.md

@@ -0,0 +1,220 @@
+# Multi-Agent Prompt ✍️
+
+A crash-proof, autosaving prompt editor for AI coding agent CLIs.
+
+Chat text boxes lose long, carefully-composed prompts to a single wrong
+keystroke, and give you almost no editing power while you write. `multi-agent-prompt`
+moves composition out of the chat box entirely: write in a real Neovim, in a
+split pane next to your agent session, autosaved to disk every couple of
+seconds so a crash or a fat-fingered shortcut can never cost you more than a
+moment of typing. When you're ready, hand it to the agent with `/prompt` —
+which reads it, archives it, and clears the file in one step, so there's no
+separate "now go clear it" to remember.
+
+---
+
+## Install
+
+```bash
+pip install multi-agent-prompt
+# or
+uv tool install multi-agent-prompt
+```
+
+Requires [Neovim](https://neovim.io/) — the autosave hook is Lua, so plain
+Vim isn't supported.
+
+## Usage
+
+Open a split pane next to your agent CLI (Windows Terminal: `Alt+Shift+-`;
+tmux: `<prefix> "`) in the **same working directory**, then run:
+
+```bash
+map
+```
+
+This opens `.ma/prompt/current.md` — resolved to the current project's git
+root, so every pane in the same repo shares one scratch file — in your actual
+`nvim`, your actual `init.lua`, your actual keymaps and plugins. No config
+import step, no reimplemented Vim subset: it's just Neovim. You land in
+**insert mode already**, cursor at the end of the buffer, so there's no `i`
+to press before you start typing (`--no-insert` if you'd rather open in
+normal mode). A buffer-local autocmd (scoped only to this one buffer — it
+never touches how you edit anything else) autosaves ~2 seconds after you stop
+typing, and immediately when you switch away from the pane
+(`FocusLost`/`BufLeave`), so the save always beats you to the chat window.
+
+When you're done, switch back to the agent pane and either:
+
+- Type `/prompt` (if the agent's install includes the skill — see below) —
+  reads the draft, archives it, and clears the file, all in one step, or
+- Reference `@prompt.md` / `@.ma/prompt/current.md` directly, if your agent
+  supports file mentions and can see gitignored files — this is a plain
+  read, so unlike `/prompt` it doesn't archive or clear anything.
+
+Pasting a long CLI transcript or diff in? Anything **6 lines or more**
+(bracketed paste, `"+p`, `"*p` — any paste source) auto-folds, closed, so it
+doesn't bury the rest of what you're writing — `za`/`zo`/`zc` (standard Vim)
+toggle it open.
+
+Also want to browse past drafts without leaving the editor? A buffer-local
+keymap — `<leader>ph` by default — lists archived drafts (newest first) in a
+split; `<CR>` opens one, read-only. Forgot what any of this is bound to?
+Press `g?` — it shows exactly the keymaps active for *this* session
+(respecting any `--clear-key`/`--history-key` overrides, and omitting
+whichever ones you disabled):
+
+```
+map            # open the scratch file (same as `map edit`)
+map where      # print the resolved file path
+map show       # print its current content to stdout (does not clear it)
+map pop        # print it, archive it, and clear it — what /prompt uses
+map clear      # archive the current draft, then empty it, without printing it
+map --clean    # skip your init.lua entirely (-u NONE) for faster startup
+```
+
+```
+map edit --clear-key '<F5>'      # rebind the in-editor clear keymap
+map edit --no-clear-key          # don't register it at all
+map edit --history-key '<F6>'    # rebind the in-editor history-browse keymap
+map edit --no-history-key        # don't register it at all
+map edit --help-key '<F1>'       # rebind the in-editor g? cheatsheet keymap
+map edit --no-help-key           # don't register it at all
+map edit --fold-threshold 3      # auto-fold pastes of 3+ lines instead of 6
+map edit --no-fold-paste         # don't auto-fold pastes at all
+map edit --no-insert             # open in normal mode instead of insert mode
+map clear --keep 20              # override how many archived drafts to retain
+map clear --no-archive           # discard instead of archiving (e.g. it had a secret in it)
+```
+
+`map pop` accepts the same `--keep`/`--no-archive` as `map clear`.
+
+### The archive
+
+`map pop`/`map clear` — from the CLI or the in-editor keymap, which shells
+out to `map clear` — never actually discard a non-empty draft; they move it
+to `.ma/prompt/archive/<timestamp>-<seq>.md` first, then prune that archive
+down to the most recent entries. Pruning is by **count**, not age (`--keep` /
+`MAP_ARCHIVE_KEEP` env var, default **10**) — simpler to reason about than a
+retention window, and it doesn't depend on the clock. Use `--no-archive` for
+the one case that shouldn't be kept anywhere: you pasted a secret and want it
+actually gone.
+
+## Performance
+
+A `map` session opens your *entire* Neovim config, which is exactly the
+point — but if that config is large, startup isn't free. Two things worth
+knowing, from actually measuring it (not guessing):
+
+- **It's not a one-time thing.** Whatever makes your first `map` slow will
+  make every subsequent one about equally slow, unless something changes
+  (lazy.nvim itself finishes installing/compiling once; LSP servers and
+  large plugin trees generally don't get meaningfully faster after that).
+- **On WSL specifically, check for `vim.opt.clipboard = 'unnamedplus'` (or
+  similar) in your own init.lua.** Setting that option makes Neovim probe for
+  a clipboard provider immediately, and on WSL that probe walks every `PATH`
+  entry checking `executable()` — including everything under `/mnt/c/...`,
+  which is slow cross-filesystem interop. Measured on this project's own dev
+  machine: ~900ms startup with that line in play, ~160ms with the Windows
+  `PATH` entries stripped, ~4ms with `-u NONE`. That's not multi-agent-prompt
+  overhead; it's one line in a personal init.lua interacting badly with WSL,
+  and fixing it (or guarding it — see `MAP_SESSION` below) speeds up *every*
+  Neovim session, not just `map`.
+- **`map --clean` (`-u NONE`)** sidesteps all of it by skipping your config
+  entirely — the built-in fast path when you don't need your plugins for a
+  quick edit.
+- **`MAP_SESSION=1`** is set in the environment of every nvim `map` launches.
+  Nothing in this package reads it — it's there so you can guard an
+  expensive line in your *own* init.lua behind
+  `if not vim.env.MAP_SESSION then ... end`, if you want full-config speed
+  back without giving up faster `map` startup. That's your config to edit,
+  not something this tool does for you. This isn't just for the clipboard
+  line above — a scratch prompt buffer has no use for a file-tree sidebar or
+  git tooling either, and with [lazy.nvim](https://github.com/folke/lazy.nvim)
+  you can skip those specific plugins the same way, with `cond` on the spec:
+
+  ```lua
+  return {
+    'nvim-neo-tree/neo-tree.nvim',
+    cond = not vim.env.MAP_SESSION,
+    -- ...
+  }
+  ```
+
+  Confirmed on this project's own dev config: with `neo-tree.nvim` and
+  `gitsigns.nvim` guarded this way, `<leader>e` (NeoTree's toggle) becomes a
+  no-op in a `map` session, and their entire module trees (dozens of
+  individual `require()` calls each) simply don't load — real startup
+  savings, not just fewer keymaps to trip over. `cond` is evaluated on every
+  start, so this takes effect immediately; no `:Lazy sync`/restart needed.
+- **It's specifically a startup cost, not a per-save one.** The clipboard
+  probe runs once, while your init.lua is sourced, not again on autosave, on
+  `FocusLost`, or when you switch panes and type `/prompt` — that last step
+  never touches nvim at all (`map pop`/reading the file is a separate,
+  plain filesystem read and write). If a session still feels slow at the
+  hand-off moment specifically, that's terminal pane-switching or the
+  agent's own slash-command overhead, not this tool or Neovim.
+- **`/prompt`'s own overhead is small, and it isn't Neovim's.** Measured on
+  this project's own dev machine: `map pop` runs in ~60-85ms end to end —
+  bare `python3 -c pass` alone is ~30ms of that, this package's own imports
+  add maybe another ~20ms, and the rest is the file read/archive/write. If
+  `/prompt` still feels slow, that latency lives in the *agent host's* own
+  tool-call round trip (spawning/sandboxing the shell command), not in
+  anything this package does — there's no nvim process in this path at all.
+  The one thing the `prompt` skill itself controls: it runs `map pop`
+  directly rather than checking `which map` first, since that check is a
+  second subprocess spawn that's a wasted round trip almost every time.
+
+## Agent integration
+
+`skills/prompt/` is a portable [Agent Skill](https://code.claude.com/docs/en/skills)
+that teaches a host to read `.ma/prompt/current.md` and treat its content as
+the user's message when they type `/prompt`. See
+[`skills/README.md`](./skills/README.md) for install paths.
+
+## Why not tmux `send-keys` / auto-injection?
+
+That's the obvious next step — save, close the pane, and have the tool type
+`/prompt` into the neighboring agent pane for you — but it needs a reliable
+way to identify *which* pane is running the agent, which varies by terminal
+(tmux panes, Windows Terminal panes, and OS-level input injection like
+`xdotool`/`wtype` all solve a different half of that problem). The manual
+handoff above works everywhere today; auto-injection is being explored as a
+follow-up, potentially building on [`multi-agent-registry`](https://github.com/InTEGr8or/multi-agent-registry)'s
+chat discovery to identify a live agent session (not just a recent one) in
+the same directory.
+
+If/when that lands: prefer sending a widely-supported "submit" keystroke —
+`Ctrl+Enter` is the closest thing to a universal convention across chat
+input boxes — into the target pane after typing `/prompt`, over anything
+input-method-specific, so the same injection code has a chance of working
+across agents rather than being re-tuned per host.
+
+## Design notes
+
+- **The prompt file is per-project, not global.** `.ma/prompt/current.md`
+  resolves against the nearest `.git` root, so working on two projects in two
+  terminal tabs never mixes up their scratch files.
+- **`.ma/` is a shared root, not this tool's alone.** It's the umbrella
+  directory for the whole multi-agent-* line (`map`'s CLI alias is the shared
+  `ma` prefix of `map`/`mar`/`maa`) — one dotfolder instead of one per
+  product. Only `.ma/prompt/` is this tool's; a sibling product could use
+  `.ma/registry/`, etc., without colliding. Note that `task-agent`'s existing
+  `.task-agent/` convention predates this and stays as-is — migrating an
+  already-shipped tool's config layout is a separate, larger decision.
+- **`.gitignore` is managed for you.** The first time `map edit` runs in a
+  git repo, it appends `.ma/prompt/` to `.gitignore` if it isn't already
+  covered — including by a broader pre-existing `.ma/` entry.
+- **Reading is non-destructive; handing off isn't, but it never discards
+  either.** `map show` and `@prompt.md` (file mention) just print/read — the
+  file is untouched either way. `/prompt` (`map pop`) clears it, because the
+  whole point is not needing a separate "now go clear it" step — but it
+  archives first, so "cleared" never means "gone". `--no-archive` is the
+  explicit opt-out for content that shouldn't be kept anywhere at all.
+- **The editor notices when the file changes out from under it.** `/prompt`
+  runs `map pop` from the *agent's* process, not from inside the running
+  nvim session — so if you're still looking at that buffer when you hand a
+  draft off, it auto-reloads (`autoread` + `checktime` on
+  `FocusGained`/`BufEnter`) the next time you focus it, rather than keep
+  showing the text you already submitted. It won't discard anything you've
+  since typed there unsaved.

multi_agent_prompt-0.1.0/pyproject.toml

@@ -0,0 +1,39 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "multi-agent-prompt"
+version = "0.1.0"
+description = "A crash-proof, autosaving prompt editor for AI coding agent CLIs — compose in your real editor, hand off with a slash command"
+readme = "README.md"
+requires-python = ">=3.12"
+license = { text = "MIT" }
+authors = [
+    { name = "Mark Stouffer", email = "1802850+InTEGr8or@users.noreply.github.com" }
+]
+dependencies = [
+    "verkit>=0.1.4",
+    "rich>=13.9.4",
+]
+
+[project.scripts]
+multi-agent-prompt = "multi_agent_prompt.cli:main"
+map = "multi_agent_prompt.cli:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/multi_agent_prompt"]
+
+[tool.hatch.metadata]
+allow-direct-references = true
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+pythonpath = ["src"]
+
+[dependency-groups]
+dev = [
+    "pytest>=8.0.0",
+    "ruff>=0.8.0",
+    "mypy>=1.13.0",
+]

multi_agent_prompt-0.1.0/skills/README.md

@@ -0,0 +1,41 @@
+# Multi-Agent Prompt portable skill
+
+One skill (`prompt`) that teaches a host to read the user's draft from
+`.ma/prompt/current.md` — the scratch file `map` edits — treat it as their
+next message, and clear it for the next one (via `map pop`, which archives
+before it clears) when they type `/prompt`.
+
+## Manual install
+
+Skills are a plain directory. Copy or symlink it into the host's skills path.
+
+### Claude Code
+
+Project-local (recommended):
+
+```bash
+mkdir -p .claude/skills
+ln -sfn ../../skills/prompt .claude/skills/prompt
+```
+
+User-global:
+
+```bash
+mkdir -p ~/.claude/skills
+cp -a skills/prompt ~/.claude/skills/
+```
+
+### Antigravity CLI (`agy`)
+
+```bash
+mkdir -p .agents/skills
+cp -a skills/prompt .agents/skills/
+```
+
+### Other hosts (Cursor, Copilot, Grok, OpenCode)
+
+Copy `skills/prompt` into that host's skills location. If the host doesn't
+support skills at all, `@prompt.md` / `@.ma/prompt/current.md` (file mention)
+works anywhere the host can see the file — including gitignored files, in
+most hosts. Note that a file mention just reads the content; it doesn't run
+`map pop`, so unlike `/prompt` it won't archive or clear the draft.