Add meeting-summarizer skill to project-management plugin

[RomarQ]

Summary

Adds a meeting-summarizer skill that converts a meeting transcript into a structured summary, classifying every item as Decision, Action Item, Discussion, or Open Question. The skill's purpose is to prevent the usual "discussed X" → "decided X" inflation that auto-summarizers produce.

What it does

• Enforces classification rules (decisions need an explicit confirmation, action items need a named owner + concrete task)
• Strips transcription noise: timestamps, AI-generated footers, pleasantries
• Filters out meeting-logistics tasks ("share the recording", "schedule a follow-up") from action items
• In file mode, discovers the project's meeting-summaries directory (meeting-summaries/, meetings/, notes/meetings/, docs/meetings/) and follows the existing naming convention
• In file mode, runs a terminology pass against any project glossary (glossary.md, terminology.md, or a glossary section in CLAUDE.md / AGENTS.md) and rewrites transcription-mangled terms to the canonical form

[timbrinded]

there are two many ## level headings which means its hard to process (as a human) - i can imagine greater nesting helping LLMs prioritise but who knows these days.

The skill also co-mingles operational rules (e.g. collision check) with summary rules (e.g. summary rules).

Consider adding a stricter structure to the context in the skill so operation is streamlined and it's less cognitive burden on LLM.

As it stands i think this skill is probably fine on a SOTA model - but would probably struggle on a crappier model.

[RomarQ]

there are two many ## level headings which means its hard to process (as a human) - i can imagine greater nesting helping LLMs prioritise but who knows these days.

The skill also co-mingles operational rules (e.g. collision check) with summary rules (e.g. summary rules).

Consider adding a stricter structure to the context in the skill so operation is streamlined and it's less cognitive burden on LLM.

As it stands i think this skill is probably fine on a SOTA model - but would probably struggle on a crappier model.

Have improved it and added a usage guide