mirror of
https://github.com/wshobson/agents.git
synced 2026-03-18 09:37:15 +00:00
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.
This commit is contained in:
@@ -22,16 +22,19 @@ Master microservices architecture patterns including service boundaries, inter-s
|
||||
### 1. Service Decomposition Strategies
|
||||
|
||||
**By Business Capability**
|
||||
|
||||
- Organize services around business functions
|
||||
- Each service owns its domain
|
||||
- Example: OrderService, PaymentService, InventoryService
|
||||
|
||||
**By Subdomain (DDD)**
|
||||
|
||||
- Core domain, supporting subdomains
|
||||
- Bounded contexts map to services
|
||||
- Clear ownership and responsibility
|
||||
|
||||
**Strangler Fig Pattern**
|
||||
|
||||
- Gradually extract from monolith
|
||||
- New functionality as microservices
|
||||
- Proxy routes to old/new systems
|
||||
@@ -39,11 +42,13 @@ Master microservices architecture patterns including service boundaries, inter-s
|
||||
### 2. Communication Patterns
|
||||
|
||||
**Synchronous (Request/Response)**
|
||||
|
||||
- REST APIs
|
||||
- gRPC
|
||||
- GraphQL
|
||||
|
||||
**Asynchronous (Events/Messages)**
|
||||
|
||||
- Event streaming (Kafka)
|
||||
- Message queues (RabbitMQ, SQS)
|
||||
- Pub/Sub patterns
|
||||
@@ -51,11 +56,13 @@ Master microservices architecture patterns including service boundaries, inter-s
|
||||
### 3. Data Management
|
||||
|
||||
**Database Per Service**
|
||||
|
||||
- Each service owns its data
|
||||
- No shared databases
|
||||
- Loose coupling
|
||||
|
||||
**Saga Pattern**
|
||||
|
||||
- Distributed transactions
|
||||
- Compensating actions
|
||||
- Eventual consistency
|
||||
@@ -63,14 +70,17 @@ Master microservices architecture patterns including service boundaries, inter-s
|
||||
### 4. Resilience Patterns
|
||||
|
||||
**Circuit Breaker**
|
||||
|
||||
- Fail fast on repeated errors
|
||||
- Prevent cascade failures
|
||||
|
||||
**Retry with Backoff**
|
||||
|
||||
- Transient fault handling
|
||||
- Exponential backoff
|
||||
|
||||
**Bulkhead**
|
||||
|
||||
- Isolate resources
|
||||
- Limit impact of failures
|
||||
|
||||
|
||||
Reference in New Issue
Block a user