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/commands/reproduce-bug.md

@@ -0,0 +1,27 @@
+---
+name: reproduce-bug
+description: Reproduce and investigate a bug using logs and console inspection
+argument-hint: "[GitHub issue number]"
+---
+
+Look at github issue #$ARGUMENTS and read the issue description and comments.
+
+Then, run the following agents in parallel to reproduce the bug:
+
+1. Task rails-console-explorer(issue_description)
+2. Task appsignal-log-investigator (issue_description)
+
+Then think about the places it could go wrong looking at the codebase. Look for loggin output we can look for.
+
+Then, run the following agents in parallel again to find any logs that could help us reproduce the bug.
+
+1. Task rails-console-explorer(issue_description)
+2. Task appsignal-log-investigator (issue_description)
+
+Keep running these agents until you have a good idea of what is going on.
+
+**Reference Collection:**
+
+- [ ] Document all research findings with specific file paths (e.g., `app/services/example_service.rb:42`)
+
+Then, add a comment to the issue with the findings and how to reproduce the bug.