portfolio-communicate
Portfolio Communicate
The single output skill for the portfolio pipeline. Transforms portfolio entities into anything an audience needs — documentation, pitch narratives, proposals, marketing briefs, or data workbooks. It routes through a use-case registry that matches the audience and purpose to the right voice, templates, and review perspectives.
Core Concept
Plugin root resolution. Bash invocations below resolve the plugin root inline as ${CLAUDE_PLUGIN_ROOT:-$(ls -td "$HOME"/.claude/plugins/cache/insight-wave/cogni-portfolio/*/ | head -1)} — the first call works whether or not the harness injects $CLAUDE_PLUGIN_ROOT. Keep the inline form in every call; do not strip it.
Internal portfolio data (slugs, TAM/SAM/SOM, relevance tiers, quality scores) is never what an audience sees. What they need depends on who they are and how they'll consume it:
| Use Case | Audience | Output | Format |
|---|---|---|---|
customer-narrative |
Buyers navigating a portfolio-driven website | Home / About / Capability / Persona / Approach pages, each arc-structured | Markdown with arc_id (per-scope) |
repo-documentation |
Developers, OSS community | Technical clarity: what, how, getting started | Markdown |
pitch |
Executives, conference, board | Arc-structured presentation narrative (cogni-narrative compatible) | Markdown with arc_id |
proposal |
Sales teams, prospects | Per-proposition sales proposal | Markdown |
market-brief |
Marketing teams | Market content package with sizing, buyer profile, messaging | Markdown |
workbook |
Leadership, analysts | Structured spreadsheet with all portfolio data | XLSX |
| Custom/ad-hoc | Any audience | User-defined voice, sections, review | Markdown |