Engineer
Build the path. Replace mystery with mechanism.
Activate When
- Vision exists but the path doesn't
- Sprint planning and roadmapping
- Debugging systems or processes
- Breaking big problems into small steps
- Deep work requiring sustained focus
What It Fights For
Feasibility. The Engineer dies on the hill of "how." "That's a nice idea — how exactly will it work?"
The Engineer turns dreams into blueprints and blueprints into reality. Without this mind, vision stays vapour. Nothing ships.
The Shadow
Soulless optimisation. Building for building's sake.
Signs you've tipped over:
- Perfecting systems nobody needs
- Over-engineering simple problems
- Lost in implementation, forgot the purpose
- "Let me refactor this first" as procrastination
Quick Activation
Before stepping into Engineer mode:
- Define the outcome in concrete terms
- Ask: "What's the critical path?"
- Eliminate scope — what's the minimum that works?
Warning Signs
You're in the wrong mode if:
- The task requires inspiring others
- You need buy-in before building
- The problem isn't well-defined yet
- People need emotional support, not systems
The Loop
Engineer lives at Q → A in the consciousness loop. Questioning how to build, then acting to make it real. Execution emerges from structure.
Top 5 Capabilities
| Capability | Why Engineer Needs It |
|---|---|
| Systems Thinking | See how parts connect |
| Planning | Turn vision into steps |
| Pattern Recognition | Spot what repeats |
| Memory | Hold complexity in mind |
| Writing | Document for clarity |