refactor: remove operator and reflector hats and workflows

Remove the operator and reflector hats, their workflow definitions
(operational, reflective), and all references from README, inject-context
hook, reflect skill, and workflows.yml.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: jwaldrip

README.md

@@ -238,8 +238,6 @@ Select a workflow during `/elaborate`:
 | **default** | Standard development | planner, builder, reviewer |
 | **adversarial** | Security-focused with Red/Blue team | planner, builder, red-team, blue-team, reviewer |
 | **design** | UI/UX units producing design artifacts | planner, designer, reviewer |
-| **operational** | Development with operational setup | planner, builder, operator, reviewer |
-| **reflective** | Full lifecycle with reflection | planner, builder, operator, reflector, reviewer |
 | **hypothesis** | Scientific debugging | observer, hypothesizer, experimenter, analyst |
 
 ## Hats
@@ -261,8 +259,6 @@ All hats follow the [Agent SOP format](https://github.com/strands-agents/agent-s
 | Builder | Implement according to plan and criteria |
 | Reviewer | Verify implementation meets criteria |
 | Designer | Produce UI/UX design artifacts |
-| Operator | Execute operational setup tasks |
-| Reflector | Analyze outcomes and capture learnings |
 | Integrator | Cross-cutting integration concerns |
 | Test Writer | Write failing tests first |
 | Implementer | Make tests pass with minimal code |

plugin/hats/operator.md

@@ -319,8 +319,6 @@ if [ -z "$PHASE" ]; then
   HAT_FOR_PHASE=$(echo "$ITERATION_JSON" | han parse json hat -r --default "builder" 2>/dev/null || echo "builder")
   case "$HAT_FOR_PHASE" in
     planner) PHASE="elaboration" ;;
-    operator) PHASE="operation" ;;
-    reflector) PHASE="reflection" ;;
     *) PHASE="execution" ;;
   esac
   ITERATION_JSON=$(echo "$ITERATION_JSON" | han parse json-set phase "$PHASE" 2>/dev/null || echo "$ITERATION_JSON")

plugin/hats/reflector.md

@@ -169,11 +169,9 @@ Produce a structured analysis:
 | {gate} | {%} | {useful/noisy/misconfigured} |
 ```
 
-### Step 3: Don the Reflector Hat
+### Step 3: Analyze Outcomes
 
-Load and follow the Reflector hat instructions from `hats/reflector.md`.
-
-As the Reflector, analyze:
+Perform a structured reflection analysis. As the reflector, analyze:
 
 1. **Execution patterns** - Which units went smoothly? Which required retries?
 2. **Criteria satisfaction** - How well were success criteria met? Any partial satisfaction?

plugin/hooks/inject-context.sh

@@ -20,14 +20,6 @@ design:
   description: Design workflow for UI/UX units that produce design artifacts
   hats: [planner, designer, reviewer]
 
-operational:
-  description: Workflow with operational setup
-  hats: [planner, builder, operator, reviewer]
-
-reflective:
-  description: Full lifecycle with reflection
-  hats: [planner, builder, operator, reflector, reviewer]
-
 hypothesis:
   description: Scientific debugging for investigating bugs
   hats: [observer, hypothesizer, experimenter, analyst]