feat(plugin): reorganize compounding-engineering v2.0.0

Major restructure of the compounding-engineering plugin:

## Agents (24 total, now categorized)
- review/ (10): architecture-strategist, code-simplicity-reviewer,
  data-integrity-guardian, dhh-rails-reviewer, kieran-rails-reviewer,
  kieran-python-reviewer, kieran-typescript-reviewer,
  pattern-recognition-specialist, performance-oracle, security-sentinel
- research/ (4): best-practices-researcher, framework-docs-researcher,
  git-history-analyzer, repo-research-analyst
- design/ (3): design-implementation-reviewer, design-iterator,
  figma-design-sync
- workflow/ (6): bug-reproduction-validator, every-style-editor,
  feedback-codifier, lint, pr-comment-resolver, spec-flow-analyzer
- docs/ (1): ankane-readme-writer

## Commands (15 total)
- Moved workflow commands to commands/workflows/ subdirectory
- Added: changelog, create-agent-skill, heal-skill, plan_review,
  prime, reproduce-bug, resolve_parallel, resolve_pr_parallel

## Skills (11 total)
- Added: andrew-kane-gem-writer, codify-docs, create-agent-skills,
  dhh-ruby-style, dspy-ruby, every-style-editor, file-todos,
  frontend-design, git-worktree, skill-creator
- Kept: gemini-imagegen

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

plugins/compounding-engineering/skills/codify-docs/assets/critical-pattern-template.md

@@ -0,0 +1,34 @@
+# Critical Pattern Template
+
+Use this template when adding a pattern to `docs/solutions/patterns/cora-critical-patterns.md`:
+
+---
+
+## N. [Pattern Name] (ALWAYS REQUIRED)
+
+### ❌ WRONG ([Will cause X error])
+```[language]
+[code showing wrong approach]
+```
+
+### ✅ CORRECT
+```[language]
+[code showing correct approach]
+```
+
+**Why:** [Technical explanation of why this is required]
+
+**Placement/Context:** [When this applies]
+
+**Documented in:** `docs/solutions/[category]/[filename].md`
+
+---
+
+**Instructions:**
+1. Replace N with the next pattern number
+2. Replace [Pattern Name] with descriptive title
+3. Fill in WRONG example with code that causes the problem
+4. Fill in CORRECT example with the solution
+5. Explain the technical reason in "Why"
+6. Clarify when this pattern applies in "Placement/Context"
+7. Link to the full troubleshooting doc where this was originally solved