The Softdev Pipeline
One event line can trigger an AI agent to plan, build, lint, and test -- automatically.
What you'll see
- Launch
rysh, split a worker pane, and have it##pane listen orchestrator. Tabback to the orchestrator and double-Escape into rysh mode.- Fire
##>event:ai:softdev:golang:planning-- triggers the worker's AgenticActor to analyze and plan. - Fire
##>event:sh:softdev:golang:development-- runsgo build ./...on the listening pane. - Fire
##>event:ai:softdev:golang:unit_testing-- the agent runs tests and fixes failures.
Commands shown
rysh
n
##pane listen orchestrator
##>event:ai:softdev:golang:planning
##>event:sh:softdev:golang:development
##>event:ai:softdev:golang:unit_testing
Keys used
Transcript
0:00One event line can trigger an AI agent to plan, build, lint, and test -- automatically.
0:03Start rysh and split a worker pane. The worker will listen and react to software-development events.
0:09In rysh mode, the worker listens to the orchestrator pane, so softdev events fire its AgenticActor.
0:16Back on the orchestrator, switch to rysh mode. The softdev schema is ai or sh, softdev, language, then phase.
0:24ai softdev golang planning triggers the worker's agent to analyze the codebase and draft an implementation plan.
0:33The sh prefix runs a real command instead. sh softdev golang development runs go build across the listening pane.
0:41ai softdev golang unit_testing has the agent run go test and fix any failures. Phases run from planning to monitoring.
0:47Planning, development, linting, testing, deployment, monitoring -- an autonomous build pipeline, one event at a time.
ai|sh:softdev:<lang>:<phase> across phases (planning, development, linting, unit_testing, integration_testing, deployment, monitoring) -- ai: drives the AgenticActor, sh: runs commands.