From golang-workflow
Agent isolation, communication protocols, failure triage, and TDD workflow rules
npx claudepluginhub jamesprial/prial-plugins --plugin golang-workflowThis skill uses the workspace's default tool permissions.
Rules for agent isolation, communication boundaries, failure classification, and TDD workflows in multi-agent pipelines.
Applies RED-GREEN-REFACTOR TDD to test workflow instructions and commands: reproduces real failures with subagents, clarifies docs before deployment.
Defines SPAWN REQUEST format, structured reports, and protocols for spawning, coordinating, and running parallel agents in Sprint plugin multi-agent sprints.
Provides protocols, templates, and rules for constructing subagent delegation prompts with context chains, protocol injection, and downstream declarations in agent orchestration.
Share bugs, ideas, or general feedback.
Rules for agent isolation, communication boundaries, failure classification, and TDD workflows in multi-agent pipelines.
| Topic | Description |
|---|---|
| test-writer-isolation.md | Strict isolation rules for test writers and implementer awareness boundaries |
| failure-triage.md | Classifying failures as CODE_BUG, TEST_BUG, or CONTRACT_MISMATCH for selective retry |
| tdd-protocol.md | RED-GREEN-REFACTOR cycle for true test-driven development mode |
Certain agents must be isolated from specific information to ensure unbiased outputs. The most critical example is Test Writer isolation — test writers must not see implementation code to write tests that verify specifications rather than implementations.
Architect → Implementation Spec ──────────────→ Implementer → Code
↘ ↗
Test Spec ─→ Test Writer → Tests
↘ ↑ (fix mode only)
Test Spec ─→ Triage → Fix Guidance