Cross-engine support: Agency plugin (MCP + hooks) → public Claude Code plugin

[vidhartbhatia]

Summary

Expand brag-sheet from Copilot CLI-only to work across both Copilot CLI and Claude Code, using Agency as the internal distribution layer and MCP as the universal tool protocol.

Product Strategy

Phase 1: Agency Plugin (internal Microsoft)

• Goal: All MSFT employees using Agency can auto-track work
• Distribution: XPASS marketplace (skill-only PR already open)
• Build: MCP server wrapping lib/ modules (3 tools) + hooks.json for session lifecycle
• Key insight: Agency abstracts the engine — one plugin works with both agency copilot and agency claude

Phase 2: Public Claude Code Plugin

• Goal: External visibility, works for any Claude Code user
• Distribution: Claude Code plugin marketplace, npm

Architecture

• lib/ (shared core, zero deps) — already done
• mcp-server.mjs (NEW) — MCP stdio server exposing 3 tools
• hooks.json (NEW) — session start/end lifecycle
• .claude-plugin/plugin.json (NEW) — plugin manifest
• extension.mjs — continues working for standalone Copilot CLI

What needs building

1. MCP server (~100-150 lines)
2. hooks.json for session lifecycle
3. Plugin manifest (.claude-plugin/plugin.json)

References

• Agency plugin docs: 1esgitops/_git/agency
• awesome-copilot skill: merged (PR #1428)
• Copilot CLI bug #3023

[vidhartbhatia]

Strategic priority order (2026-05-11)

After shipping v1.1.0 (copilot-brag-sheet@1.1.0 on npm with copilot-brag-sheet-mcp bin), the host-coverage order is:

1. Copilot CLI — shipped, must stay working. extension.mjs joinSession({ onSessionStart, onPostToolUse }) is the auto-capture surface.
2. Agency Copilot — Phase 1 of this issue. One Agency plugin serves both engines.
3. Agency Claude — same Agency plugin (the engine is abstracted by Agency).
4. Claude Code — Phase 2 here / Explore Claude Code plugin packaging #19. Hooks bundle at ~/.claude/hooks/{PostToolUse,SessionEnd} + a 4th bin.
5. Then VSCode, Cursor, Codex — per-host integration kits.

"Automated" means passive auto-capture like the Copilot CLI hook surface, not just on-demand tool calls. Each host needs its own lifecycle hook layer because MCP itself is request-response — the spec has no onPostToolUse analog. That gap is the single biggest blocker to a unified codebase across all hosts.

Long-term goals

• Unified codebase using common SDKs and patterns (one extension serves all hosts).
• Continuously simpler install — native marketplaces and awesome-list visibility.

Immediate next work

Phase 1 scaffolding (hooks.json + .claude-plugin/plugin.json wrapping mcp-server.mjs) is the next dev task.