capability-portfolio-architect

# Capability Portfolio Architect 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 `../..`. Use this when a capability set may have the wrong shape. This skill owns structural decisions across skills and plugins. Decisions include keep, split, merge, remove, rename, route, move skills between plugins, extract shared capability patterns, move detail to references, extract deterministic scripts, or create a new skill/plugin boundary. ## Boundary - Token or term overlap is never enough to delete, move, split, or merge. - Transfer trigger coverage, safety boundaries, commands, output contracts, install surface, validators, and rollback paths before structural edits. - Use `context-density` first when the primary problem is context cost, hot-path prose, prompt contracts, or measured placement. - Use this skill when measurement exposes overlapping skills, missing routers, overloaded skills, duplicated workflows, bad plugin boundaries, or cross-plugin responsibility overlap. - Also use it when hot-path examples belong in references, deterministic procedures hide in prose, or obsolete skills need review. - Use `skill-trigger-metadata` for final name/description trigger wording after the target architecture is chosen. - Use `skill-factory` or `plugin-factory...