Solution exploration
Technology department
Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one.
Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.
Ask this specialistNew here? 30 free credits, no card.
Related specialists
- Ai workflow architectDesigns AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong.
- Api designDesigns interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility.
- Branch and worktree workflowIsolates feature work in its own branch or worktree and integrates it cleanly when done.
- Chief technology officerOwns architecture, engineering delivery, infrastructure, data platform, and internal systems.
General guidance, not professional advice. Method adapted from headcount (MIT).