Quality-improve 10 v7.0.0-era engineering skills

Applies three consistent fixes across the v7.0.0 batch:
- Rename `## Output Structure` → `## Output Format` for consistency
- Wrap output template in `---` document separators (code-review-checklist,
  debugging-log-analyser needed full structural upgrade; remaining 8 already
  had the wrapper)
- Remove `## Example Trigger Phrases` section from all 10 skills

Skills updated: code-review-checklist, debugging-log-analyser,
changelog-generator, pr-description-writer, system-design-interview,
test-strategy-doc, runbook-writer, incident-postmortem, api-docs-writer,
architecture-decision-record

Both `skills/` and `plugins/pm-engineering/skills/` copies synced.

https://claude.ai/code/session_01C3HwChrccJd145vJ6Z7ajF

plugins/pm-engineering/skills/debugging-log-analyser/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: debugging-log-analyser
-description: "Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when sharing a log, stack trace, error output, or crash dump. Produces a structured diagnosis with probable root cause, affected code path, suggested fix, and next debugging steps. Optimised for Opus 4.7 and newer models."
+description: "Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when sharing a log, stack trace, error output, or crash dump. Produces a structured diagnosis with probable root cause, affected code path, suggested fix, and next debugging steps."
 ---
 
 # Debugging Log Analyser Skill
@@ -16,10 +16,13 @@ Ask for these if not provided:
 - **Environment** (local dev / staging / production)
 - **What they've already tried** (if anything)
 
-## Output Structure
+## Output Format
 
-### 1. Error Classification
-**Error type:** [Runtime exception / Build error / Config error / Network error / Memory/resource error / Unknown]
+---
+
+# Debugging Report: [Service/App Name]
+
+**Error type:** [Runtime exception / Build error / Config error / Network error / Memory error / Unknown]
 **Severity:** [Fatal / Critical / Warning / Informational]
 **Recurrence pattern:** [One-off / Intermittent / Consistent / On-startup / Under load]
 
@@ -64,16 +67,11 @@ One or two concrete things that would prevent this class of error recurring:
 - Add monitoring/alerting for [condition]
 - Test that covers [scenario]
 
+---
+
 ## Quality Checks
 - [ ] Root cause is specific (not "there might be a null pointer issue")
 - [ ] At least one concrete code-level fix is suggested
 - [ ] Next steps are actionable commands, not vague advice
 - [ ] Language-specific idioms are used correctly
 - [ ] Prevention is proactive (not just "add error handling")
-
-## Example Trigger Phrases
-- "Why is this crashing?" + [paste log]
-- "Can you analyse this stack trace?"
-- "I'm getting this error, what does it mean?"
-- "Debug this log for me"
-- "What's causing this exception?"