pm-comms-charterlisted

# PM - Communication Charter ## Agent mode (`--agent`) Supports `--agent`: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note. - **No flag** → interactive (default); if inputs are heavy, offer agent mode. - **`--agent`** → obey. First check inputs are complete. Anything missing: do NOT invent it - mark `[ASSUMED - what/why]` in the output and summary. Never hallucinate to fill a gap. --- ## What this skill does Generates two artifacts: 1. **Communication Charter** - Channels, rules, async principles 2. **Meeting Rhythm** - Meeting cadence with clear purpose and outputs --- ## Dependencies **Recommended before running:** - `pm-team-roster` - team size, timezones, and tools directly shape communication setup **Produces artifacts used by:** - All subsequent phases - communication charter is the operational backbone of the project --- ## Step 0: Current state check Check for existing artifacts: - Communication Charter - Meeting Rhythm Also check: does a Team Roster exist? Cross-reference team size and timezones vs. proposed meeting cadence. Look for: tools no longer in use, meeting cadence that doesn't match current project phase, missing async alternatives, escalation path not defined. **Re-run behavior (delta mode):** If a Communication Charter already exists, do not redraft blank. Compare new answers against the existing version, show what changed (tools, cadence, working style), and update on