Defame1297
e3e43502db
## Why The existing kyberforge research covered skills vs agents (ADR-0010), Copilot track selection, and agent scope hierarchy — but had no documented basis for three practical decisions: when to use MCP servers vs skills vs agents, when hooks are the right tool vs skills, and when bin/ is appropriate vs scripts/ inside a skill directory. Without this, the plugin-author and agent-author skills have no research backing for those choices. ## Implementation Notes Sourced from official Claude Code plugin docs (code.claude.com), official GitHub Copilot CLI docs (docs.github.com), and the Copilot customization-cheat-sheet and comparing-cli-features pages — the latter containing the only official "putting it together" decision table across components. Context7 MCP was the primary retrieval mechanism; web reads deepened the hooks and bin/ content. Three files produced: - overview.md — mental model, component roles, cross-provider portability - decision-guide.md — explicit decision tables for all three gaps, including anti-patterns and Copilot surface support matrix - hooks.md — full lifecycle event reference, stdin/stdout schema, hookSpecificOutput per event, plugin scope restriction Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0147vXtL5sP6vorDdqXGJJU9