Proposal: New pm-governance plugin — decision governance layer (4 skills, 3 commands)

## Summary Proposing a new `pm-governance` plugin that adds a **decision governance layer** on top of the existing pm-skills ecosystem. While your plugins handle PM *execution* (what to do), this plugin handles *when to pause and how to decide* — preventing the most expensive PM mistake: building the wrong thing at full speed. ## Proposed Plugin: `pm-governance` ### 4 Skills | Skill | Description | Auto-invokes when... | |-------|------------|---------------------| | `clarification-gate` | Asks max 5 clarifying questions before any build; states assumptions first, then confirms | User says "build", "implement", "create", "design" | | `honest-evaluator` | 6-part evaluation framework: strengths (specific mechanisms only), fatal flaws, hidden costs, risk heatmap, verdict (BUILD NOW / LATER / DIFFERENTLY), alternative | User says "should we build", "evaluate", "pros and cons" | | `adr-creator` | Generates Architecture Decision Records with cost analysis at 4 scale tiers (MVP / 10K / 1M / 100M users) | User mentions database, infrastructure, scaling, "X or Y" | | `instruction-auditor` | Detects anti-patterns in CLAUDE.md and skills (>200 lines, linting rules in CLAUDE.md, vague descriptions) and suggests specific fixes | User asks to review setup or output quality is declining | ### 3 Commands | Command | Description | What it chains | |---------|------------|---------------| | `/act [goal]` | Structured 5-Act experience: Context → Discovery → Design (pause) → Implementation...