capability-synthesizerlisted

# Capability Synthesizer Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: `PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"`), otherwise the absolute path of this skill folder's `../..`. Build one cohesive result from a broad capability corpus. The internet and public repositories are the primary corpus; local skills are supplementary evidence and candidate implementations. Candidates are evidence, not merge targets. ## Target Contract Before discovery, write a compact contract: ```json { "capability": "short target", "primary_target": "named skill/plugin/MCP/capability to create or strengthen", "named_targets": ["@plugin-or-$skill explicitly named by the user"], "cwd_role": "workspace | source-reference | target", "mode": "new-skill | augment-existing | plugin-pack | source-import | reference-only", "artifact_type": "skill | plugin | mcp | mixed | report", "install_scope": "global-agent | repo-local | workspace-snapshot | reference-only", "install_required": false, "destination_path": "chosen source or install path", "marketplace_path": "only when global marketplace activation is required", "trigger_model": ["task context, artifacts, evidence, or agent decision point that should invoke the capability"], "core_workflows": ["workflow 1"], "non_goals": ["excluded behavior"], "must_keep_capabilities": ["capability that must su