66s Review
Benchmarked against: Anthropic — Using the Evaluation Tool Skill:
/66s-review(on-demand, L3 Progressive Disclosure) Framework: Six Thinking Hats (de Bono) + Six Action Shoes (de Bono) + Systems Thinking
The 66s Review is SuperPortia's systematic review framework for plans, specs, architecture decisions, and any proposal before Captain approval. It ensures decisions are examined from multiple perspectives before commitment.
When to use
| Trigger | Example |
|---|---|
| Major spec or plan | MTAAA v1.4 spec review |
| Architecture decision | Choosing between LangGraph vs n8n |
| Before HITL presentation | Presenting options to Captain |
| WO with high blast radius | Infrastructure migration |
| New capability design | PAM (Project Agentic Manager) design |
Rule of thumb: If a decision affects multiple agents, ships, or is hard to reverse — run a 66s Review first.
The framework
Six Thinking Hats
Each "hat" represents a thinking perspective. The review cycles through all six:
| Hat | Color | Perspective | Key question |
|---|---|---|---|
| ⬜ White | Information | What data do we have? What's missing? | "What are the facts?" |
| 🟥 Red | Emotion/Intuition | Gut feeling — what feels right or wrong? | "What does instinct say?" |
| ⬛ Black | Caution | Risks, dangers, weaknesses | "What could go wrong?" |
| 🟨 Yellow | Optimism | Benefits, opportunities, value | "What's the best case?" |
| 🟩 Green | Creativity | Alternatives, new ideas | "What else could we do?" |
| 🟦 Blue | Process | Meta-thinking — is the review process working? | "Are we thinking correctly?" |
Six Action Shoes
Each "shoe" represents an action mode — what to do after thinking:
| Shoe | Color | Action mode | When to use |
|---|---|---|---|
| 🔵 Navy | Formal/Routine | Follow established procedures | Standard operations, SOPs |
| 🟤 Brown | Pragmatic | Get practical results | Implementation, delivery |
| 🟠 Orange | Emergency | Act quickly on danger | Incidents, critical failures |
| 🩷 Pink | Caring | Consider human impact | Team dynamics, user experience |
| 🟣 Purple | Authority | Exercise judgment | Captain decisions, policy changes |
| 🔘 Grey | Investigation | Gather more information | Unknowns, research needed |
Systems Thinking
The third lens — how this decision interacts with the whole system:
| Check | Question |
|---|---|
| Dependencies | What depends on this? What does this depend on? |
| Feedback loops | Will this create positive or negative spirals? |
| Side effects | What unintended consequences are possible? |
| Reversibility | How hard is it to undo? |
| Fleet impact | Does this affect SS1/SS2/SS3 differently? |
Review output format
## 66s Review: [Subject]
### White Hat — Facts
- [Data points, current state, metrics]
### Red Hat — Intuition
- [Gut feelings, team sentiment]
### Black Hat — Risks
- [Potential failures, weaknesses, costs]
### Yellow Hat — Benefits
- [Advantages, opportunities, value]
### Green Hat — Alternatives
- [Other approaches considered]
### Blue Hat — Process
- [Is this review thorough? What's missing?]
### Action Shoes
- **Recommended shoe:** [which action mode]
- **Rationale:** [why this mode]
### Systems Thinking
- **Dependencies:** [what's affected]
- **Reversibility:** [easy/moderate/hard]
### Verdict
- **Recommendation:** [approve / approve with conditions / reject / needs more research]
- **Conditions:** [if applicable]
- **Key risks to monitor:** [top 2-3 risks]
Review scoring
Each hat dimension gets a score:
| Score | Meaning |
|---|---|
| ✅ Clear | This dimension is well-addressed |
| ⚠️ Concern | Issues identified but manageable |
| 🔴 Blocker | Critical issue — must be resolved before proceeding |
A review with any 🔴 Blocker cannot be approved until the blocker is resolved.
Integration with WO system
66s Reviews are typically triggered during the Architect phase of the ADLC:
Review results are ingested to UB with tags: 66s-review, [project], [subject].
Example reviews
| Subject | Verdict | Key insight | UB ref |
|---|---|---|---|
| PAM Design Spec v1.1 | Approved with 4 recommendations | Purple shoe — this is a Captain-level architecture decision | ub-7a4a003357d5 |
| Cloud UB Migration | Approved | Orange shoe — current split is causing data loss risk | ub-396f44b70763 |
| MTAAA v1.4 | Approved | Green hat found Amazon Books as taxonomy source | MTAAA spec |
Related pages
| Page | Relationship |
|---|---|
| EGS Compliance | 66s Review is part of EGS compliance for major decisions |
| Pre-Flight Check | Quick risk check (30 seconds) vs full review (66s) |
| EGS Spec | ADLC Architect phase requires 66s Review |
| HITL/HOTL | Review results inform Captain decisions |