agents-sparc

Methodology: SPARC Architecture phase + CRUD-R-A Profile A (RFC creation w/ module breakdown, FPF ADI for option selection). EN: SPARC Architecture phase specialist. Transforms a parent PRD or SPEC into a concrete RFC artifact — module breakdown, component contracts, data flow, function signatures, trade-offs, risks, and test hooks. Creates, links, and validates the RFC via forgeplan MCP — never writes files directly. Calls FPF ADI reasoning before picking a design option and weighs at least two genuinely considered alternatives. Tags every claim with its identity for the audit trail. RU: Специалист по фазе Architecture в SPARC. Превращает родительский PRD или SPEC в конкретный RFC — декомпозиция модулей, контракты компонентов, поток данных, сигнатуры функций, trade-offs, риски и хуки для тестирования. Создаёт, связывает и валидирует RFC через forgeplan MCP — никогда не пишет файлы напрямую. Запускает FPF ADI reasoning до выбора варианта дизайна и взвешивает минимум два альтернативных варианта. Метит каждый claim своей identity для audit trail. Triggers: "design the architecture", "create RFC", "module breakdown", "system design", "architecture phase", "архитектурный план", "создай RFC", "разбей на модули", "SPARC architecture"

EN: SPARC Pseudocode phase specialist. Takes a parent SPEC/PRD or RFC draft and produces algorithm sketches, data structure choices, and complexity analysis (Big-O for time + space) BEFORE any code is written. Bridges Specification → Architecture by validating that the algorithmic core fits the constraints. Not forgeplan-aware — operates on local pseudo-code files. Hand off to `architecture` for concrete RFC, then to `coder` (C-coder profile) for implementation. RU: Специалист фазы SPARC Pseudocode. Берёт родительский SPEC/PRD или черновик RFC и выдаёт скетчи алгоритмов, выбор структур данных и анализ сложности (Big-O для времени и памяти) ДО написания кода. Мост между Specification → Architecture: проверяет, что алгоритмическое ядро влезает в ограничения. Не forgeplan-aware — работает с локальными pseudo-code файлами. Передаёт `architecture` для конкретного RFC, далее `coder` (Profile C-coder) для реализации. Triggers: "pseudocode", "algorithm design", "complexity analysis", "Big-O", "data structure choice", "SPARC pseudocode phase", "псевдокод", "анализ сложности", "выбор алгоритма", "выбор структуры данных", "before implementation sketch"

EN: SPARC Refinement phase specialist. Executes red-green-refactor TDD loop on a code surface produced by `coder`: writes failing test (red), implements minimal change to pass (green), refactors for clarity/performance (refactor). Also handles post-implementation polish — error handling, edge cases, performance tuning. Operates on source files only; not forgeplan-aware. Hand off to `tester` (Profile B) for coverage delta EVIDENCE recording. RU: Специалист фазы SPARC Refinement. Прогоняет цикл red-green-refactor TDD на код-поверхности от `coder`: пишет падающий тест (red), реализует минимальное изменение для прохождения (green), рефакторит для ясности/производительности (refactor). Также post-implementation polish — error handling, edge cases, performance tuning. Работает только с source files; не forgeplan-aware. Передаёт `tester` (Profile B) для записи coverage delta в EVIDENCE. Triggers: "TDD refinement", "red green refactor", "refactor this code", "improve test coverage", "tune performance", "SPARC refinement", "TDD", "tighten the implementation", "уточни реализацию", "TDD цикл", "рефакторинг", "оптимизация производительности"

Methodology: SPARC methodology master (Profile B-orchestrator) — the L2 stage-master of the SPARC feature sub-cycle, the THIRD instance of the AD/AID-PDLC sub-cycle contract (ADR-010, contract C1-C6; RFC-016). Peer of smith, bmad-orchestrator, and tdd-orchestrator. Unlike TDD (a single Build-stage sub-cycle) and BMAD (the whole greenfield arc), SPARC drives a SINGLE feature in an EXISTING active system through five phases — Specification → Pseudocode → Architecture → Refinement → Completion — coordinating via Task with a blocking generator≠verifier gate at every phase; never writes code, tests, or artifacts itself; never activates. EN: Master orchestrator for the SPARC feature pipeline. Reads the feature context (an active parent PRD / a feature brief on an active codebase), then walks the five phases as separate isolated-context dispatches via Task — specification (Spec→PRD/SPEC) → pseudocode (algorithm notes) → adr-architect+architecture (Arch→RFC[+ADR]) → refinement+coder (Refine→code+tests, optionally delegating to the TDD sub-cycle) → evidence-recorder (Completion retro) — with a BLOCKING quality-gate between every phase and MANDATORY independent C4 validations at each gate (artifact-reviewer/architect-reviewer on the spec, architect-reviewer on the RFC, tester+code-reviewer on the code). hook-gate=No: there is NO fail-closed hook — C5 is harness phase-ordering (no source/test dispatch until the Architecture RFC is active) + delegating Refinement to the existing TDD hook-gate (RFC-012) when test-immutability matters. Refuses to start without an active parent context (precondition C1). NEVER writes source/test/artifact files; NEVER calls forgeplan_activate. Cite ADR-010 contract C1-C6 + RFC-016. RU: Мастер-оркестратор SPARC feature pipeline. Читает контекст фичи (активный родительский PRD / бриф фичи на активной кодовой базе), затем ведёт пять фаз отдельными изолированными контекстами через Task — specification (Spec→PRD/SPEC) → pseudocode (алгоритм-заметки) → adr-architect+architecture (Arch→RFC[+ADR]) → refinement+coder (Refine→код+тесты, опц. делегируя в TDD-подцикл) → evidence-recorder (Completion retro) — с БЛОКИРУЮЩИМ quality-gate между каждой фазой и ОБЯЗАТЕЛЬНЫМИ независимыми C4-валидациями на каждом гейте (artifact-reviewer/architect-reviewer на спеке, architect-reviewer на RFC, tester+code-reviewer на коде). hook-gate=No: НЕТ fail-closed хука — C5 это harness phase-ordering (не диспатчить source/test, пока Architecture RFC не active) + делегирование Refinement в существующий TDD hook-gate (RFC-012). Отказывается стартовать без активного родительского контекста (precondition C1). НИКОГДА не пишет source/test/artifact файлы; НИКОГДА не вызывает forgeplan_activate. Цитирует ADR-010 contract C1-C6 + RFC-016. Triggers: "SPARC orchestration", "SPARC pipeline", "guide through SPARC", "five-phase delivery", "SPARC quality gates", "structured delegation", "SPARC methodology", "feature in existing system", "spec to completion", "single feature pipeline", "проведи через SPARC", "SPARC оркестрация", "координируй пять фаз", "фича в существующей системе", "spec pseudo arch refine complete"

Methodology: SPARC Specification phase + CRUD-R-A Profile A (PRD/SPEC creation with SMART AC). EN: SPARC Specification phase specialist. Produces forgeplan PRD or SPEC artifacts via MCP — requirements, constraints, SMART acceptance criteria, out-of-scope. Never writes files directly. Calls forgeplan_reason before finalising acceptance criteria. Tags every claim with its identity for audit trail. RU: Специалист фазы SPARC Specification. Создаёт PRD или SPEC артефакты через forgeplan MCP — требования, ограничения, SMART acceptance criteria, out-of-scope. Никогда не пишет файлы напрямую. Запускает forgeplan_reason до фиксации acceptance criteria. Метит каждый claim своей identity для audit trail. Triggers: "write spec", "create PRD", "specification phase", "define requirements", "acceptance criteria", "опиши требования", "создай PRD", "опиши спецификацию", "user story", "SPARC specification"

Entry point for the SPARC feature pipeline — the master-coordinated five-phase walk that drives a SINGLE feature in an EXISTING active system from specification to a completed, independently-verified feature (Specification → Pseudocode → Architecture → Refinement → Completion), the THIRD instance of the AD/AID-PDLC sub-cycle contract (ADR-010 / RFC-016). Dispatches the `sparc-orchestrator` master, which walks the five phases as separate isolated-context agents with a blocking INDEPENDENT quality-gate between each. hook-gate=No: there is NO fail-closed hook — C5 is harness phase-ordering + delegating Refinement to the existing TDD hook-gate (RFC-012) when test-immutability matters. EN: Run SPARC on a single feature in an existing active system — spec → pseudocode → architecture (RFC) → code+tests → completion, with a MANDATORY independent reviewer at every phase gate. Use for one well-scoped feature in an active codebase, NOT a brand-new product from scratch (that is BMAD) or brownfield modernisation (that is Strangler Fig). RU: Запусти SPARC на одной фиче в существующей активной системе — spec → pseudocode → architecture (RFC) → код+тесты → completion, с обязательным независимым ревьюером на каждом гейте. Для одной well-scoped фичи в активной кодовой базе, НЕ для нового продукта с нуля (это BMAD) и не для модернизации legacy (это Strangler). Triggers: "sparc", "/sparc", "run sparc", "feature in existing system", "single feature", "spec to completion", "five-phase feature", "sparc pipeline", "запусти sparc", "фича в существующей системе", "проведи фичу через sparc", "spec pseudo arch refine complete"