Team Plugins · Marketplace 1.148.0

Know what to run. Know when to stop.

Start with the outcome, not the package name. Get the exact MoxyWolf sequence, required inputs, deliverable, human gate, and stop condition.

October 25, 2026 · changes since the October 14 guide

What changed in the field

Shipped in source

Goal merge, usability, Production

gstack 0.94.0 adds co-authored goal briefs and /gstack-usability. GO-011 permits the final bot merge after four green checks and clean whole-goal review. Usability and the Production yes follow separately.

Follow the current goal lifecycle
Shipped in source

Shared work has a shared home

Project-init 0.43.0 routes org-shared work to GitHub/Projects, with shared rules and gate logs there. Personal projects can remain in Taskade. Chief of Staff 0.3.1 logs to the declared project workspace.

Resolve the right workspace
Shipped in source

Scored decisions before routing

Council 0.12.0 adds a three-voice decision quorum. Its caller-specific gate requires scored outcomes before the majority can steer a decision; unavailable answers and ties stay explicit.

Read the routing evidence limits

Catalog: 50 packages, 233 active skills, 135 commands and 12 direct agents. Nine package versions changed. Academic Pipeline and SCAMPER remain at 0.7.0, and the ten department-agent structure is unchanged. REA, diagram-design and Understand-Anything remain upstream pointers, not bundled implementations.

Verification boundary: inventory and operating instructions are source-verified at 54bfcfc. The repository’s MR-003 live-hook validation and CS-007 live /cos dispatch tagging are still unverified. A source merge and passing CI do not establish live host behavior. /cos-brief and /cos-review remain planned.

From orientation to execution

Complete operating guides

Use the quick runbooks to choose a path, then open the full guide for prerequisites, gates, commands, outputs, and recovery conditions.

New · flagship operating layer

Daily Briefings: see the work your calendar misses

It reads your calendar, inbox, and every configured work surface to expose real clashes, unprepped deadlines, open loops, renewals, approvals, and automations that will fire without you. The calendar and morning brief are read-only. CRM sync health can now make two bounded bookkeeping repairs: sweep running rows older than two hours and release an eligible dead-lettered sync_tasks row at most once a day, excluding budget overruns.

  1. 01Configureowner + surfaces
  2. 02Look aheadcommitments + clashes
  3. 03Start todaymorning brief
  4. 04Trust silencesource state disclosed

Featured lens

Competitive intelligence

Do not reduce competitor work to a web search. The suite can join market evidence, SEO visibility, pricing architecture, customer language, product implications, and an explicit decision review.

  1. 01Researchsources + category
  2. 02Observesearch + visibility
  3. 03Normalizeoffers + pricing
  4. 04Decidegaps + moves

Ten operating missions

Scenario atlas

50 runbooks cover the path from market sensing through execution, learning, and durable memory.

Verified marketplace inventory

All 50 catalog entries

Each entry is a runnable package, hook/runtime infrastructure or an upstream-install pointer. Presence in this source catalog does not prove installation or runtime access.

50 entries

Extend the core

Companion ecosystem

These are not part of the 50-package MoxyWolf count. They provide live systems and specialist evidence used by the runbooks.

Companion

Apollo

B2B account discovery, contact enrichment, and reviewable prospect lists.

The core suite needs net-new account or contact data before CRM deduplication and qualification.
Companion

MailForge

Domains, mailboxes, DNS authentication, and outbound email infrastructure.

Approved cold-outbound work needs dedicated sending infrastructure before any sequence can run.
Companion

SalesForge

Approved email and LinkedIn outbound sequences, sending, replies, and performance reporting.

Qualified prospects and ready sending infrastructure must become a reviewed outbound sequence.
Companion

Ahrefs

SEO, backlinks, keyword gaps, competitor visibility, and AI share of voice.

Competitive analysis needs externally observed search evidence.
Companion

Clarify

CRM source of truth for accounts, contacts, deals, activities, and deduplication.

A workflow needs CRM deduplication, customer context, segmentation, or pipeline truth.
Companion

QuickBooks

Accounting system of record for margin, cash, close, invoices, and payroll.

Operational decisions need financial truth.
Companion

Figma

Design source, design systems, implementation handoff, and interface review.

A product or campaign needs collaborative visual design.
Companion

GitHub

Repository, issues, pull requests, reviews, and delivery evidence.

Engineering work crosses the source-control boundary.
Companion

Taskade

Personal-project engineering source material and design mirrors; org-shared projects use GitHub/Projects workspaces.

The declared project is personal and its workspace is in Taskade; shared projects retain redirects rather than a second canonical home.
Companion

Vercel

Project and deployment lookup, preview inspection, CI/CD guidance, preview verification, and conditional environment-variable handling.

A repository is hosted on Vercel and its user-visible change needs preview-to-production evidence.
Companion

Endform

Cloud execution of a repository's Playwright suite against Vercel preview deployments.

A Vercel-hosted repository needs the gstack pull-request E2E gate; it runs in GitHub Actions rather than through a connector.
Companion

Playwright

Meaningful browser smoke and acceptance tests for user-visible behavior.

A web acceptance criterion must be proven locally or against a deployed preview.
Companion

Codex

Builder, checker, or bounded review participant for an explicitly permitted task-graph packet.

gstack dispatch assigns it a declared node with frozen inputs and outputs.
Companion

Claude Code

Builder, checker, or bounded cross-tool peer reviewer for an explicitly permitted task-graph packet.

gstack needs an independent tool to check evidence or review a committed revision.
Companion

Google Drive

Shared Docs, Sheets, Slides, and durable working files.

A workflow needs collaborative source material or deliverables.
Companion

PostHog

First-party product events, funnels, cohorts, experiments, and lifecycle workflow orchestration.

Marketing or email decisions need behavioral evidence beyond acquisition.
Companion

Resend

Transactional and lifecycle email transport for approved product messages.

A reviewed lifecycle sequence is ready to be staged or sent by the product runtime.
Companion

Slack

Team communication, digests, decisions, and operating visibility.

A private workflow must become team-visible.
Companion

Supabase

Postgres, authentication, storage, migrations, and runtime diagnostics.

A product build needs managed application infrastructure.
Companion

Composio Router

Fallback access to SaaS tools without a native connector.

No supported first-party connector exists.

Practical setup and handoffs

Start in the right environment

Engineering setup

Install and authenticate Claude Code and Codex for the normal build/review loop. Two-reviewer design mode also needs a second non-writer reviewer family, such as Gemini. Vercel is a companion integration, not a Team Plugin. Endform runs in GitHub Actions without a dedicated connector.

Repository diagrams

Use /excalidraw or /excalidraw-here with a writable Obsidian vault and its Excalidraw plugin. Pin the commit, read committed source, trace real calls, attach one Sources row per claim, then run check_repo_diagram.py. Report citation validity and later code drift separately.

Read diagram requirements

Publishing and daily work

/blog-publish prepares a local commit; the writer makes the final push through GitHub Desktop. /sprint-day plans focus blocks, records evidence and can send an owner-only close email. Neither workflow should be described as universally read-only.

Understand-Anything, REA and diagram-design are upstream-install pointers. Model-router is hook/runtime infrastructure with no slash command. Updating the marketplace does not prove every plugin is installed or refreshed.