feat: add Conductor plugin for Context-Driven Development

Add comprehensive Conductor plugin implementing Context-Driven Development
methodology with tracks, specs, and phased implementation plans.

Components:
- 5 commands: setup, new-track, implement, status, revert
- 1 agent: conductor-validator
- 3 skills: context-driven-development, track-management, workflow-patterns
- 18 templates for project artifacts

Documentation updates:
- README.md: Updated counts (68 plugins, 100 agents, 110 skills, 76 tools)
- docs/plugins.md: Added Conductor to Workflows section
- docs/agents.md: Added conductor-validator agent
- docs/agent-skills.md: Added Conductor skills section

Also includes Prettier formatting across all project files.

plugins/backend-development/skills/cqrs-implementation/SKILL.md

@@ -48,14 +48,14 @@ Comprehensive guide to implementing CQRS (Command Query Responsibility Segregati
 
 ### 2. Key Components
 
-| Component | Responsibility |
-|-----------|---------------|
-| **Command** | Intent to change state |
+| Component           | Responsibility                  |
+| ------------------- | ------------------------------- |
+| **Command**         | Intent to change state          |
 | **Command Handler** | Validates and executes commands |
-| **Event** | Record of state change |
-| **Query** | Request for data |
-| **Query Handler** | Retrieves data from read model |
-| **Projector** | Updates read model from events |
+| **Event**           | Record of state change          |
+| **Query**           | Request for data                |
+| **Query Handler**   | Retrieves data from read model  |
+| **Projector**       | Updates read model from events  |
 
 ## Templates
 
@@ -534,6 +534,7 @@ class ConsistentQueryHandler:
 ## Best Practices
 
 ### Do's
+
 - **Separate command and query models** - Different needs
 - **Use eventual consistency** - Accept propagation delay
 - **Validate in command handlers** - Before state change
@@ -541,6 +542,7 @@ class ConsistentQueryHandler:
 - **Version your events** - For schema evolution
 
 ### Don'ts
+
 - **Don't query in commands** - Use only for writes
 - **Don't couple read/write schemas** - Independent evolution
 - **Don't over-engineer** - Start simple