
Project-local guidance for CodebrewRouter Codex skills. Use when documenting, creating, reviewing, or maintaining repository-specific Codex skills under .agents/skills for the Blaze.LlmGateway project.
Generate a Product Requirements Document from a task description, user intent, or PRD outline. Structure the PRD with sections: Overview, Problem Statement, Goals, Scope, Features, Acceptance Criteria, Metrics. Use this when the Planner or Orchestrator needs to formalize requirements before decomposing into implementation steps.
Supervise an autonomous multi-agent loop, detecting stalls, managing timeouts, and performing safe interventions when agents are blocked or slow. Monitor agent health, log decisions, and escalate issues. Use this in the Orchestrator parallel path to ensure the autonomous loop makes progress and doesn't deadlock or hang.
Enforce the -warnaserror build + 95% coverage test gate on every squad [DONE]. Use this before any specialist (Coder, Tester, Reviewer, Infra) marks a phase complete.
DevSquad-style bug-fix flow — reproduce, write a failing test, fix, verify. Use this whenever the squad task is "fix bug X" or the Planner flags a step as a bug repro.
Orchestrate parallel agent development using Git worktrees. Spin isolated checkouts for each task, assign Coders to independent worktrees, monitor progress, and merge results back. Use this when the Conductor or Orchestrator needs to parallelize file-disjoint implementation tasks across multiple agents.
Maintain the append-only reasoning log and write handoff envelopes for every squad delegation. Use this when the Conductor delegates to a specialist or when a specialist records a non-trivial decision.
Provide a task queue, scheduler, and persistent memory system for autonomous multi-agent loops. Track task state, monitor agent progress, retry on failure, and persist decisions across sessions. Use this in the Orchestrator parallel path when running an autonomous PRD-driven loop without human gates.
Automatically dispatch multiple agent subtasks in parallel based on file-lock disjointness. Compute task dependencies, validate no file conflicts, emit parallel delegation handoffs. Use this when the Conductor or Orchestrator has multiple independent Coder/Tester tasks to farm out simultaneously.
Orchestrate parallel agent workflows using tmux pane management (via dmux or native tmux). Spin multiple agents in isolated tmux panes, monitor logs, synchronize completion, and collect results. Use this in the Orchestrator parallel path when targeting Unix/Linux or WSL environments for shell-based coordination.
Delegate implementation work to specialized subagent instances, each inheriting a task scope and constraints from the parent. Emit structured handoffs, monitor completion signals, aggregate results. Use this in the Orchestrator parallel path when spawning independent Coder/Tester/Infra subagents from a single coordinator.
Compose parallel teams of specialized agents for a multi-faceted task. Map subtasks to agent roles, balance workload, and validate team composition. Use this when breaking a task into parallel streams that require different expertise (Coder, Tester, Infra, etc.).