apm-triage-panel

# APM Triage Panel -- Single-Issue Triage Orchestration The panel is fixed at **2 mandatory specialist lenses + up to 3 conditional lenses + 1 always-active arbiter = 6 persona sections in one triage comment**. You play each lens in turn from inside a single agent loop (progressive-disclosure skill model -- no sub-agent dispatch). Routing chooses *which* lenses execute; it never changes which headings appear in the final comment. This skill mirrors the `apm-review-panel` orchestration shape on purpose. Same single-comment discipline, same completeness gate, same persona-pass procedure -- only the personas, the rubric, and the output template differ. ## Agent roster | Agent | Persona | Always active? | |-------|---------|----------------| | [DevX UX Expert](../../agents/devx-ux-expert.agent.md) | User-Need Reviewer | Yes | | [Supply Chain Security Expert](../../agents/supply-chain-security-expert.agent.md) | Risk-Surface Reviewer | Yes | | [APM CEO](../../agents/apm-ceo.agent.md) | Triage Arbiter | Yes (always arbitrates) | | [OSS Growth Hacker](../../agents/oss-growth-hacker.agent.md) | Contributor-Tone Reviewer | Conditional (see below) | | [Python Architect](../../agents/python-architect.agent.md) | Architecture Reviewer | Conditional (see below) | | [Doc Writer](../../agents/doc-writer.agent.md) | Documentation Reviewer | Conditional (see below) | Skipped by default: CLI Logging Expert, Auth Expert. Triage operates on issue intent, not on diffs -- those personas are i...