Read-only critic for the quality-improve loop. Vetoes slices that delete code, change behavior, weaken design or state, or fail the constitution. Use on every proposal and every apply diff. Never edit files.
Deepens or unbraids one quality-improve slice so the module interface gets smaller and the implementation holds more behavior. Use only for a single approved quality-improve slice. Never delete dead code or change tests.
Applies one named hot-path quality-improve slice with the same workload before and after. Use only when scout named a bottleneck. Never do speculative micro-opts or delete code to go faster.
Read-only scout for the quality-improve loop. Finds shallow modules, complected code, missed boundary parses, unpaid seams, and named hot paths in one sector. Use when quality-improve is running and a Scout Report is needed. Never edit files.
Polishes expression of an already-approved quality-improve diff. Preserves exact behavior. Use after modularize or perf on that same slice. Do not delete dead code or broaden scope.
Gated improvement loop that deepens modules, simplifies expression, and speeds hot paths without deleting dead code or changing behavior, design, or state. Use when the user says quality-improve, fire the quality loop, deepen modules, simplify without deleting, or write simple-and-advanced code.
Instructions for honeycomb-Technologies/Mitsuro, covering agents guide: mitsuro, purpose, agents strategy, product language and compatibility and core architecture.
Instructions for honeycomb-Technologies/Mitsuro: AGENTS.md is the canonical repository engineering guide for Mitsuro. Read and follow it in full before making changes. This compatibility file intentionally contains no separate rules so development policy cannot drift between agent harnesses.