merge: resolve incident-tracker-plugin with origin/main

Author: jack-nsheaps[bot]

.claude-plugin/marketplace.json

@@ -11,7 +11,7 @@
     {
       "name": "1pass",
       "description": "Install and manage 1Password CLI (op) and op-exec in Claude Code sessions. Provides session-start auto-install for web sessions and comprehensive workflow skills.",
-      "version": "0.3.1",
+      "version": "0.3.2",
       "author": {
         "name": "Nathan Heaps"
       },
@@ -268,6 +268,18 @@
         "deep-research"
       ]
     },
+    {
+      "name": "discord",
+      "description": "Discord channel for Claude Code — messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /discord:access.",
+      "version": "0.0.4",
+      "author": {
+        "name": "Nathan Heaps"
+      },
+      "source": "./plugins/discord",
+      "category": "utility",
+      "tags": ["utility", "skill"],
+      "keywords": ["discord", "messaging", "channel", "mcp"]
+    },
     {
       "name": "edit-utils",
       "description": "File editing utilities: auto-formatting and linting for written/edited files with project-aware configuration",
@@ -512,25 +524,6 @@
       "tags": ["utility", "skill"],
       "keywords": ["plugin", "install", "update", "reload", "management"]
     },
-    {
-      "name": "product-development-and-sdlc",
-      "description": "Iterative spec and user story writing with structured SDLC workflows. Guides incremental specification development through research, review, and refinement cycles.",
-      "version": "0.1.1",
-      "author": {
-        "name": "Nathan Heaps"
-      },
-      "source": "./plugins/product-development-and-sdlc",
-      "category": "utility",
-      "tags": ["utility", "skill"],
-      "keywords": [
-        "spec",
-        "specifications",
-        "user-stories",
-        "sdlc",
-        "iterative-development",
-        "product-management"
-      ]
-    },
     {
       "name": "proxmox",
       "description": "Skills for managing Proxmox VE hosts and LXC containers — creating containers, running Docker in LXC, and hosting services like cloudflared.",
@@ -604,7 +597,7 @@
     {
       "name": "scm-utils",
       "description": "Source control management utilities for improving interactions with branches and PRs, both locally and in CI environments",
-      "version": "0.1.14",
+      "version": "0.2.0",
       "author": {
         "name": "Nathan Heaps"
       },
@@ -613,6 +606,27 @@
       "tags": ["utility", "command", "skill"],
       "keywords": ["git", "branch", "pr", "pull-request", "sync", "merge", "scm", "source-control"]
     },
+    {
+      "name": "sdlc-utils",
+      "description": "Software development lifecycle utilities — skills organized by SDLC phase: plan, implement, review, test, deploy, and maintain.",
+      "version": "0.2.0",
+      "author": {
+        "name": "Nathan Heaps"
+      },
+      "source": "./plugins/sdlc-utils",
+      "category": "utility",
+      "tags": ["utility", "skill"],
+      "keywords": [
+        "sdlc",
+        "planning",
+        "implementation",
+        "code-review",
+        "testing",
+        "deployment",
+        "maintenance",
+        "software-engineering"
+      ]
+    },
     {
       "name": "self-terminate",
       "description": "Allows Claude to gracefully terminate itself using SIGINT",

plugins/1pass/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "1pass",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Install and manage 1Password CLI (op) and op-exec in Claude Code sessions. Provides session-start auto-install for web sessions and comprehensive workflow skills.",
   "author": {
     "name": "Nathan Heaps",

plugins/1pass/skills/op-exec/SKILL.md

@@ -150,6 +150,47 @@ also in bash sessions.
 - **Both (default)**: Most common — ensures secrets are available everywhere
   during the session and to all tool types.
 
+## ENVIRONMENT Aggregator Pattern
+
+The `ENVIRONMENT` item in 1Password (e.g., `op://AI-Jack/ENVIRONMENT`) serves as the
+canonical aggregator for all environment variables. Instead of adding separate items to
+`opExec.items`, add new secrets as fields to the ENVIRONMENT item:
+
+1. In 1Password, add a new field to the ENVIRONMENT item with the desired env var name
+   as the label (e.g., `DISCORD_BOT_TOKEN`)
+2. Set the field value to an `op://` reference pointing to the actual secret
+   (e.g., `op://AI-Jack/discord--jack_oat_bot/token`)
+3. op-exec resolves references recursively, so the field value will be the actual secret
+   at runtime
+4. The field label becomes the exported env var name (converted to UPPER_SNAKE_CASE)
+
+This pattern means you only need one item in `opExec.items` (the ENVIRONMENT item) to
+manage all secrets. Adding separate items should be avoided unless the secret doesn't
+fit the aggregator pattern.
+
+### Example
+
+```
+ENVIRONMENT item fields:
+- TELEGRAM_BOT_TOKEN = op://AI-Jack/telegram-bot/token
+- DISCORD_BOT_TOKEN = op://AI-Jack/discord--jack_oat_bot/token
+- BRAINTRUST_API_KEY = op://AI-Jack/braintrust/api-key
+```
+
+### Plugin Config with Aggregator
+
+When using the aggregator pattern, the plugin config is minimal — just one item:
+
+```yaml
+1pass:
+  opExec:
+    items:
+      - "op://AI-Jack/ENVIRONMENT"
+```
+
+All env vars are managed by adding/removing fields on that single 1Password item,
+rather than editing plugin configuration.
+
 ## Troubleshooting
 
 ### "op-exec: command not found"

plugins/discord/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "name": "discord",
+  "description": "Discord channel for Claude Code \u2014 messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /discord:access.",
+  "version": "0.0.4",
+  "author": {
+    "name": "Nathan Heaps",
+    "email": "nsheaps@gmail.com",
+    "url": "https://github.com/nsheaps"
+  },
+  "homepage": "https://github.com/nsheaps/ai-mktpl/tree/main/plugins/discord",
+  "repository": "https://github.com/nsheaps/ai-mktpl",
+  "keywords": ["discord", "messaging", "channel", "mcp"]
+}

plugins/discord/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "discord": {
+      "command": "bun",
+      "args": ["run", "--cwd", "${CLAUDE_PLUGIN_ROOT}", "--shell=bun", "--silent", "start"]
+    }
+  }
+}

plugins/discord/.npmrc

@@ -0,0 +1 @@
+registry=https://registry.npmjs.org/

plugins/discord/ACCESS.md

@@ -0,0 +1,143 @@
+# Discord — Access & Delivery
+
+Discord only allows DMs between accounts that share a server. Who can DM your bot depends on where it's installed: one private server means only that server's members can reach it; a public community means every member there can open a DM.
+
+The **Public Bot** toggle in the Developer Portal (Bot tab, on by default) controls who can add the bot to new servers. Turn it off and only your own account can install it. This is your first gate, and it's enforced by Discord rather than by this process.
+
+For DMs that do get through, the default policy is **pairing**. An unknown sender gets a 6-character code in reply and their message is dropped. You run `/discord:access pair <code>` from your assistant session to approve them. Once approved, their messages pass through.
+
+All state lives in `~/.claude/channels/discord/access.json`. The `/discord:access` skill commands edit this file; the server re-reads it on every inbound message, so changes take effect without a restart. Set `DISCORD_ACCESS_MODE=static` to pin config to what was on disk at boot (pairing is unavailable in static mode since it requires runtime writes).
+
+## At a glance
+
+|                |                                                     |
+| -------------- | --------------------------------------------------- |
+| Default policy | `pairing`                                           |
+| Sender ID      | User snowflake (numeric, e.g. `184695080709324800`) |
+| Group key      | Channel snowflake — not guild ID                    |
+| Config file    | `~/.claude/channels/discord/access.json`            |
+
+## DM policies
+
+`dmPolicy` controls how DMs from senders not on the allowlist are handled.
+
+| Policy              | Behavior                                                                                                                           |
+| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
+| `pairing` (default) | Reply with a pairing code, drop the message. Approve with `/discord:access pair <code>`.                                           |
+| `allowlist`         | Drop silently. No reply. Use this once everyone who needs access is already on the list, or if pairing replies would attract spam. |
+| `disabled`          | Drop everything, including allowlisted users and guild channels.                                                                   |
+
+```
+/discord:access policy allowlist
+```
+
+## User IDs
+
+Discord identifies users by **snowflakes**: permanent numeric IDs like `184695080709324800`. Usernames are mutable; snowflakes aren't. The allowlist stores snowflakes.
+
+Pairing captures the ID automatically. To add someone manually, enable **User Settings → Advanced → Developer Mode** in Discord, then right-click any user and choose **Copy User ID**. Your own ID is available by right-clicking your avatar in the lower-left.
+
+```
+/discord:access allow 184695080709324800
+/discord:access remove 184695080709324800
+```
+
+## Guild channels
+
+Guild channels are off by default. Opt each one in individually, keyed on the **channel** snowflake (not the guild). Threads inherit their parent channel's opt-in; no separate entry needed. Find channel IDs the same way as user IDs: Developer Mode, right-click the channel, Copy Channel ID.
+
+```
+/discord:access group add 846209781206941736
+```
+
+With the default `requireMention: true`, the bot responds only when @mentioned or replied to. Pass `--no-mention` to process every message in the channel, or `--allow id1,id2` to restrict which members can trigger it.
+
+```
+/discord:access group add 846209781206941736 --no-mention
+/discord:access group add 846209781206941736 --allow 184695080709324800,221773638772129792
+/discord:access group rm 846209781206941736
+```
+
+## Mention detection
+
+In channels with `requireMention: true`, any of the following triggers the bot:
+
+- A structured `@botname` mention (typed via Discord's autocomplete)
+- A reply to one of the bot's recent messages
+- A match against any regex in `mentionPatterns`
+
+Example regex setup for a nickname trigger:
+
+```
+/discord:access set mentionPatterns '["^hey claude\\b", "\\bassistant\\b"]'
+```
+
+## Delivery
+
+Configure outbound behavior with `/discord:access set <key> <value>`.
+
+**`ackReaction`** reacts to inbound messages on receipt as a "seen" acknowledgment. Unicode emoji work directly; custom server emoji require the full `<:name:id>` form. The emoji ID is at the end of the URL when you right-click the emoji and copy its link. Empty string disables.
+
+```
+/discord:access set ackReaction 🔨
+/discord:access set ackReaction ""
+```
+
+**`replyToMode`** controls threading on chunked replies. When a long response is split, `first` (default) threads only the first chunk under the inbound message; `all` threads every chunk; `off` sends all chunks standalone.
+
+**`textChunkLimit`** sets the split threshold. Discord rejects messages over 2000 characters, which is the hard ceiling.
+
+**`chunkMode`** chooses the split strategy: `length` cuts exactly at the limit; `newline` prefers paragraph boundaries.
+
+## Skill reference
+
+| Command                                        | Effect                                                                                             |
+| ---------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| `/discord:access`                              | Print current state: policy, allowlist, pending pairings, enabled channels.                        |
+| `/discord:access pair a4f91c`                  | Approve pairing code `a4f91c`. Adds the sender to `allowFrom` and sends a confirmation on Discord. |
+| `/discord:access deny a4f91c`                  | Discard a pending code. The sender is not notified.                                                |
+| `/discord:access allow 184695080709324800`     | Add a user snowflake directly.                                                                     |
+| `/discord:access remove 184695080709324800`    | Remove from the allowlist.                                                                         |
+| `/discord:access policy allowlist`             | Set `dmPolicy`. Values: `pairing`, `allowlist`, `disabled`.                                        |
+| `/discord:access group add 846209781206941736` | Enable a guild channel. Flags: `--no-mention`, `--allow id1,id2`.                                  |
+| `/discord:access group rm 846209781206941736`  | Disable a guild channel.                                                                           |
+| `/discord:access set ackReaction 🔨`           | Set a config key: `ackReaction`, `replyToMode`, `textChunkLimit`, `chunkMode`, `mentionPatterns`.  |
+
+## Config file
+
+`~/.claude/channels/discord/access.json`. Absent file is equivalent to `pairing` policy with empty lists, so the first DM triggers pairing.
+
+```jsonc
+{
+  // Handling for DMs from senders not in allowFrom.
+  "dmPolicy": "pairing",
+
+  // User snowflakes allowed to DM.
+  "allowFrom": ["184695080709324800"],
+
+  // Guild channels the bot is active in. Empty object = DM-only.
+  "groups": {
+    "846209781206941736": {
+      // true: respond only to @mentions and replies.
+      "requireMention": true,
+      // Restrict triggers to these senders. Empty = any member (subject to requireMention).
+      "allowFrom": [],
+    },
+  },
+
+  // Case-insensitive regexes that count as a mention.
+  "mentionPatterns": ["^hey claude\\b"],
+
+  // Reaction on receipt. Empty string disables.
+  "ackReaction": "👀",
+
+  // Threading on chunked replies: first | all | off
+  "replyToMode": "first",
+
+  // Split threshold. Discord rejects > 2000.
+  "textChunkLimit": 2000,
+
+  // length = cut at limit. newline = prefer paragraph boundaries.
+  "chunkMode": "newline",
+}
+```

plugins/discord/CHANGES.md

@@ -0,0 +1,15 @@
+# Changes from upstream
+
+This plugin is derived from Anthropic's official
+[Discord channel plugin](https://github.com/anthropics/claude-code/tree/main/packages/channel-discord)
+(Apache-2.0). The following modifications were made for use in the `ai-mktpl`
+marketplace:
+
+- **Bot message support** -- the upstream server ignores all bot-authored
+  messages. This fork processes messages from other bots, which enables
+  multi-agent relay scenarios (e.g. a bridge bot forwarding from another
+  platform). Messages from the bot's own user ID are still ignored to prevent
+  self-loops.
+- **Self-message guard** -- an explicit check against the bot's own user ID
+  (`client.user.id`) replaces the blanket `message.author.bot` filter, so only
+  the bot's own messages are dropped.