governed-workflow

Orchestrates a governed multi-phase implementation workflow — assessment, research, planning, execution, review, and delivery — with backend-enforced phase gates, scope locking, and proof-driven research.

Guides the orchestrator through phases 1.0-1.4 of the governed workflow — assessment, research, research proving, impact analysis, and preparation review. Produces a thorough, structured foundation before planning begins.

Guides the orchestrator through Phase 2.0 (Planning) of the governed workflow — structuring the execution plan (with per-item scope), proposing acceptance criteria, and collaborating with the plan-advisor teammate.

Install, repair, and manage the multi-session Telegram channel server that allows switching between Claude Code sessions from Telegram

Initial workspace setup — configures modules and verification profiles based on user selections from the admin panel

Install, repair, and manage the multi-session Telegram channel server that allows switching between Claude Code sessions from Telegram

Manage project rules (.claude/rules/*.md with glob-based auto-loading). Use when authoring, editing, or deleting rule files via MCP, or when explaining how rule loading works to the user.

Diagnose and fix Claude Chrome extension connectivity issues. Use when browser automation tools fail with "extension not connected" or similar errors.

Commit, push, and create merge requests in GitLab. ONLY use when the user explicitly asks to commit, push, or create an MR. Never do any of these autonomously.

Review local branch changes vs develop before creating an MR. Launches 4 independent sub-agents for objective code review. Posts no comments — outputs findings to console.