← ClaudeAtlas

protocol-123listed

Strict 9-phase multi-agent autonomous engineering and bugfixing pipeline triggered by '123' or 'по 123'. Enforces SDD-first specification, multi-agent plan review, user sign-off gateway, TDD-driven execution (Red-Green-Refactor), multi-agent code/test review, two-strike self-healing, and QA verification.
ivanestar/eitr · ★ 4 · Testing & QA · score 77
Install: claude install-skill ivanestar/eitr
# The 123 Protocol Skill (v2.1) ## Purpose Provides a 100% deterministic engineering workflow combining **Spec-Driven Architecture (SDD)** with **Test-Driven Execution (TDD)** and multi-agent verification swarms. ## Activation Rules & Trigger Phrases - **Strict Trigger Rule (Explicit Activation Only)**: - The 123 Protocol is activated **STRICTLY AND ONLY** when the user explicitly requests it via keywords: - `123` / `по 123` (Full Swarm) - `таска по 123` / `исправь по 123` - `123-fast` (Fast Track for 1-file minor fixes) - For standard requests without "123", execute directly in standard mode. - **Proactive Suggestion (User Decision Gateway)**: For complex multi-file refactorings or architectural changes, the assistant may proactively ask: _"Хотите выполнить эту задачу по протоколу 123 с полным мульти-агентным ревью?"_. The 123 pipeline is launched ONLY if the user explicitly approves. ## Modes 1. **Full Protocol (`123`)**: - 9-phase lifecycle: live web & codebase recon, invariants discovery feeding the Architect, single Lead Reviewer with Arbiter escalation gateway, and TDD execution. 2. **Fast Track (`123-fast`)**: - 1 research -> 1 plan -> User Approval Gateway -> 1 TDD execution (Red -> Green) -> 1 reviewer -> QA. - Used for single-file, pre-scoped fixes. ## Deterministic Orchestration Script To eliminate LLM reasoning drift or omission of mandatory subagents (such as skipping `web-researcher` or invariant discovery), orchestrators can i