docs: community roadmap, unified plugin strategy, industry workflow-pack template - #139
Merged
Conversation
Community-facing commitment doc: explicit not-abandoned statement with a maintenance SLO for every shipped plugin, the one-marketplace/two-consumers architecture (Claude Code install + Conduit catalog ingestion), what shipped in the official-format alignment wave (#136/#137, conduit#917), the first four industry workflow packs, contribution pointers, and the semver + bump-gate release policy.
…cture Single design note defining what a workflow pack is (job-shaped, cross-vendor, gateway-wired) vs a vendor plugin, the exemplar ops-pack directory layout, official-frontmatter snippets for pack skills/agents/commands, the .mcp.json gateway wiring, marketplace entry with category workflow-pack, composition and missing-connector rules, and a definition of done for new packs.
New /getting-started/roadmap/ page for mcp.wyre.ai presenting the roadmap for customers: the open-marketplace commitment, one catalog consumed by Claude Code and Conduit, recent shipping highlights, the four upcoming industry workflow packs, and follow-along links. One-line Sidebar registration under Getting Started.
Time-bound support commitments (2-day ack, 1-week regression fix, 90-day deprecation notice) were a draft's guess at what sounds credible, not a commitment WYRE has actually signed up to operationally. Keep the one guarantee that's mechanically true today — CI-enforced installability and no-silent-removal via the changelog — and drop the rest rather than publish numbers nobody agreed to.
asachs01
added a commit
that referenced
this pull request
Jul 14, 2026
…#142) * feat(ops-pack): add MSP Operations workflow pack Cross-vendor service-desk operations plugin: board health, dispatch prioritization, SLA escalation, and shift handoffs across whatever PSA/RMM is connected through the WYRE MCP Gateway (Conduit). First of four planned industry workflow packs (see ROADMAP.md draft in #139). - skills: sla-escalation-playbooks, dispatch-prioritization, board-hygiene - agents: board-health-auditor, stale-ticket-chaser, dispatch-coordinator - commands: /ops-pack:morning-huddle, /ops-pack:sla-breaches, /ops-pack:eod-handoff marketplace.json intentionally not touched — registered separately. * feat(finance-pack): add Finance & Billing industry workflow pack Cross-vendor billing and agreement reconciliation pack: PSA contracts vs accounting invoices (agreement-reconciliation), marketplace subscription vs billed vs deployed seats (license-true-up), and per-client margin (margin-analysis), each with agents (billing-drift-detector, renewal-calendar-builder, profitability-ranker) and slash commands (month-end-recon, true-up, renewals). Connects via Conduit per the industry-workflow-packs roadmap; never hardcodes a single PSA/accounting/ distributor vendor and degrades explicitly when a connector is absent. * feat(secops-pack): add Security Operations workflow pack Cross-vendor alert triage and incident response across whatever EDR/MDR/SIEM stack is connected (Huntress, Blackpoint Cyber, SentinelOne, Blumira, SaaS Alerts, CIPP, etc.). Adds three skills (severity normalization, containment playbooks, BEC response), three agents (overnight-alert-summarizer, incident-timeline-builder, tenant-exposure-ranker), and three commands (portfolio-sweep, incident-report, tenant-exposure), all discovering connected tools via conduit__search_tools rather than hardcoding a vendor. Not yet registered in .claude-plugin/marketplace.json — a sibling process combines all workflow-pack marketplace entries in a follow-up change. * feat(compliance-pack): add Compliance industry workflow pack Cross-vendor compliance evidence collection and control drift detection against CIS/SOC 2/HIPAA and cyber-insurance questionnaires, grounded in CIPP, Liongard, and IT Glue via the Conduit MCP Gateway. - skills: evidence-mapping, standards-drift, insurance-questionnaires - agents: evidence-packager, control-drift-reporter, questionnaire-autofiller - commands: /compliance-pack:evidence-pack, :drift-report, :questionnaire Not yet registered in .claude-plugin/marketplace.json — combined by a separate process alongside the sibling ops-pack/secops-pack/finance-pack industry workflow packs. * feat(marketplace): register the four industry workflow packs Adds ops-pack, secops-pack, finance-pack, compliance-pack to marketplace.json under a new workflow-pack category and regenerates docs/src/data/plugins.ts. Marketplace version 1.15.0 -> 1.16.0. Verification: node scripts/check-marketplace-drift.mjs --base origin/main passes (68 entries, bump-gate clean — 4 new plugins, nothing to bump); claude plugin validate . passes; docs Astro build passes (144 pages).
Mechanical/accuracy-only fixes to a stale draft (opened 2026-07-14): plugin count 63 -> 81 (live marketplace.json), #137 and conduit#917 status "in review" -> merged (both actually merged 2026-07-13, minutes after this draft was written), and corrected the CI hard-fail claim -- #137 merged but per-plugin validation is still advisory pending a follow-up cleanup, not yet flipped. Does NOT touch the roadmap's positioning/commitment content (industry workflow-pack scope, timelines, the "not being abandoned" stance) -- that's held pending Aaron's sign-off per boss, not a mechanical fix. Authored-by: scribe <scribe@wyre-internal>
Collaborator
Author
|
Automated review (forge): Reviewed the diff:
The PR author flags two things as needing Aarons explicit sign-off before merge, and I agree those are the real decision points here rather than anything technical: (1) the SLO numbers (2-day ack, 1-week regression fix, 2-week Production-tier breakage fix, 90-day deprecation notice) become public commitments on merge, and (2) the No concerns beyond those two flagged decision points. Safe to merge once Aaron confirms the SLOs and naming. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The public commitment piece of the marketplace work (#136/#137/#138 shipped the mechanics; this states the direction).
/plugin marketplace add, Conduit via skills-catalog ingestion — conduit#917), what shipped, and the four planned industry workflow packs (ops-pack, secops-pack, finance-pack, compliance-pack) with named example skills/agents/commands._templates/workflow-pack-template/README.md) — one exemplar structure, not a 50-file scaffold: compose-don't-duplicate rule, real gateway tool names, explicit missing-connector degradation, frontmatter matching the post-refactor: migrate all plugin frontmatter to official Claude Code formats #137 official formats.Review wanted on two things
ops-pack/secops-pack/finance-pack/compliance-packbecome command namespaces (/ops-pack:morning-huddle); rename now or never.Verification
Astro build green (140 pages, roadmap emitted, nav renders); drift/bump-gate clean (0 plugins touched); relative links resolve.