Files

Defame1297 e3e43502db docs(kyberforge): add component-selection research closing the when-to-use gap

## 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

2026-06-28 20:49:05 +00:00

research

docs(kyberforge): add component-selection research closing the when-to-use gap

2026-06-28 20:49:05 +00:00

README.md

chore(kyberforge): move research docs under docs/research/ and update README

2026-06-23 17:18:20 +00:00

README.md

docs/

Plugin documentation. Not read automatically by Claude Code or GitHub Copilot CLI — reference specific files from skill bodies or agent prompts as needed.

Files

Path	Purpose
`plugin-marketplace-architecture.md`	Claude Code vs Copilot CLI divergence, two-manifest pattern, plugin constraints, cross-tool compatibility
`adding-agents.md`	How to add agent definitions to the kyberforge plugin

research/

Upstream reference material gathered during skill authoring. Not shipped with the plugin — used at development time only.

Path	Purpose
`research/docs/agentskillsio/`	agentskills.io spec, skill authoring, description optimization, eval design, scripts
`research/docs/agentsmd/`	agents.md format spec and cross-tool configuration reference
`research/examples/skill-write/`	Upstream skill examples reviewed when authoring skill-write and skill-audit