capability-workbenchlisted

# Capability Workbench Author and govern reusable skills, plugins, agent guidance, trigger contracts, and capability portfolios. Runtime operation, orchestration, and harness reliability belong to Agent Harness. Installation and cache refresh are explicit activation steps, never automatic authoring side effects. ## Plugin Root Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell): the host-provided plugin root, or the absolute path of this skill folder's `../..`. Scripts, references, and sibling skills live under that root. ## Route The Work Choose one primary lifecycle lane before making changes: | Lifecycle lane | Capability situation | Use | Output | | --- | --- | --- | --- | | Frame | Behavior gaps plus trusted sources -> design | `capability-synthesizer` | Evidence, decisions, skill/plugin | | Frame | Split, merge, move, delete, router, shared mechanics, or ownership boundaries | `capability-portfolio-architect` | Decision ledger and structural plan | | Frame | Names, descriptions, trigger metadata, or catalog survivability | `skill-trigger-metadata` | Trigger contract and probes | | Author | Create or refactor one portable skill | `skill-factory` | Skill folder and validation | | Author | Create/update a marketplace plugin | `plugin-factory` | Plugin, manifests, validation | | Author | Create/refresh AGENTS.md, CLAUDE.md, or scoped rules | `agent-guidance-factory` | Guidance and precedence checks | | Assure/evolve | Compare a capability change wit