Add Quarterdeck plugins (quarterdeck-goals, quarterdeck-guard)

SH
16m ago
+14-0

What this PR does

Adds Quarterdeck to the aitmpl marketplace as two external plugins. Each catalog folder holds only source.json, pinned to commit 097c135 (the release branch at v0.31.0) of shannonbay/Quarterdeck (Apache-2.0).

  • plugins/productivity/quarterdeck-goals: path plugins/quarterdeck-goals, the plugin people install.
  • plugins/productivity/quarterdeck-guard: path plugins/quarterdeck-guard. quarterdeck-goals lists it in dependencies, so it has to be in the same marketplace for the install to resolve.

The pin is the release branch, not main, because only release carries the bundled MCP server (plugins/quarterdeck-goals/server/).

Quarterdeck runs standing goals for Claude Code, like "sell my birdcage on Facebook Marketplace" or "find the best new job ads each week". Each goal runs on a schedule in a background subagent, asks before it acts, and remembers what was decided. You approve or reject its proposals from a Goals pane beside the chat.

Type

  • New component
  • Change to an existing component
  • CLI (cli-tool/src, cli-tool/bin)
  • Website (dashboard/)
  • Docs or other

Checklist for components

  • Files are under cli-tool/components/{type}/{category}/ with a kebab-case name (plugins/productivity/quarterdeck-goals and quarterdeck-guard, matching each plugin's name)
  • Frontmatter has name and a specific description (in each .claude-plugin/plugin.json upstream)
  • No API keys, tokens or absolute paths; secrets are read from environment variables
  • If it runs code (hook script, MCP, mod), the README or description says what it runs and what it accesses (plugin READMEs and PRIVACY.md)
  • I did not commit docs/components.json or dashboard/public/ (they are regenerated after merge)

What it runs and accesses

  • MCP server (quarterdeck-goals, started from the plugin's .mcp.json; Node 22.13+ with built-in node:sqlite, no native build): keeps goals, run history, proposals and memory in one local SQLite file in the user's home folder (path overridable with QUARTERDECK_DB).
  • Hooks modules (both plugins): quarterdeck-goals starts due goal runs in background subagents and shows the Goals pane; quarterdeck-guard checks a goal run's tool calls against the autonomy the person set (refusing turned-off kinds of action, holding the rest for approval) and keeps run reports out of the chat.
  • Network: an update check at most every 6 hours that downloads the released plugin.json from raw.githubusercontent.com/shannonbay/Quarterdeck (off with QUARTERDECK_UPDATE_CHECK=0), and one-click unsubscribe requests (RFC 8058) only for unsubscribes the person allowed. Nothing about the user or their goals is sent anywhere. Details in PRIVACY.md.

How I tested it

Before tagging a release, Quarterdeck's release script runs claude plugin test on both plugins plus the unit tests and the live tests of the bundled server over stdio; this commit passed them. Both plugins install from it with claude plugin marketplace add shannonbay/Quarterdeck#release and claude plugin install quarterdeck-goals@quarterdeck.

🤖 Generated with Claude Code


Summary by cubic

Adds two Quarterdeck plugins to the marketplace under cli-tool/components/plugins/productivity/ so users can run standing goals and have a guard that enforces the autonomy they set.

  • New components: quarterdeck-goals (the installable plugin) and quarterdeck-guard (listed as its dependency, so it must live in the same marketplace to resolve), both pinned to shannonbay/Quarterdeck v0.31.0 via commit 097c135.
  • Pinned to the release branch rather than main because only release carries quarterdeck-goals' bundled MCP server.
  • Only source.json is added per component; the catalog (docs/components.json) must be regenerated after merge.
  • No required secrets or environment variables; optional overrides are QUARTERDECK_DB (SQLite file path) and QUARTERDECK_UPDATE_CHECK=0 (disable the update check).