Roadmap: agent-plugins marketplace — reach & feature-completeness

[devantler]

🤖 Generated by the Agentic Engineer

Agent Plugins provides category-based bundles for VS Code, GitHub Copilot CLI, and Claude Code. The marketplace packages skills, specialist agents, and tool connections. The remaining work is reliable consumption, tested operating contracts, and usable versioned distribution.

The catalogue contains 7 plugins, 25 skills, 5 agents, and one MCP server (verified 2026-09-06). The Flux bundle includes its MCP connection and troubleshooter; agentic-engineering includes the engineer, surveyor, and improver. Version 5 requires explicit maintainer opt-in for spend stewardship, disabled by default.

CI checks marketplace and plugin-manifest parity, catalogue resource counts, upstream skill provenance, protected synced-skill trees, content-version bumps, and desired-state digests. Packaging checks do not establish hands-on discovery in every supported application.

The roadmap has four delivery themes:

• Verify installation and discovery: Verify VS Code discovery of bundled plugin agents and settle the agent filename convention #74 owns agent-picker discovery, unchanged agent names, and usable tool identifiers across the supported consumers.
• Complete reusable autonomous roles: feat: extract the generic "Automated AI Engineer" core into a dedicated plugin #51 owns consumer convergence; Productize the agent-improver routine as a first-class plugin capability #76 owns first-class improver consumption and verification. Deployment facts remain in the consumer contract.
• Make the surveyor dependable: test(agentic-engineering): port the surveyor contract guards upstream #95 ports generic contract guards upstream; The surveyor forge-guard adapter is declared unconditionally required but documented as conditionally installed #161 reconciles adapter installation requirements; The surveyor cannot resolve the default-branch CI classifier's admitted path, so rung 0 is blind on every repository #200 makes the guarded classifier discoverable while preserving command restrictions.
• Version the marketplace as a distribution: feat(ci): cut semver releases so the marketplace has a version to pin #101 provides repository-level releases and release notes while preserving independent plugin versions.

Catalogue expansion and richer discovery metadata remain follow-on directions. Additions should address demonstrated user needs, fit coherent categories, and satisfy the supported consumers' manifest contracts. Existing actionable work takes priority over new inventory.

Completion is measured by the linked issues' acceptance criteria and verified consumer behavior. Native sub-issues carry ownership and progress; this epic does not duplicate their status histories.