architect

Compare two or three technical approaches for a feature or system (ownership, interfaces, data flow, failure behaviour, operational cost, migration, testing) and recommend one with its trade-offs, before anyone writes code. It first asks for architecture diagrams or docs the repo can't show and confirms how the system works. For a question about building or storing something, it proposes the simplest concrete design, starting from what already exists, (such as a table's keys and indexes) and walks every query in the question through it; can record the decision as a short ADR. Use for "how should we design this?", "A or B?", "which approach is better?", "should this be a queue or a cron job?", "where should this logic live?", or any design choice with real alternatives. For checking a recommendation already made, use challenge; to stress-test one option, use devils-advocate. (Dev Mentor)