Harness-engineering harness-event-driven
name: harness-event-driven
install
source · Clone the upstream repo
git clone https://github.com/Intense-Visions/harness-engineering
manifest:
agents/skills/claude-code/harness-event-driven/skill.yamlsource content
name: harness-event-driven version: "1.0.0" description: Message queues, event sourcing, CQRS, and saga patterns stability: static cognitive_mode: constructive-architect triggers:
- manual
- on_new_feature platforms:
- claude-code
- gemini-cli
- cursor
- codex tools:
- Bash
- Read
- Write
- Edit
- Glob
- Grep
cli:
command: harness skill run harness-event-driven
args:
- name: path description: Project root path required: false
- name: pattern description: "Pattern focus: pub-sub, event-sourcing, cqrs, or saga. All evaluated when omitted." required: false
- name: broker description: "Message broker: kafka, rabbitmq, sqs, nats, redis-streams. Auto-detected when omitted." required: false mcp: tool: run_skill input: skill: harness-event-driven path: string type: rigid tier: 3 internal: false keywords:
- event
- message queue
- kafka
- rabbitmq
- SQS
- pub/sub
- event sourcing
- CQRS
- saga
- async
- webhook
- event bus
- NATS
- Redis Streams stack_signals:
- "src//events/"
- "src//handlers/"
- "src//subscribers/"
- "src//sagas/"
- "docker-compose.kafka"
- "docker-compose.rabbit"
- "src//queues/" phases:
- name: discover description: Map existing event flows, message brokers, and async boundaries required: true
- name: design description: Produce event schemas, topic topology, and handler architecture required: true
- name: validate description: Check for delivery guarantees, idempotency, ordering, and failure handling required: true
- name: document description: Generate event catalog, flow diagrams, and contract documentation required: true state: persistent: false files: [] depends_on: [] related_skills:
- events-event-schema
- events-pubsub-pattern
- events-kafka-patterns
- events-outbox-pattern